Interface for Downstream Installers, E4All, and other Automated Installers

For downstream installers to be able to add their files into a previously installed ENOVIA kernel installation, both the ENOVIA Live Collaboration Server and ENOVIA Studio Modeling Platform setup programs deposit a file named enovia.install into the top-level directory of the respective installation to describe where various categories of files are to be found.

Related Topics
Installing ENOVIA Live Collaboration Server
Uninstalling ENOVIA Live Collaboration Server
Upgrading the Database After Installing a New Version of ENOVIA Live Collaboration

Internal directory structure defined in enovia.install

Downstream installers must deposit their files in the correct locations. In order to do this, they must do all of the following:


  • Request the kernel install directory as part of their installation process.
  • Use the directories specified in the enovia.install file, which can be found in the top-level kernel installation directory:
  • SERVERHOME (UNIX) or SERVER_INSTALL (Windows) (ENOVIA Live Collaboration Server)
  • ENOVIAHOME (UNIX) or ENOVIA_INSTALL (Windows) (ENOVIA Studio Modeling Platform)
  • Construct the file target location based on the retrieved entries. The following are some key paths that may need to be updated:
 

Old Path (hard-coded)

New Path (dynamically generated)
MQL Command server\bin\winnt\mql.exe <MQL_COMMAND>
Java Properties Path server\java\properties\ <MANAGED_PATH>\properties\
Managed Path server\managed\ <MANAGED_PATH>\
Staging Path server\STAGING\ematrix\ <STAGING_PATH>\
Jar Path server\java\lib\ Either:<JAVA_COMMON_PATH>\ or <JAVA_SERVER_PATH>\
Apps Path studio\Apps\ <APP_INSTALL_PATH>\

The enovia.install file provides both necessary file names and absolute paths.

Example enovia.install files

The following is an example of a typical server enovia.install file (on Windows):

ENOVIA_INI=C:\enoviaVERSION\server\PLATFORM\code\bin\enovia.ini   
MQL_COMMAND=C:\enoviaVERSION\server\PLATFORM\code\bin\mql.exe   
BIN_PATH=C:\enoviaVERSION\server\PLATFORM\code\bin   
LIB_PATH=C:\enoviaVERSION\server\PLATFORM\code\bin   
JAVA_COMMON_PATH=C:\enoviaVERSION\server\PLATFORM\docs\javacommon   
JAVA_SERVER_PATH=C:\enoviaVERSION\server\PLATFORM\docs\javaserver   
JAVA_CLIENT_PATH=C:\enoviaVERSION\server\PLATFORM\docs\java   
JAVA_CUSTOM_PATH=C:\enoviaVERSION\server\PLATFORM\docs\custom   
MANAGED_PATH=C:\enoviaVERSION\server\managed   
DISTRIB_PATH=C:\enoviaVERSION\server\distrib   
STAGING_PATH=C:\enoviaVERSION\server\STAGING\ematrix   
APP_INSTALL_PATH=C:\enoviaVERSION\server\Apps   
JAVA_CLASSPATH=C:\enoviaVERSION\server\PLATFORM\docs\javacommon;
   C:\enoviaVERSION\server\PLATFORM\docs\javaserver;C:\enoviaVERSION\server\PLATFORM\docs\custom  
JDK_PATH=C:\Java\JDK_VERSION

Note: The Apps directory has been moved from ENOVIA_INSTALL\Apps\ (studio install tree) to SERVER_INSTALL\Apps\ (server install tree).

The following is an example of a typical studio enovia.install file (on Windows):

ENOVIA_INI=C:\enoviaVERSION\studio\PLATFORM\code\bin\enovia.ini   
BIN_PATH=C:\enoviaVERSION\studio\PLATFORM\code\bin   
LIB_PATH=C:\enoviaVERSION\studio\PLATFORM\code\bin   
JAVA_COMMON_PATH=C:\enoviaVERSION\studio\PLATFORM\docs\javacommon   
JAVA_SERVER_PATH=C:\enoviaVERSION\studio\PLATFORM\docs\javaserver   
JAVA_CLIENT_PATH=C:\enoviaVERSION\studio\PLATFORM\docs\java   
JAVA_CUSTOM_PATH=C:\enoviaVERSION\studio\PLATFORM\docs\custom   
MANAGED_PATH=C:\enoviaVERSION\studio\managed

Matrix.ini and eMatrix.ini file dependency removed

The Matrix.ini and eMatrix.ini files (formerly located in C:\WINDOWS\) no longer exist. Rather than depending on these file to determine the default ENOVIA core installation root path, downstream installers should pop up a question and explicitly prompt the user to enter the core installation root path.

Studio Version of MQL command removed

Rather than using MQL from the ENOVIA Studio Modeling Platform installation, ENOVIAHOME (UNIX) or ENOVIA_INSTALL (Windows), downstream installers should use MQL from the ENOVIA Live Collaboration Server installation, SERVERHOME (UNIX) or SERVER_INSTALL (Windows), to perform schema installation.