The Java Runtime Environment

When installing on Linux and UNIX servers, the installation program prompts you to install the JRE or to provide a valid path to a JRE. When installing on Windows, the installation program automatically installs the JRE without prompting you.

On Solaris 10 servers, the installation script prompts you to use JRE v1.4.2 that is already installed in /usr/j2se. You can choose to use this version of the JRE rather than installing a new version.

If you are installing on a Red Hat Linux or a SUSE Linux server, the installation script searches your machine for an instance of the JRE in the default location.

• If the JRE is not installed in the default location, you must install the JRE.

• If the installation program finds the JRE in the default location, you can choose whether or not to reinstall the JRE.

If you are installing on a Solaris OS, IBM AIX, or HP-UX server and you chose not to install the JRE, the installation script prompts you to provide a path to a valid JRE. Then the installation script verifies that the JRE is supported.

• If the JRE is not supported but has a higher version number than the versions that are supported, the installer warns you that the JRE is not supported and asks if you want to continue.

• If you specified a version of the JRE that is supported by the N1 Service Provisioning System 5.1, the installation script sets the JRE_HOME variable to the JRE that you specified. The installation script also creates a symbolic link, N1SPS5.1-home/common/jre, which points to the JRE directory. N1SPS5.1-home is the home directory of the N1 Service Provisioning System 5.1. By creating a symbolic link, the N1 Service Provisioning System 5.1 applications use the JRE without changing its location, which other applications might depend upon.

You should install the bundled JRE only once for each machine. For example, if you are installing the Master Server, a Local Distributor, and the CLI Client on the same machine, you should install the JRE with the Master Server, but not with the Local Distributor or the CLI Client.