The Initialization File in Windows

In Windows environments, Studio Modeling Platform apps read the enovia.ini file upon startup to determine the location of the database and to set up the program environment. During Studio Modeling Platform installation on Windows, the enovia.ini file is placed in ENOVIA_INSTALL\studio\win_b64\code\bin\. The apps then access the enovia.ini file as needed during the session. For example, the pixmappath setting is read when the Studio Modeling Platform needs to display a .gif image for the first time. When preferences or the size and location of a window are altered, the changes are written to the enovia.ini file, and it is saved when the session is closed.

A typical Windows version of the enovia.ini file is as follows:

[MATRIX]

MATRIXHOME=C:\enoviaVERSION\studio\

MATRIXINSTALL=C:\enoviaVERSION\studio\

MX_FLASH_PATH=C:\enoviaVERSION\mxcache

PIXMAPPATH=C:\enoviaVERSION\studio\win_b64\pixmaps\app\

COLORPATH=C:\enoviaVERSION\studio\win_b64\code\lib

MATRIXPATH=C:\enoviaVERSION\studio\win_b64\code\bin

MX_TCL_SHLIB=

TCL_LIBRARY=C:\enoviaVERSION\studio\win_b64\tcl85\lib\tcl8.5

TK_LIBRARY=C:\enoviaVERSION\studio\win_b64\tcl85\lib\tk8.5

TMPDIR=C:\DOCUME~1\xxx\LOCALS~1\Temp

MX_DEFAULT_KERNEL=

MX_JVM_DIR=C:\Program Files\Java\jdkVERSION\jre\bin\client\

MX_JDK_DIR=C:\Program Files\Java\jdkVERSION\

MX_JAVAC=C:\Program Files\Java\jdkVERSION\bin\javac.exe

MX_CLASSPATH=C:\Program Files\Java\jdkVERSION\lib;C:\
enoviaVERSION\studio\managed\properties;C:\enoviaVERSION\studio\wi
n_b64\docs\javacommon;C:\enoviaVERSION\studio\win_b64\docs\javaser
ver;C:\enoviaVERSION\studio\win_b64\docs\custom;

LANG=C

When installing the 3DSpace Service to provide access to 3DSpace via Web-based apps, it must be set up as any other 3DSpace client. This means that it must not only have a connection file (MATRIX-R file) and a database alias established, but it also requires an initialization file on Windows. A separate file, also called enovia.ini is created and installed when the 3DSpace Service is installed on Windows platforms. During 3DSpace Service installation, the enovia.ini file is placed in SERVER_INSTALL\win_b64\code\bin\ (previously C:\WINDOWS\). The server’s enovia.ini file can (and should) contain most of the settings that have been added to the enovia.ini file for your Studio Modeling Platform clients.

In Windows environments, it is highly recommended that the enovia.ini file (previously matrix.ini) for the Studio Modeling Platform and the enovia.ini file (previously ematrix.ini) for the 3DSpace Service not be located in the Windows installation directory or C:\WINDOWS. You can choose to put these files in any directory, however enhanced Windows security does not permit applications to modify files in this directory. Also, it is important to note that the enovia.ini file installed with the Studio Modeling Platform and the enovia.ini file installed with 3DSpace Service are not interchangeable and should not be placed in the same directory.

An enovia.ini file directory can be set in any of the following ways:

• Appending the -inidir option to the command lines that run the Studio Modeling Platform apps. For example:

  mql.exe -inidir c:\enovia

  For details on appending options, see Command Line Options.

• When installing 3DSpace Service as a Windows service, the directory can be set with the RMIService.exe config option. For example:

  RMIService.exe -config "3DSpace Service"
  -inidir c:\enovia

  For details, see Reconfiguring the 3DSpace Service Windows Service in Live Collaboration - Server Installation Help.

• Setting the Windows environment variable, ENOVIAINIDIR. For details, see "Typical Environment Variables".
• When developing a custom Studio Customization Toolkit app, you can call the static method, MatrixSession.etIniDirPath(PathToIni), to set the directory. This must be done before any other Studio Customization Toolkit call is made.
• When running a custom Studio Customization Toolkit app based on eMatrixServletRMI or when using any Java based app server (e.g. Tomcat), you can set the directory using the JAVA_OPTS: “-Denovia.inidir=PathToIniDir.” For example:

  java.exe -Denovia.inidir=c:\enovia myApp

  The JAVA_OPTS must also be applied to the matrix.util.ComputedClassPath. If you are running the RMI service in a command window (rmireg.bat), the JAVA_OPTS must be applied to rmid.exe using “-C-Denovia.inidir=PathToIniDir.”

Since copies of the enovia.ini files can exist in more than one location on the same machine, the system uses a lookup order to determine which files to use. This lookup order is used to determine which file to use. It is not used to determine which values in that file to use.

The following table lists the lookup order. The system attempts to use the directory defined by the first method on the list. If no directory is defined, it moves on to the next method down to the default directory, C:\WINDOWS. If the directory defined by a method does not exist, the system will NOT move to the next method.

Studio Modeling Platform Apps	Web Server	3DSpace Service	Studio Customization Toolkit App
			Set directly to MatrixSession
-inidir Argument.	Java Options	For Windows Service: RMIService.exe config (-inidir). For Rmireg.bat: Java Options enovia.inidir	Java Options enovia.inidir.
Environment Variable	Environment Variable	Environment Variable	Environment Variable
Executable Location	eMatrix.jni.dll or eMatrix.net.dll location	eMatrix.jni.dll location	eMatrix.jni.dll or eMatrix.net.dll location
C:\WINDOWS	C:\WINDOWS	C:\WINDOWS	C:\WINDOWS