Configure Apache HTTP Server V2.0

Configure Apache HTTP Server V2.0

This topic describes how to change configuration settings for Apache HTTP Server V2.0.
Apache HTTP Server v2.0 is different from IBM HTTP Server (powered by Apache). Apache HTTP Server is not supported on i5/OS. For details on configuring IBM HTTP Server (Powered by Apache), see Configure IBM HTTP Server powered by Apache 2.0.
When you install the Web server plug-ins for WebSphere Application Server on a non-iSeries system, the Plug-ins installation wizard configures the Web server.
See Installing Web server plug-ins.
This topic describes how to configure the Apache HTTP Server V2.0 Web server. Other procedures in Edit Web server configuration files describe configuring other supported Web servers.

If you are using an Apache HTTP Server that supports 64-bit addressing, use the 64-bit CD provided with the WAS product to install the Apache Web server plug-in binaries. If you use the 32-bit CD, you will receive an error message indicating that the plug-in binaries did not load.

If you are using an Apache HTTP Server that supports 32-bit addressing, use the 32-bit CD provided with the WAS product to install the Apache Web server plug-in binaries. If you use the 64-bit CD, you will receive an error message indicating that the plug-in binaries did not load.

A sample error message follows:
httpd: Syntax error on line XXX of /home/apache/conf/httpd.conf: Cannot load /home/apache/Plugins/mod_was_ap20_http.sl into server: Invalid argument
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.
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 that is 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.

Overview

Perform the step that configures Apache 2.0 for your 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. The Plug-ins installation wizard installs a dummy plugin-cfg.xml file during installation, but this file requires periodic propagation from the real file on the Application Server machine.
The node_name in the following Application Server local file paths is web_server_name_node for a stand-alone Application Server or managed_node_name for a managed node.
The name of the Web server definition in the following steps is webserver1.

Procedure
Configure entries in the httpd.conf file. Use the following examples of the LoadModule and the WebSpherePluginConfig directives as models for configuring your file:
LoadModule 
     was_ap20_module /usr/IBM/WAS/Plugins/bin/mod_was_ap20_http.so
Local distributed example:
WebSpherePluginConfig
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig 
     /usr/IBM/WAS/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file. Use the following examples of the LoadModule and the WebSpherePluginConfig directives as models for configuring your file:
LoadModule 
     was_ap20_module /opt/IBM/WAS/Plugins/bin/mod_was_ap20_http.so
Local distributed example:
WebSpherePluginConfig 
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig 
     /opt/IBM/WAS/Plugins/config/webserver1/plugin-cfg.xml
On the Solaris SPARC 64-bit platform, the Plug-ins installation wizard installs both 32-bit and 64-bit versions of the plug-in for Apache 2.0, however it configures the Web server to use the 32-bit plug-in only. If the Web server is 64-bit, configure the LoadModule directive in the httpd.conf file to use the 64-bit plug-in as follows:
LoadModule 
     was_ap20_module /usr/IBM/WAS/Plugins/bin/64bits/mod_was_ap20_http.so
Configure entries in the httpd.conf file. Use the following examples of the LoadModule and the WebSpherePluginConfig directives as models for configuring your file:
LoadModule 
     was_ap20_module /opt/IBM/WAS/Plugins/bin/mod_was_ap20_http.sl
Local distributed example:
WebSpherePluginConfig 
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig 
     /opt/IBM/WAS/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file. Use the following examples of the LoadModule and the WebSpherePluginConfig directives as models for configuring your file:
LoadModule was_ap20_module 
     drive:\IBM\WebSphere\Plugins\bin\mod_was_ap20_http.dll
Local distributed example:
WebSpherePluginConfig 
     profile_root\config\cells\
        dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml
Example:
WebSpherePluginConfig
     C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml
Results

This procedure results in reconfiguring the Apache 2.0 Web server.

What to do next

The Plug-ins installation wizard installs the GSKIT SSL encryption library at the required level if it is not installed. If you manually copy the plug-in to a new machine, you might not have the required GSKIT libraries for encrypting back-end connections.
After configuring a Web server, you can install applications on it. See the Applications section of the information center for more information.

Related tasks

Configure IBM HTTP Server V6.x
Configure IBM HTTP Server powered by Apache 2.0
Edit Web server configuration files