3DSpace Service installs descriptor files that are used to configure the ENOVIA Web app. You can make modifications to these files based on your requirements. Also installed is the WAR Utility, which enables packaging ENOVIA Web apps for use in an app server. The WAR Utility creates an EAR (Enterprise Archive) file or a WAR (Web Archive) file, based on the configured descriptor files. The app server then deploys the J2EE archive file. The 3DSpace Service is generally deployed with the WAR file, using the app server’s administrative tools to complete the configuration. However, since the EAR file contains all information needed for deployment (including the Web app name and context root), system administrators of an 3DSpace Service may deploy the EAR file instead, so that the context root is already configured. The context root is the relative path to the server root for a particular Web app; for example, /ematrix. More About J2EEDirectory StructureWhen you install 3DSpace Service, the following directory structure is created: 3DSpace Service installation directory
¦-- distrib\
¦
¦-- PLATFORM\code\command\
¦
¦-- PLATFORM\resources\warutil\fragment\
¦
¦-- STAGING\
The 3DSpace Service installation directory (SERVER_INSTALL on Windows or SERVERHOME on UNIX/Linux) uses the path you assigned during the installation. It has the following subdirectories (as well as several others):
|