Configure Apache HTTP Server V2.0

This topic describes how to change configuration settings for Apache HTTP Server Version 2.0.

(dist) After you install the web server plug-ins, we can use the Web Server Plug-ins Configuration Tool to configure a web server plug-in.

This topic describes how to configure the Apache HTTP Server Version 2.0 Web Server. Other procedures in Edit web server configuration files describe configuring other supported web servers.

(dist) Avoid trouble:

A sample error message follows:


(dist) The plug-in was tested with the threaded worker multi-processing module (MPM) on all platforms except Windows. The plug-in was tested with the default threaded MPM on Windows.

(dist) The plug-in works with the Apache 2 prefork MPM but works best with the worker MPM. The plug-in maintains connection pools to backend WebSphere Application Servers and uses in-memory caching. These plug-in functions perform most efficiently when Apache 2.0 is configured to use a single child process with the ThreadsPerChild value equal to the MaxClients value. The plug-in can be used with the prefork MPM or the worker MPM configured with multiple child processes, but at reduced efficiency.

Compatibility Statement The plug-in works with versions of the Apache HTTP Server that claim full binary compatibility with Apache 2.0.47 and later, which are built with compilers and compiler options that are compatible with those used to build the plug-in.

Perform the step that configures Apache 2.0 for the operating system.

Examples and messages are shown on more than one line for clarity. Place each directive in a web server configuration file on one line.

Local file path means a file path to the plugin-cfg.xml file on an application server that is on the same machine as the web server. Remote file path means the file path to the plugin-cfg.xml file when the application server is on a remote machine.

(dist) The Web Server Plug-ins Configuration Tool installs a dummy plugin-cfg.xml file during installation, but this file requires periodic propagation from the real file on the application server machine.

(dist) The node in the following application server local file paths is web_server_name_node for a standalone application server or managed_node for a managed node.

The name of the web server definition in the following steps is webserver1.


This procedure results in re-configuring the Apache 2.0 Web Server.

What to do next

(dist) The mod_was_ap20_http plug-in module requires the GSKIT SSL encryption library if the plug-in is configured to support encrypted connections to back-end WebSphere Application Servers.

(dist) Install the web server plug-ins installs the GSKIT SSL encryption library at the required level if it is not installed. If we manually copy the plug-in to a new machine, you might not have the required GSKIT libraries for encrypting backend connections.

After configuring a web server, we can install applications on it. See the Applications section of the information center for more information.

To unconfigure a web server, reverse the manual steps and remove what was manually added in this procedure.

Related tasks

  • Configure Apache HTTP Server V2.2
  • Configure IBM HTTP Server v8.5
  • Configure IBM HTTP Server powered by Apache 2.x