Application server startup scripts typically pass their home directory as a property on the command line to their Java processes. Java properties are prefixed with a -D and are a means of passing a parameter to any Java code running in the process, such as the application server's own code or the ENOVIA Live Collaboration Server running in RIP mode. For example, if the Java command line contains: -Dtomcat.home=${TOMCAT_HOME} then the Java process is a Tomcat application server and its home directory can be found in the TOMCAT_HOME environment variable. This is the home directory for the application server and can be used to locate startup scripts and configuration files, as required in "Additional ENOVIA Live Collaboration Server Configuration Troubleshooting," Collecting Logs and Core Files. The following table shows a list of properties that can be used to locate a Java process:
The java.rmi.activation.port property is in the following format: -Djava.rmi.activation.port=1099 It shows the ENOVIA Live Collaboration Server port, which is useful when using the RMI Gateway with multiple ENOVIA Live Collaboration Servers running on different ports. When running in RMI mode, a process called rmid is loaded and used to start ENOVIA Live Collaboration Servers on demand. Its command line includes the JVM options that will be passed to any ENOVIA Live Collaboration Server it creates and the port on which the ENOVIA Live Collaboration Server is listening. |