Installing a Web or Application Server

The ENOVIA Live Collaboration Server uses J2EE/RMI technology and works in conjunction with a Web Application Server.

Related Topics
Java Development Kit
Installing WebSphere
Installing a WebLogic Server

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:

  1. Simple Web server—When using ENOVIA Live Collaboration Server, a simple Web server may be used for custom Java client applications written with the ENOVIA Studio Customization Toolkit that are not JSP-based. One or several simple Web servers may also be used to front-end an enterprise's Website. Refer to "Optional Static Content Server" for more information.

  2. A JSP/servlet-enabled Web or Application Server —When servlets and JSP applications will be used, the Web server must be JSP- and servlet- enabled. All ENOVIA products require at least this level of Web server. ENOVIA-specific configuration is required.

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:

  1. Installing a supported Web server using its installation guide and the guidance provided below. Most supported Application Servers include a Java Development Kit, which can be used by ENOVIA Live Collaboration as well, but in some cases you'll need to install it.
  2. Configuring the Application Server as required.
  3. Making sure the Application Server is operational before installing the Live Collaboration Server.

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 Sizes

When 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


WebLogic

Refer to the following sources:


  • For WebLogic Server releases 9.0 and higher--A server instance uses a self-tuned thread pool. The best way to determine the appropriate pool size is to monitor the pool's current size, shrink counts, grow counts, and wait counts. See Thread Management in the WebLogic documentation. Tuning MDBs are a special case. See Chapter 11, Tuning Message-Driven Beans, in the WebLogic documentation.
  • For releases prior to WebLogic Server 9.0--In general, the number of connections should equal the number of threads that are expected to be required to process the requests handled by the pool. The most effective way to ensure the right pool size is to monitor it, and to make sure it does not shrink and grow. See How to Enable the WebLogic 8.1 Thread Pool Model in the WebLogic documentation.
  • For more information including configuration details, refer to http://edocs.bea.com/common/docs100/install/index.html.