When you upgrade a domain to WebLogic Server 8.1, consider upgrading your JVM to JRockit. WebLogic JRockit is a JVM designed for running server-side applications in Windows and Linux running on Intel architectures. For server-side applications, JRockit has these advantages over other virtual machines:

 It employs adaptive optimization, which detects and removes bottlenecks in the deployed APPLICATION.

 It is designed specifically for the special requirements of server-side applications, which tend to be parallel and thread-intensive, to RUN for longer periods of time, and not to use graphical interfaces.

 You can monitor JRockit using the WebLogic Server Administration Console.

 Steps to change:

 In the server start scripts, set JAVA_HOME (or equivalent) shell variables to point to the JRockit root directory. For example, change:

@rem Set user-defined variables.

set JAVA_HOME=WL_HOMEjdk131

 where WL_HOME is the WebLogic Server 7.0 installation directory, to

@rem Set user-defined variables.

set JAVA_HOME=WL_HOMEjrockit81_141_02

 where WL_HOME is the WebLogic Server 8.1 installation directory.

 Change the domain’s config.xml to use the JRockit javac.exe. For example, change

JavaCompiler="WL_HOMEjdk131binjavac"

 where WL_HOME is the WebLogic Server 7.0 installation directory, to

JavaCompiler=WL_HOMEjrockit81_141_02binjavac”

where WL_HOME is the WebLogic Server 8.1 installation directory.

 Remove from server start scripts any switches specific to the Sun JVM. For example, from the start command:

ECHO on "%JAVA_HOME%binjava" -HOTSPOT .... weblogic.Server delete “-hotspot”.

When you upgrade a domain to WebLogic Server 8.1, consider upgrading your JVM to JRockit. WebLogic JRockit is a JVM designed for running server-side applications in Windows and Linux running on Intel architectures. For server-side applications, JRockit has these advantages over other virtual machines:

 It employs adaptive optimization, which detects and removes bottlenecks in the deployed application.

 It is designed specifically for the special requirements of server-side applications, which tend to be parallel and thread-intensive, to run for longer periods of time, and not to use graphical interfaces.

 You can monitor JRockit using the WebLogic Server Administration Console.

 Steps to change:

 In the server start scripts, set JAVA_HOME (or equivalent) shell variables to point to the JRockit root directory. For example, change:

@rem Set user-defined variables.

set JAVA_HOME=WL_HOMEjdk131

 where WL_HOME is the WebLogic Server 7.0 installation directory, to

@rem Set user-defined variables.

set JAVA_HOME=WL_HOMEjrockit81_141_02

 where WL_HOME is the WebLogic Server 8.1 installation directory.

 Change the domain’s config.xml to use the JRockit javac.exe. For example, change

JavaCompiler="WL_HOMEjdk131binjavac"

 where WL_HOME is the WebLogic Server 7.0 installation directory, to

JavaCompiler=WL_HOMEjrockit81_141_02binjavac”

where WL_HOME is the WebLogic Server 8.1 installation directory.

 Remove from server start scripts any switches specific to the Sun JVM. For example, from the start command:

echo on "%JAVA_HOME%binjava" -hotspot .... weblogic.Server delete “-hotspot”.