ENOVIA supports only those Application Server versions listed in "Prerequisites" in the Program Directory for a given release. If a newer version is available that is not explicitly stated as qualified for ENOVIA Live Collaboration, it is highly recommended NOT to use it unless otherwise stated for that specific platform. If a qualified version includes a patch level (fix level, MP, etc.), it is highly recommended to use this patch level although it is possible to use a higher patch level than the qualified level. A patch level older than the level qualified should NOT be used. Higher patch levels can be used as exact patch levels may not be available at the time of deployment. Higher patch levels can improve security and/or performance and may be beneficial. While most patch levels do not impact the functionality or stability of the system, it is possible for a higher patch level to cause interoperability issues. If this is the case, ENOVIA may recommend installing a higher patch level or reverting back to the qualified patch level. Note: After every type of system change, such as a JVM patch or Application Server service pack installation, it is highly recommended to check all configuration files (such as jvm.cfg, rmireg.sh, etc.) to ensure that no important settings were changed. There are different levels of servers that may be used for internet access, and each may be used with the ENOVIA Live Collaboration Server as follows:
This section describes how to set up and configure the qualified Application Servers required for level 2 use (above). The main tasks involved in installing and configuring a Web or Application Server are:
After confirming that the Application Server is operational, installing the ENOVIA Live Collaboration Server by following the instructions in Preparing to Install the ENOVIA Live Collaboration Server. Note: Since File Collaboration Server and PDF rendering functions require access to Live Collaboration native code libraries, you must install the ENOVIA Live Collaboration Server on each Application Server that will be used for ENOVIA Live Collaboration access. Tuning Pool SizesWhen many (i.e., 20 or more) users try to check in files simultaneously, FCS errors can occur. To avoid this, be sure to tune pool sizes (e.g., for JDBC connections, Stateless Session EJBs, and MDBs) to maximize concurrency for the expected thread utilization. Sun Java System Application Server
Tomcat
WebLogicRefer to the following sources:
WebSphere
|