You deploy a web application by completing steps 4 through 6 of the General Installation for ENOVIA Live Collaboration Server procedure, and then: ENOVIA Live Collaboration Server installs descriptor files that are used to configure the ENOVIA web application. You can make modifications to these files based on your requirements. Also installed is the WAR Utility, which enables packaging ENOVIA web applications for use in an application server. The WAR Utility creates an EAR (Enterprise Archive) file or a WAR (Web Archive) file, based on the configured descriptor files. The application server then deploys the J2EE archive file. The ENOVIA Live Collaboration Server is generally deployed with the WAR file, using the application server’s administrative tools to complete the configuration. However, since the EAR file contains all information needed for deployment (including the web application name and context root), system administrators of an ENOVIA Live Collaboration Server 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 application; for example, /ematrix. Directory StructureWhen you install ENOVIA Live Collaboration Server, the following directory structure is created: ENOVIA Live Collaboration Server installation directory
¦-- distrib\
¦
¦-- PLATFORM\code\command\
¦
¦-- PLATFORM\resources\warutil\fragment\
¦
¦-- STAGING\
The ENOVIA Live Collaboration Server 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):
|