Optional Static Content Server

It is recommended that a static content server (i.e., a "reverse hosting server") be implemented for a production instance of the ENOVIA Live Collaboration Server. This is a simple Web server front end (using products such as Apache or IIS) that is configured to serve all static content and then pass any dynamic requests on to the Application Server. This is especially crucial if there is WAN access to the ENOVIA products.

Related Topics
Java Development Kit
Installing a WebLogic Server
Installing a Web or Application Server

The importance of a front-end web reverse hosting server can be shown by breaking down the requests from frequently-used application pages. For example, when logging into an ENOVIA product from emxLogin.jsp, there are about 11 requests for static content (depending on the version used) and only 1 request for dynamic content generated. Loading or refreshing the primary (content) page of the application (emxNavigator.jsp) results in approximately 7 HTTP requests for dynamic content and the actual number of requests for static content depends upon the browser configuration for browser caching:

  • "Automatic" browser caching generates about 10 requests.
  • "Automatic" browser caching on startup generates about 52 requests.
  • "Every page" browser caching generates about 164 requests.

The default is "Automatic," however, previous versions of ENOVIA products recommended "Every page" to ensure that the newest version of any page was used. The "Automatic" setting is the recommendation for Version 10.7 and higher.

For more information, refer to "Using a Web server in addition to an application server".