Sun Java Solaris Communities My SDN Account Join SDN
 
JRE Installation Notes 1.4.0

Java 2 Runtime Environment Installation Instructions

 

Installation Notes

Java 2 Runtime Environment, Standard Edition
Version 1.4.0
Solaris Operating Environment

System Requirements

The Java 2 Runtime Environment, Standard Edition, v. 1.4.0 is intended for use on Solaris 2.6, Solaris 7, and Solaris 8 operating environments.

Prior to installing the Java 2 Runtime Environment, 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 Solaris Font Package Requirements for information about which font packages should be on your system.

Installation Instructions

The Java 2 Runtime Environment (J2RE), Standard Edition, v1.4.0 comes in the form of a self-extracting binary file. Follow the instructions below to install the J2RE.

At the end of this file, see also

Java Plug-in product installation instructions
Java WebStart product installation instructions

64-bit support for the Java 2 Runtime Environment is available for SPARC processor platforms in a separate download. Installation instructions for 64-bit support are in a separate document.

1. Check the download file size

Check the large file that you downloaded (or that you created by concatenating the small pieces) to ensure that it is the correct size:

j2re-1_4_0-solsparc.sh     22634498 bytes

j2re-1_4_0-solx86.sh       20461750 bytes

If the file size doesn't match, it probably means the file was corrupted during download. In that case, try downloading again.

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

On SPARC:
chmod +x j2re-1_4_0-solsparc.sh

On x86:
chmod +x j2re-1_4_0-solx86.sh

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

4. Run the self-extracting binary.

A directory called j2re1.4.0 will be created in the current directory.


Java Plug-in Product Installation Instructions

For documentation on the Java Plug-in product, see

http://java.sun.com/j2se/1.4/docs/guide/plugin/index.html


Follow these steps to install the Java Plug-in product:

1. For Netscape 4.x browsers: Set the NPX_PLUGIN_PATH environment variable to the directory containing the javaplugin.so file. (This step is not necessary if you use only Netscape 6.x browsers.)

On the SPARC operating environment, the default location of javaplugin140.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/

 

1. The location of the Plug-in (javaplugin.so) should be give with an absolute path—not relative to the installation location of the JRE.

2. Setting NPX_PLUGIN_PATH will override the default search path used by the browser. Therefore any plugin directories that the browser currently searches for plugins should also be added to the path.

2. For Netscape 6 browsers: Use regxpcom tool provided by Netscape to register Java Plug-in 1.4.

 

Notes:

  1. Before you run regxpcom, as described below, first shut down the browser.
  2. setenv LD_LIBRARY_PATH <Netscape 6>:$LD_LIBRARY_PATH

If you do not add Netscape to your LD_LIBRARY_PATH you are likely get an error when you run regxpcom. The message will say that Open failed: No such file or directory.

If and only if you are using Netscape 6, you will need to use regxpcom provided by Netscape to register the libjavaplugin_oji140.so file. In the package installation of 1.4.0, copies of this file are located at /usr/j2se/jre/plugin/<arch>/ns600/libjavaplugin_oji140.so and /usr/j2se/jre/plugin/<arch>/ns610/libjavaplugin_oji140.so, where <arch> is either sparc or i386, depending on your platform. For example:

cd ${NETSCAPE6}/bin

If you use a Netscape 6.0x browser:

regxpcom ${JRE}/plugin/sparc/ns600/libjavaplugin_oji140.so

If you use a Netscape 6.1x browser:

regxpcom ${JRE}/plugin/sparc/ns610/libjavaplugin_oji140.so

After running the regxpcom command you should get a message saying that registration was successful for <jre>/plugin/sparc/ns610/libjavaplugin_oji140.so


If regxpcom does not register the Java Plug-in successfully—i.e., you get a registration-failed message or a core dump—try creating a link to the Java
Plug-in libjavaplugin.so file in the Netscape 6 plugins directory.

cd <Netscape 6>/plugins
ln -s <JRE>/plugin/sparc/ns610/libjavaplugin_oji140.so .

Be sure to include the period at the end.

Note: Only one Java Plug-in can be registered at a time. When you want to use a different version, unregister the one you have and register the new version.

regxpcom -u <absolute path to Java Plug-in libjavaplugin.so file>

Example:

regxpcom -u ${JRE}/plugin/sparc/ns610/libjavaplugin_oji140.so
regxpcom ${JRE}/plugin/sparc/ns610/libjavaplugin_oji141.so

3. For Netscape 4.x browsers, restart your browser twice. For Netscape 6.x browsers, start up your browser.

In Netscape do Help -> About Plug-ins to confirm that the Java Plug-in is loaded.


Java WebStart Installation Instructions

Java RE 1.4.0 includes the Java Web Start product. In the top-level directory you will find a ZIP file named javaws-1_0_1_02-solsparc-int.zip on SPARC platforms and javaws-1_0_1_02-solx86-int.zip on Intel platforms. Move this file to a location where you want to install the Java Web Start product (preferably outside the Java RE installation). Unzip the file. One of the files extracted will be install.sh. Run this script to install the Java Web Start product.



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 processors)
jre/lib/i386/client/libjvm.so (on x86 processors)

The path to the Java HotSpot Server VM is

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

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.