Configure IBM HTTP Server powered by Apache 2.x

(dist)(iseries)
Configure IBM HTTP Server powered by Apache 2.x

This topic describes how to change configuration settings for IBM HTTP Server powered by Apache 2.x.

(iseries) If we are running IBM HTTP Server (powered by Apache) on IBM i, we can use the manual configuration steps outlined below with the IBM Web Administration for IBM i.
(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 IBM HTTP Server. Other procedures in Edit web server configuration files describe configuring other supported web servers.

Perform the step that configures IBM HTTP Server version 2.2 for the operating system. IBM HTTP Server powered by Apache 2.2 is supported on IBM i Versions 6.1 and 7.1.
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 spplication 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 spplication 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 spplication server machine.
The web server definition name in the following examples is webserver1.
(dist) The node name node in the following spplication server local file paths is web_server_name_node for a standalone spplication server or managed_node for a managed node.
(iseries) Configure entries in the httpd.conf file.
Use the IBM Web Administration for IBM i GUI to configure the httpd.conf file. See the topic Configuring an HTTP server instance on IBM i for a description of how to use this GUI.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the file for IBM i:
LoadModule was_ap20_module
   /QSYS.LIB/product_library.LIB/QSVTAP22.SRVPGM
where product_library is the name of the WAS product library, such as QWAS85A, and QWAS85B. See the topic Directory conventions for information about how to determine the product library name.
(WAS v8.5.0.1)
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the file for IBM i Version 7.1 when group PTF SF99368 (IBM HTTP Server for IBM i) level 16 or higher is installed:
LoadModule was_ap20_module /QSYS.LIB/product_library.LIB/QSVTAP22LF.SRVPGM
where product_library is the name of the WAS product library, such as QWAS85A, and QWAS85B. See the Directory conventions article for information about how to determine the product library name.
(v8552)
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring your file for IBM i Version 7.2:
LoadModule was_ap20_module /QSYS.LIB/product_library.LIB/QSVTAP24.SRVPGM
where product_library is the name of the WAS product library, such as QWAS85A, and QWAS85B. See the Directory conventions article for information about how to determine the product library name.

Local distributed example (Network Deployment only - the web server is configured in a managed node):
WebSpherePluginConfig
   profile_root/config/cells/my_cell/
   nodes/my_managednode/servers/webserver1/plugin-cfg.xml
Local standalone example:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V85/
   ND/profiles/profile1/config/cells/my_cell/nodes/
   webserver1_node/servers/webserver1/plugin-cfg.xml
Remote example:
WebSpherePluginConfig
   /QIBM/UserData/WebSphere/AppServer/V85/
   ND/profiles/httpprofile1/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the file:

LoadModule was_ap20_module /usr/IBM/WebSphere/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/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the file:

LoadModule was_ap20_module /opt/IBM/WebSphere/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/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the file:

LoadModule was_ap20_module /opt/IBM/WebSphere/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/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the httpd.conf file.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring the 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 editing and re-configuring IBM HTTP Server powered by Apache 2.x.

What to do next

If the IBM HTTP Server 1.3.2x directive, LoadModule ibm_app_server_http_module, is present in an IBM HTTP Server 2.x httpd.conf file, the IBM HTTP Server cannot start. We must comment or delete the directive to start the Version 2.x server.
(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 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 back-end 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