Configure IBM HTTP Server v7.0

Network Deployment (Distributed operating systems), v8.0 > Set up intermediary services > Implement a web server plug-in > Edit web server configuration files

Configure IBM HTTP Server v7.0

This topic describes how to change configuration settings for IBM HTTP Server.
The Web Server Plug-ins Configuration Tool configures the web server plug-in.
This topic describes how to configure IBM HTTP Server, v7.0. Other procedures in Edit web server configuration files describe configuring other supported web servers.
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.
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
(AIX) Configure entries in the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.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/HTTPServer/Plugins/bin/mod_was_ap22_//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .so
Local distributed example:
WebSpherePluginConfig
     PROFILE_ROOT/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig
     /usr/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml
(Solaris) Configure entries in the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.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/HTTPServer/Plugins/bin/mod_was_ap22_//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .so
Local distributed example:
WebSpherePluginConfig
     PROFILE_ROOT/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig
     /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml
Configure entries in the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.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/HTTPServer/Plugins/bin/mod_was_ap22_//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .sl
Local distributed example:
WebSpherePluginConfig
     PROFILE_ROOT/config/cells/
        dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Example:
WebSpherePluginConfig
     /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml
(Windows) Configure entries in the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf file.
Use the following examples of the LoadModule and the WebSpherePluginConfig directives as models for configuring your file:
LoadModule was_ap22_module
     drive:\IBM\HTTPServer\Plugins\bin\mod_was_ap22_//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .dll
Local distributed example:
WebSpherePluginConfig
     PROFILE_ROOT\config\cells\
        dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml
Example:
WebSpherePluginConfig
     C:\IBM\HTTPServer\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_//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ plug-in module requires the GSKIT SSL encryption library if the plug-in is configured to support encrypted connections to back-end WASs.
Install 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 information center for more information.
Tip: To unconfigure a web server, reverse the manual steps and remove what was manually added in this procedure.
Edit web server configuration files
Configure Apache HTTP Server V2.2
Configure IBM HTTP Server powered by Apache 2.x
Configure IBM HTTP Server v6.x
Configure IBM HTTP Server v8.0

+
Search Tips | Advanced Search