Java Migration

Unlike in the 6.0 release, Java is enabled by default in the Sun Java System Web Server 6.1. In the Sun Java System Web Server 6.1, you can enable and configure Java for every instance of the server. Unlike in the previous 6.0 release which supported an installation-wide configuration of the JDK.

During migration you can choose to install either the JDK that is bundled with Sun Java System Web Server 6.1 (JDK 1.4.2_13) or install a custom JDK. If you install the server with a custom JDK, the javahome setting of the migrated instance refers to the custom JDK path (taken from the javahome setting of the Administration Server). Otherwise the javahome setting points to /bin/https/jdk.

Sun Java System Web Server 6.1 supports the Java Development Kit (JDK) version 1.4 and above. It does not support a standalone Java Runtime Environment (JRE).

In the Sun Java System Web Server 6.1 this data is stored in the server.xml file.

The JAVA element in the new server.xml file contains the JDK configuration information copied from the start-jvm file of the migrated instance.

The JVMOPTIONS element in the new server.xml file contains the JVM options information from the jvm12.conf file of the migrated instance.

If the previous version of your server was configured to use JDK 1.4.1 or above, the NSES_JDK path from the server’s start-jvm file is copied into the Sun Java System Web Server 6.1 server.xml file, otherwise, the JDK path points to server-root/bin/https/jdk, which is the default JDK path in Sun Java System Web Server 6.1.

For information about the mapping of the start-jvm and jvm12.conf files with the server.xml file in Sun Java System Web Server 6.1, refer to the Sun Java System Web Server 6.1 Administrator’s Configuration File Reference.