JVM Options for ENOVIA Live Collaboration Servers

For ENOVIA Live Collaboration Servers, JVM settings can usually be retrieved from either the rmireg.sh file (on Unix/Linux) or the rmireg.bat file (on Windows). An exception is when the ENOVIA Live Collaboration RMI service is used. A service called rmiservice will be running at machine startup; each ENOVIA Live Collaboration Server is spawned by this service and the JVM options are kept in the registry.

Related Topics
Calculating Maximum Heap Size
The Java Process Command Line
JVM Options for ENOVIA Live Collaboration Servers on Windows

ENOVIA Live Collaboration Servers are spawned by the rmid (also known as the RMI daemon), a process shipped with the Java Development Kit (JDK). The rmireg.bat, rmireg.sh, or the rmiservice will spawn this process and pass it a list of the JVM options. Each option is prefixed by -C. For example, the initial heap size option would typically be -C-Xms256m. The rmid must know that this is a JVM option in order to be passed to any ENOVIA Live Collaboration Servers it creates.

On Windows, open the rmireg.bat file and find the rmid start line. (Unix is the same except from the "start "RMI Daemon 1099" /min" line is at the beginning.). Then using the settings in JVM Options for Application Servers, verify that the JVM options are at least the minimum value.

Following is a sample rmireg.sh file:

JAVA_OPTIONS="-C-Xss512k -C-Xms256m -C-Xmx256m -C-XX:NewSize=128m
-C-XX:MaxNewSize=128m -C-XX:SurvivorRatio=2" 
JAVA_SECURITY=-Djava.security.policy=/matrix/rmi1100_EPC/<platform>/docs/security/rmid.policy 
${JAVA_PATH}/rmid $1 $JAVA_OPTIONS -J$JAVA_SECURITY -port
1100

-XX settings are for use only with Sun's JVM.