This topic describes how to change configuration settings for IBM
HTTP Server powered by Apache 2.0.
Before you begin
When you install the Web server
plug-ins for WebSphere Application Server on a non-iSeries system, the Plug-ins
installation wizard configures the Web server.
See Installing Web server plug-ins
.
This topic describes how to configure the IBM HTTP
Server, V2.x. 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 version 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 Web server definition name in the following examples
is webserver1.
The node name node_name in
the following Application Server local file paths is web_server_name_node for
a stand-alone Application Server or managed_node_name for
a managed node. In each case, the remote file
path is also shown.
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_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
Local stand-alone example:WebSpherePluginConfig
profile_root/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
profile_root/config/cells/
dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Local stand-alone example:WebSpherePluginConfig
profile_root/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
profile_root/config/cells/
dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
Local stand-alone example:WebSpherePluginConfig
profile_root/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
profile_root\config\cells\
dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml
Local stand-alone example:WebSpherePluginConfig
profile_root\config\cells\
sa_cell\nodes\webserver1_node\servers\webserver1\plugin-cfg.xml
Remote example:WebSpherePluginConfig
C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml
Results
This procedure results in editing and reconfiguring IBM HTTP Server
powered by Apache 2.0.
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.0 httpd.conf file,
the IBM HTTP Server cannot start. You must comment or delete the directive
to start the Version 2 server.
The mod_was_ap20_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.
The Plug-ins installation wizard 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,
you can install applications on it. See the Applications section of the information
center for more information.