WAS v8.5 > Set up intermediary services > Implement a web server plug-in > Edit web server configuration files
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.
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.
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.
-
Configure entries in httpd.conf.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring your file:
LoadModule was_ap20_module /usr/IBM/WebSphere/Plugins/bin/mod_was_ap20_http.so
Example:WebSpherePluginConfig /usr/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml -
Configure entries in httpd.conf.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring your file:
LoadModule was_ap20_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap20_http.so
Example:WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml -
Configure entries in httpd.conf.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring your file:
LoadModule was_ap20_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap20_http.sl
Example:WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml -
Configure entries in httpd.conf.
Use the following example of the LoadModule and the WebSpherePluginConfig directives as a model for configuring your file:
LoadModule was_ap20_module drive:\IBM\WebSphere\Plugins\bin\mod_was_ap20_http.dll
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.
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. You must comment or delete the directive to start the v2.x server.
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.
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 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
Configure Apache HTTP Server V2.2
Configure IBM HTTP Server v8.5