J2SE Runtime Environment Installation Instructions
Java Plug-in Browser Registration Instructions
Java Web Start Installation Notes
J2SE Runtime Environment 5.0 is supported on the Solaris 8, Solaris 9 and Solaris 10 operating systems. For supported processors, desktop managers, browsers, locales and disk space requirements, see System Configurations.
Prior to installing the J2SE Runtime Environment, you should ensure that you have installed the full set of required patches needed for support of this release. Recommended and required patches are available for download from the SunSolve website.
See also Solaris Font Package Requirements for information about which font packages should be on your system.
To install the 32-bit JRE, follow the installation instructions below.
To install the 64-bit JDK on a SPARC, AMD64, or EM64T platform, you must follow a two-step procedure: Install the 32-bit JDK using the installation instructions below, and also install the supplemental support for 64-bit operation by following the 64-bit Installation Instructions.
Note that Java Plug-in and Java Web Start are automatically installed with the JRE, but Java Plug-in needs to be registered with the browser. Instructions for doing so can be found below at Java Plug-in Browser Registration Instructions.
Note: For any text on this page containing the following notation, you must substitute the appropriate JRE update version number (such as "_01") for the notation.
For example, if you are installing update 1.5.0_01, the following command:
chmod +x jre-1_5_0 <update>-solaris-sparc.sh
chmod +x jre-1_5_0_01-solaris-sparc.sh
1. Download the self-extracting binary and check the 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 JRE.
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 on the self-extracting binary:
On SPARC processors:
chmod +x jre-1_5_0 <update> -solaris-sparc.sh
On x86/AMD64/EM64T processors:
chmod +x jre-1_5_0 <update> -solaris-i586.sh
3. Change directory to the location where you would like the files to be installed.
The next step installs the JRE into the current directory.4. Run the self-extracting binary.
Execute the downloaded file with the path prepended to it. For example, if the file is in the current directory, prepend it with " ./" (necessary if " ." is not in the PATH environment variable):
On SPARC processors:
./jre-1_5_0 <update> -solaris-sparc.sh
On x86/AMD64/EM64T processors:
./jre-1_5_0 <update> -solaris-i586.sh
The binary code license is displayed, and you are prompted to agree to its terms.
The JRE files are installed in a directory called jre1.5.0 <update> in the current directory.
Note about System Preferences - When run by a non-root user, the installation is considered a "private" or non-system install. During a private install, the installation script configures Java such that the backing store for the java.util.prefs package is created inside the JRE's installation directory. If the JRE is installed this way on a network-mounted drive, all Java applications, libraries, and preferences can be exported for sharing, so that the same version of the Java runtime environment and preferences are available to other machines.
As an alternative, when root users run the installation script, preferences are stored in the /etc directory. This is similar to installing the Java packages for Solaris, and this installation is "public" or system specific. Installing Java in this manner allows all versions of Java that support the java.util.prefs package to share the same set of preferences. In other words, in a public/system install, preferences set by a user running JRE 5.0 will also be available when the system is upgraded to JRE 6.
See the Preferences API documentation for more information about preferences in the Java platform.
You must register the Java Plug-in component with Netscape or Mozilla for the Plug-in to work. Instruction to do this can be found at Manual Java Plug-in Registration for Solaris.
Java Plug-in is supported for Netscape 7.x, plus Mozilla 1.x and higher on Solaris 8, 9, and 10. Java Plug-in also supports Netscape 4.x, but only on Solaris 8. Java Plug-in no longer works with Netscape 6.x. Java Plug-in may work with other non-supported browsers. If you are using a non-supported browser, check your browser documentation for details on registering the Java Plug-in.
This JRE release includes Java Web Start; Java Web Start is installed automatically with the JRE. 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: 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 changed, but all your settings will remain intact after the upgrade, since Java Web Start will translate your settings to the new form.
- 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
pkgaddutility use: If you use the
pkgaddutility to install the Solaris packages for JDK/JRE 5.0, a symbolic link for
../j2se/jre/javaws/javawswill be created in
Note About Location of Java VM Library Files: If you want to use the Invocation API to launch an application directly rather than using the Java application launcher, please see Location of VM Library Files (libjvm.so) .
J2SE Runtime Environment 5.0
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.