ENOVIA Live Collaboration Server Environment Settings

Environment Setting	Description
`MX_NUL_COURTESY_MSG`	When a user attempts to use the ENOVIA Live Collaboration Server without an appropriate product assigned, an ENOVIA Live Collaboration product is automatically assigned to that user as a courtesy. When this variable is set to true (by default), a message is also sent to mxtrace.log indicating that an ENOVIA Live Collaboration product has been assigned to the user as a courtesy.
`MX_BOS_ALLOW_SHARED_CONTEXT`	May be set to TRUE in order to allow processing of a session that is shared by multiple threads. When this occurs, a message stating `Session SESSION_ID in use by multiple threads` is written to the mxtrace.log file. This message is only a warning and the threads will continue processing. By default, `MX_BOS_ALLOW_SHARED_CONTEXT` is set to false, which means that a session cannot be shared by multiple threads. The same message, `Session SESSION_ID in use by multiple threads`, is written to the mxtrace.log file but this time, the second thread using the shared session ID stops processing. For an explanation of context object problems, see the "Context Object User Access" topic in the "Creating a Sample Server-side Application" chapter of the ENOVIA Studio Modeling Platform Programming Guide.
`MX_BOS_ROOT`	This is the same as the WWW document root directory.
`MX_BOS_WORKSPACE`	This is the directory below `$MX_BOS_ROOT` that is created by the ENOVIA Live Collaboration Server installation. This directory is used as a location for file access for all logged on users. Subdirectories are created for users as they log into the server, and automatically removed when they log out. The value is `matrix/workspace`.
`MX_CONNECTION_POOL_SIZE`	Dictates how many database connections are pre-initialized. This helps in cases where a multi-threaded ENOVIA Studio Customization Toolkit application tries to initiate multiple contexts at the same time. Without the pre-initialized database connections configured, connect failures may occur if the network or database are slow to respond. The default value is determined by the Java heap size selected during installation of the ENOVIA Live Collaboration Server (on UNIX, that is small = 10, medium = 20, large = 30). For more information on this setting, see System Scaling.
`MX_TRACE_FILE_PATH`	Sets the location where the `mxtrace.log` file is generated. Defaults to `$SERVER_INSTALL\logs`.
`MX_ABORT_DANGLING_TRANSACTION`	Set to TRUE. See "Optional Settings" for a description of this setting.

On UNIX, these settings are added as environment variables in the ENOVIA Live Collaboration Server startup script.

On Windows, an enovia.ini file for the ENOVIA Live Collaboration Server is created (or updated) with the settings shown above. A typical Windows enovia.ini file is shown below:

[MATRIX]
MX_BOS_ROOT=C:\enoviaV6R2012\server\   
MX_BOS_WORKSPACE=workspace   
MX_TRACE_FILE_PATH=C:\enoviaV6R2012\server\logs  
MX_ABORT_DANGLING_TRANSACTION=true   
MX_SESSION_TIMEOUT=60   
MX_BOS_ALLOW_SHARED_CONTEXT=false   
MATRIXHOME=C:\enoviaV6R2012\server\   
MATRIXINSTALL=C:\enoviaV6R2012\server\   
MX_FLASH_PATH=C:\enoviaV6R2012\server\mxcache   
PIXMAPPATH=C:\enoviaV6R2012\server\intel_a\pixmaps\app\   
COLORPATH=C:\enoviaV6R2012\server\intel_a\code\lib   
MATRIXPATH=C:\enoviaV6R2012\server\intel_a\code\bin   
MX_TCL_SHLIB=   
TCL_LIBRARY=C:\enoviaV6R2012\server\intel_a\tcl85\lib\tcl8.5   
TK_LIBRARY=C:\enoviaV6R2012\server\intel_a\tcl85\lib\tk8.5   
TMPDIR=C:\DOCUME~1\<user>\LOCALS~1\Temp   
MX_DEFAULT_KERNEL=
MX_JVM_DIR=C:\Java\JDK_VERSION\jre\bin\client\   
MX_JDK_DIR=C:\Java\JDK_VERSION\   
MX_JAVAC=C:\Java\JDK_VERSION\bin\javac.exe   
MX_CLASSPATH=C:\Java\JDK_VERSION\lib;C:\enoviaV6R2012\server\
managed\properties;C:\enoviaV6R2012\server\intel_a\docs\java?
common;C:\enoviaV6R2012\server\intel_a\docs\javaserver;C:\eno?
viaV6R2012\server\intel_a\docs\custom;   
MX_CHARSET=UTF8   
LANG=C   
NLS_LANG=_UTF8   
MX_CONNECTION_POOL_SIZE=20   
MX_MEMORY_SYSTEM_LIMIT=640m