Configuring IBM® HTTP Server

When you have successfully installed IBM® Connections to run on WebSphere® Application Server, you can configure IBM® HTTP Server to handle web traffic.


You have installed and configured the prerequisite software.
  1. IBM® WebSphere® Application Server with the latest version and fixes
  2. IBM® HTTP Server with the latest version and fixes
  3. IBM® Web server plug-ins with the latest version and fixes
  4. IBM® Connections and databases

Configuring the IBM® HTTP server

Depending on whether the IBM HTTP server was installed and configured during Connections installation, some of the these tasks might already have been performed. Configure IBM® HTTP Server to manage web requests to IBM® Connections by following these steps.

Note: When you configure an HTTP server or change the URL used by end users to access Connections, you must also re-configure FileNet® Collaboration Services with the base URL of the HTTP server. See Configuring the FileNet® deployment used by Libraries for more information.

Disabling edge-side-include caching

Edge-side-include (ESI) caching is enabled by default in WebSphere Application Server. You must disable it for IBM Connections. If it is not disabled, it will cause problems for the IBM Connections Surveys application.

To disable ESI caching, in the WebSphere Administration Console, go to Servers > Server Types > Web servers > web_server_name > Plug-in properties > Caching and deselect Enable Edge Side Include (ESI) processing to cache the responses. Save the configuration and synchronize nodes. Then generate the plugin configuration, propagate it, and restart the HTTP server or servers.