Configuring IBM HTTP Server

This article describes how to change configuration settings for IBM HTTP Server.

Before you begin

[IBM i] IBM HTTP Server Version 8.5 is not supported on IBM® i.

[AIX Solaris HP-UX Linux Windows] The Web Server Plug-ins Configuration Tool configures the web server plug-in.

This topic describes how to configure IBM HTTP Server Version 8.5. Other procedures in Editing web server configuration files describe configuring other supported web servers.

About this task

Perform the step that configures IBM HTTP Server 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.

[AIX Solaris HP-UX Linux Windows] 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.

The node_name in the following application server local file paths is web_server_name_node for a standalone application server, or managed_node_name for a managed node.

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_ap22_module /usr/IBM/WebSphere/Plugins/bin/mod_was_ap22_http.so
```
If the web server application uses a 64-bit architecture, the plug-in library should be loaded from the plugin_root/bin/64bit directory. If the web server application uses a 32-bit architecture, the plug-in library should be loaded from the plugin_root/bin/32bits directory. If the plugin_root/bin/64bits directory does not exist, you must use the 32-bit architecture.
Local distributed example:
```
WebSpherePluginConfig
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
```
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_ap22_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap22_http.so

Local distributed example:

WebSpherePluginConfig 
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml

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

Local distributed example:

WebSpherePluginConfig 
     profile_root/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml

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_ap22_module 
     drive:\Program Files\IBM\WebSphere\Plugins\bin\mod_was_ap22_http.dll

Local distributed example:

WebSpherePluginConfig 
     profile_root\config\cells\
        dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml

Example:

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

Results

This procedure results in editing and re-configuring IBM HTTP Server.

What to do next

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

Installing the web server plug-ins 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 backend connections.

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

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