Print-friendly Version

Prior to installing the Java 2 SDK, you should insure that you have installed the full set of required patches needed for support of this release. See Solaris Patch Installation before proceeding. See also the note about the location of the Java HotSpot libjvm.so files.

The Java 2 SDK, Standard Edition, v1.3.0_03, is available in two installation formats.

• A self-extracting binary file which can be used to install the Java 2 SDK in a location chosen by the user. If you are using this file, see Self-Extracting Binary below.

• A .tar.Z file containing Solaris packages to be installed with the pkgadd utility. If you are using this bundle, see Installation of Packages below.

Installation of Self-Extracting Binary

Use these instructions if you want to use the self-extracting binary file to install the Java 2 SDK. If you want to install Solaris packages comprising the SDK, use Installation of Packages below.

1. Check the download file size to ensure that you have downloaded the full, uncorrupted software bundle:

j2sdk-1_3_0_03-solsparc.bin  26522783  bytes

j2sdk-1_3_0_03-solx86.bin    24694999  bytes

2. Make sure that execute permissions are set on the self-extracting binary:

On SPARC:
chmod +x j2sdk-1_3_0_03-solsparc.bin

On x86:
chmod +x j2sdk-1_3_0_03-solx86.bin

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

4. Run the self-extracting binary.

The files will be installed in a subdirectory called j2sdk1_3_0_03. After the installation is finished, the subdirectory can be renamed as desired.

Use these instructions if you want to use the pkdadd utility to install the Solaris packages for the Java 2 SDK. If you want to use the self-extracting binary file instead, see Self-extracting Binary above.

1. Check the download file size to ensure that you have downloaded the full, uncorrupted software bundle:

j2sdk-1_3_0_03-solsparc.tar.Z  37833558   bytes

j2sdk-1_3_0_03-solx86.tar.Z    35259611   bytes

2. Extract the contents of the compressed tar file:

On SPARC:
zcat j2sdk-1_3_0_03-solsparc.tar.Z | tar -xf -

On x86:
zcat j2sdk-1_3_0_03-solx86.tar.Z | tar -xf -

This will create four packages (SUNWj3dmo, SUNWj3dev, SUNWj3man, and SUNWj3rt) along with the product license, README, and other release documentation.

Note: The package for the J2SE demos has changed names. In this release it is named SUNWj3dmo; previously it was named SUNWj3dem.

3. Become root:

su

4. Run the pkgadd command to install the packages:

pkgadd -d . SUNWj3rt SUNWj3dev SUNWj3man SUNWj3dmo

This will install the SDK into /usr/j2se; see the pkgadd(1) and admin(4) man pages for information on installing the SDK in an alternate location.

5. Delete the tar files and extracted directories.

6. Exit the root shell.

• Set the NPX_PLUGIN_PATH environment variable to the directory containing the javaplugin.so file.

  On SPARC platforms, the default location of javaplugin.so for the package installation is in this directory: /usr/j2se/jre/plugin/sparc/ns4/

  On Intel platforms, the default location is this directory: /usr/j2se/jre/plugin/i386/ns4/

• For Netscape 6 browsers: Create a symbolic link in the Netscape plugins directory

  If (and only if) you are using Netscape 6, you will need to create a symbolic link in the Netscape plugins directory to the path of the libjavaplugin_oji.so file. In the package installation of J2SE 1.3.1 Beta, this file is located at /usr/j2se/jre/plugin/<arch>/ns600/libjavaplugin_oji.so, where <arch> is either sparc or i386, depending on your platform. For example:

  cd ${NETSCAPE6}/bin/plugins
  ln -s ${JRE}/plugin/sparc/ns600/libjavaplugin_oji.so .
  

• For all Netscape browsers: Start your Netscape browser, or restart it if it is already up.

• For all Netscape browsers: Restart your browser a second time.

  Restarting the browser a second time is necessary because of bug 4358142.

  Location of libjvm.so files

  If you use the Invocation API to launch an application directly rather than using the Java application launcher, be sure to use the correct paths to invoke the Java HotSpot Client VM or Java HotSpot Server VM as desired. The path within the SDK to the Java HotSpot Client VM is

  jre/lib/sparc/client/libjvm.so (on SPARC)
  jre/lib/i386/client/libjvm.so (on x86)

  The path to the Java HotSpot Server VM is

  jre/lib/sparc/server/libjvm.so (on SPARC)
  jre/lib/i386/server/libjvm.so (on x86)

  The Exact VM and Classic VM are no longer part of the Java 2 platform, and legacy code that uses the Invocation API to launch an application based on old paths to the Exact or Classic VMs will not work.

  Selecting the Default Java Platform

  The /usr/java symbolic link is used to define the default Java environment on a Solaris system when more than one Java environment is installed. Currently, JDK 1.1 is installed in /usr/java1.1, J2SE 1.2.2 is installed in /usr/java1.2, and J2SE 1.3.0 is installed in /usr/j2se.

  Prior to the Solaris 8 release, the /usr/java symbolic link pointed to /usr/java1.1 if both JDK 1.1 and J2SE 1.2.2 were installed. Starting wi th the Solaris 8 release, the /usr/java symbolic link points to /usr/java1.2 by default if both JDK 1.1 and J2SE 1.2.2 are installed.

  Since there are symbolic links in /usr/bin (also known as /bin ) that use /usr/java (for example, /usr/bin/java refers to /usr/java/bin/java), this /usr/java link can change the default Java installation seen by most users. Many Java applications run on any of J2SE 1.3.0, J2SE 1.2.2, or JDK 1.1, but users and applications might want to be selective about which Java installation they use.

  Java users that want to use JDK 1.1 should add /usr/java1.1/bin to their PATH settings before /usr/bin. Java users that want to use J2SE 1.3.0_03 should add /usr/j2se/bin to their PATH settings before /usr/bin. Also, depending on the situation, you might need to make changes to other environment variables such as CLASSPATH, LD_LIBRARY_PATH, or JAVA_HOME, although none of these environment variables are required.

  It is possible for root users to make J2SE 1.3.0_03 the default Java platform by modifying the /usr/java symbolic link to point to /usr/j2se. However, changing the symbolic link in this manner may cause problems for some Java applications that are expecting to use earlier versions of the Java platform. See the online compatibility documentation for incompatibilities between J2SE 1.2 and J2SE 1.3.

  http://java.sun.com/j2se/1.3/compatibility.html