This topic describes how to change configuration settings
for Apache HTTP Server Version 2.0.
Before you begin
After you install the web server plug-ins,
you can use the Web Server Plug-ins Configuration Tool to configure
a web server plug-in.
This topic describes how to configure
the Apache HTTP Server Version 2.0 Web Server. Other procedures in Editing web server configuration files describe configuring
other supported web servers.
Avoid trouble: - If you are using an Apache HTTP Server that supports 64-bit addressing,
you must use the 64-bit CD provided with the WebSphere® Application Server product to
install the Apache Web Server plug-in binaries. If you use the 32-bit
CD, you will receive an error message indicating that the plug-in
binaries did not load.
- If you are using an Apache HTTP Server that supports 32-bit addressing,
you must use the 32-bit CD provided with the WebSphere Application Server product to
install the Apache Web Server plug-in binaries. If you use the 64-bit
CD, you will receive an error message indicating that the plug-in
binaries did not load.
A sample error message follows:
httpd: Syntax error on line XXX of /home/apache/conf/httpd.conf: Cannot
load /home/apache/Plugins/mod_was_ap20_http.sl into server: Invalid argument
gotcha
The plug-in was tested with the threaded worker multi-processing
module (MPM) on all platforms except Windows.
The plug-in was tested with the default threaded MPM on Windows.
The plug-in
works with the Apache 2 prefork MPM but works best with the worker
MPM. The plug-in maintains connection pools to backend WebSphere Application Servers and uses
in-memory caching. These plug-in functions perform most efficiently
when Apache 2.0 is configured to use a single child process with the
ThreadsPerChild value equal to the MaxClients value. The plug-in can
be used with the prefork MPM or the worker MPM that is configured
with multiple child processes, but at reduced efficiency.
Compatibility Statement The plug-in works with
versions of the Apache HTTP Server that claim full binary compatibility
with Apache 2.0.47 and later, which are built with compilers and compiler
options that are compatible with those used to build the plug-in.
About this task
Perform the step that configures Apache 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 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.
The name of the web server definition
in the following steps is webserver1.
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
Example:WebSpherePluginConfig
/usr/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
![[Linux]](../images/linux.gif)
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
Example:WebSpherePluginConfig
/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
![[Solaris]](../images/solaris.gif)
On the Solaris SPARC 64-bit platform, the Web Server
Plug-ins Configuration Tool installs both 32-bit and 64-bit versions
of the plug-in for Apache 2.0; however, it configures the web server
to use the 32-bit plug-in only. If the web server is 64-bit, you
need to configure the LoadModule directive in the
httpd.conf file
to use the 64-bit plug-in as follows:
LoadModule
was_ap20_module /usr/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap20_http.so
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
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
Example:WebSpherePluginConfig
C:\IBM\WebSphere\Plugins\config\webserver1\plugin-cfg.xml
Results
This procedure results in re-configuring the Apache 2.0
Web Server.
What to do next
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.
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 information center for more information.
Tip: To unconfigure a web server, reverse the manual steps and
remove what was manually added in this procedure.