Key Live Collaboration Environment Variables

The configuration checker evaluates key 3DSpace environment variables that can be easily overlooked.

Setting environment variables appropriately for system-wide use can improve performance dramatically. These variables may have been set originally by an ENOVIA engineer, but during upgrades of an app server the variables may be lost because a new app server startup script is used.

See Also
System Scaling
Evaluation Details

Check the app server's startup script (see the App Server table) for the environment variables or for a script that gets executed that may set them externally.

A good tip for checking what is being set is to locate the line in the script files that starts the JVM (usually it's near the end and begins with java-install-path/bin/java) and insert a line that pipes the environment to a file.

Example for Linux:
env > env.fil
Example for Windows:
set > env.fil

Start the app server and edit the env.fil file. Search for the environment variables listed in the 3DSpace environment variable table.

The MATRIXHOME environment variable should be noted since most traces and scripts are found using this path.

A good practice to ensure that the environment variables are set is to create a script or batch file that contains them and call the script directly from the app server startup script.

In Windows, environment variables are checked as follows: the enovia.ini file is checked first; if the variable does not exist then the environment is checked. If still not found, internal defaults are used.