All settings may be retrieved using the startup files listed in the Application Server table. For all application servers, except for Sun Java System Application Server, edit the startup script and find the JAVA_HOME variable in the file. This will point to the
java.exe (it may be in a bin or jre directory beneath this path). Run this java.exe from a command line with the -version argument to retrieve the Java version, and use the value in the above table to verify that the number is not less than the minimum value.
The configuration checker checks for obsolete versions of eMatrixServletXXX.jar by comparing Java and native versions of eMatrixServletXXX.jar. Any obsolete versions will generate a Critical error.
The JVM mode may not be obvious since most application servers leave it at the default value. The available modes for the Sun JVM can be,
for example, classic, client or server. Server mode must be the mode
used for all configurations.
There are two ways to set the JVM mode:
- Make the first parameter in the Java command line
-server. Then edit the jvm.cfg file pointed to by the JAVA_HOME variable and make -server the first line after the comments in the file. If your platform does not have jvm.cfg, refer to your
JVM documentation for the location of -server. It can be assumed that if the Java version is correct then the JVM
version should also be compatible. However, on Windows particularly,
care must be taken to ensure that there are no other jvm.dlls in the
Windows or Windows system directories that could cause a JVM mismatch
and shut down the JVM.
The JVM version and mode is actually displayed in the startup messages
for the Sun Java System Application Server.
If the JVM is controlled by the application server, the configuration
checker may not be able to detect the presence of -server and it will
generate an error. If this situation occurs, verify that your application
server does set -server and ignore the error in mxAudit.log.