Configure Apache HTTP Server V2.0

This topic describes how to change configuration settings for Apache HTTP Server V2.0.

 

Before you begin

When you install the WAS Web server plug-ins , as described in Installing Web server plug-ins, the Plug-ins installation wizard configures the Web server. This topic describes how to configure the Apache HTTP Server V2.0 Web server. Other procedures in Editing Web server configuration files describe configuring other supported Web servers.

Important:

  • If you are using an Apache HTTP Server that supports 64-bit addressing, use the 64-bit CD provided with the WebSphere Application Server 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 WebSphere Application Server 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.

Testing verified that the WAS plug-in for Apache HTTP Server, V2.0 works with Apache HTTP Server Version 2.0.48, the latest version of Apache 2.0. 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.42 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 in the following Application Server local file paths is Web_servername_node for a stand-alone Application Server or managed_node for a managed node. In each case, the remote file path is also shown.

The name of the Web server definition is webserver1.

 

Steps for this task (dependent on configuration)

  • 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/WebSphere/Plugins/bin/mod_was_ap20_http.so

    Local distributed example:

    WebSpherePluginConfig 
     /usr/IBM/WebSphere/AppServer/profiles/custom01/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml

    Local stand-alone example:

    WebSpherePluginConfig 
     /usr/IBM/WebSphere/AppServer/profiles/default/config/cells/
      sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml

    Remote example:

    WebSpherePluginConfig 
     /usr/IBM/WebSphere/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/WebSphere/Plugins/bin/mod_was_ap20_http.so

    Local distributed example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/AppServer/profiles/custom01/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml

    Local stand-alone example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/AppServer/profiles/default/config/cells/
        sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml

    Remote example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/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/WebSphere/Plugins/bin/mod_was_ap20_http.sl

    Local distributed example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/AppServer/profiles/custom01/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml

    Local stand-alone example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/AppServer/profiles/default/config/cells/
        sa_cell/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml

    Remote example:

    WebSpherePluginConfig 
     /opt/IBM/WebSphere/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 
     C:\IBM\WebSphere\AppServer\profiles\default\config\cells\
        dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml

    Local stand-alone example:

    WebSpherePluginConfig 
     C:\IBM\WebSphere\AppServer\profiles\default\config\cells\
        sa_cell\nodes\webserver1_node\servers\webserver1\plugin-cfg.xml

    Remote example:

    WebSpherePluginConfig 
     C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml

 

Result

This procedure results in reconfiguring the Apache 2.0 Web server.

 

What to do next

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