Installation Notes

   

Contents

System Requirements
J2SE Runtime Environment Installation Instructions
    Installation of Self-Extracting Binary
    Installation of RPM File
Java Plug-in Browser Registration Instructions
Java Web Start Installation Notes

System Requirements

System Configurations

For issues, see the Troubleshooting section of the JDK installation notes and the Linux Notes section of the Release Notes. Also available is Known Problems on Non-Supported Platforms of the JDK installation notes.

Installation Instructions

Install formats
  • Self-extracting Binary File - This file can be used to install the J2SE Runtime Environment in a location chosen by the user. This one can be installed by anyone (not only root users), and it can easily be installed in any location. As long as you are not root user, it cannot displace the system version of the Java platform suppled by Linux. To use this file, see Installation of Self-Extracting Binary below.

     

  • RPM Packages - A rpm.bin file containing RPM packages, installed with the rpm utility. Requires root access to install, and installs by default in a location that replaces the system version of the Java platform supplied by Linux. To use this bundle, see Installation of RPM File below.
Note: For any text on this page containing the following notation, you must substitute the appropriate J2SE Runtime Environment update version number for the notation.
                  <version>
              
For example, if you are downloading update 1.5.0_01, the following command:
                  ./jre-1_5_0_<version>-linux-i586.bin
              
would become:
                  ./jre-1_5_0_01-linux-i586.bin
              

Installation of Self-Extracting Binary

Installation of RPM File

1. Download and check the download file size to ensure that you have downloaded the full, uncorrupted software bundle.

You can download to any directory you choose; it does not have to be the directory where you want to install the J2SE Runtime Environment.

Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.

2. Make sure that execute permissions are set
Run this command:
chmod +x jre-1_5_0_<version>-linux-i586.bin

3. Change directory to the location where you would like the files to be installed.

The next step installs the J2SE Runtime Environment into the current directory.

4. Run the self-extracting binary.

Execute the downloaded file, prepended by the path to it. For example, if the file is in the current directory, prepend it with " ./" (necessary if " ." is not in the PATH environment variable):

./jre-1_5_0_<version>-linux-i586.bin

The binary code license is displayed, and you are prompted to agree to its terms.

The J2SE Runtime Environment files are installed in a directory called jre1.5.0_<version> in the current directory. Follow this link to see its directory structure.

Note about Root Access: Unbundling the software automatically creates a directory called jre1.5.0_<version>. Note that if you choose to install the J2SE Runtime Environment into system-wide location such as /usr/local, you must first become root to gain the necessary permissions. If you do not have root access, simply install the J2SE Runtime Environment into your home directory, or a subdirectory that you have permission to write to.

Note about Overwriting Files: If you unpack the software in a directory that contains a subdirectory named jre1.5.0_<version>, the new software overwrites files of the same name in that jre1.5.0_<version> directory. Please be careful to rename the old directory if it contains files you would like to keep.

Note about System Preferences: By default, the installation script configures the system such that the backing store for system preferences is created inside the J2SE Runtime Environment's installation directory. If the JRE is installed on a network-mounted drive, it and the system preferences can be exported for sharing with Java runtime environments on other machines. As an alternative, root users can use the -localinstall option when running the installation script, as in this example:

jre-1_5_0_<version>-linux-i586.bin -localinstall
This option causes the system preferences to be stored in the /etc directory from which they can be shared only by VMs running on the local machine. You must be root user for the -localinstall option to work.

See the Preferences API documentation for more information about preferences in the Java platform.

Installation of RPM File

Use these instructions if you want to install J2SE Runtime Environment in the form of RPM packages. If you want to use the self-extracting binary file instead, see Installation of Self-Extracting Binary.

1. Download and check the file size.

You can download to any directory you choose.

Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.

2. Become root by running the su command and entering the super-user password.

3. Extract and install the contents of the downloaded file.

Change directory to where the downloaded file is located and run these commands to first set the executable permissions and then run the binary to extract and run the RPM file:

 

                chmod a+x jre-1_5_0_<version>-linux-i586-rpm.bin  ./jre-1_5_0_<version>-linux-i586-rpm.bin
            

Note that the initial " ./" is required if you do not have " ." in your PATH environment variable.

The script displays a binary license agreement, which you are asked to agree to before installation can proceed. Once you have agreed to the license, the install script creates and runs the file jre-1_5_0_<version>-linux-i586.rpm in the current directory.

NOTE - If instead you want to only extract the RPM file but not install it, you can run the .bin file with the -x argument. You do not need to be root to do this.

4. Delete the bin and rpm file if you want to save disk space.

5. Exit the root shell.

Java Plug-in Browser Registration Instructions

See Java Plug-in Browser Registration Instructions in the Installation Notes for JDK for Linux.

Java Web Start Installation Notes

This J2SE Runtime Environment release includes Java Web Start; it is installed automatically with the J2SE Runtime Environment. But note the following:

  • Compatibility: The release of Java Web Start that comes with this JDK/JRE can be run on SDK/JRE 1.2.2 or later. It will not work with SDK/JRE 1.1.x or earlier.
  • Upgrading from Previous Versions: If you have a previous release of Java Web Start, do not uninstall it. Uninstalling it will cause the download cache to be cleared, and all previously installed Java Web Start applications will have to be downloaded again. This new release will overwrite previous installations and automatically update browsers to use this new release. The configuration files and program files folder used by Java Web Start have not changed, so all your settings will remain intact after the upgrade.
  • Using Java Web Start with Netscape 6.x/7.x: For Netscape 6.x/7.x users, setup the Java Web Start MIME type (JNLP) in the Edit->Preferences->Navigator->Helper Applications section. The file extension is jnlp; MIME Type is application/x-java-jnlp-file. It should be handled by the javaws executable file in your Java Web Start directory. Also note that, due to a problem with the JavaScript in Netscape 6.x/7.x, you must use the non-JavaScript version of the demos page

Installation Notes

J2SE Runtime Environment 5.0
Linux (32-bit)

 

Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.