This topic describes how to change configuration settings
for Apache HTTP Server Version 2.2.
Before you begin
Install Apache Version 2.2 and the latest
version of the web server plug-ins.
Avoid trouble: If you are running IBM
® HTTP Server (powered by Apache) on
IBM i, you can use the
manual configuration steps outlined below. However, it is recommended
that you use the IBM Web Administration
for
IBM i GUI.
gotcha
Apache HTTP Server Version 2.2 is different
from IBM HTTP Server (powered
by Apache). Apache HTTP Server is not supported on IBM i.
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.2 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_ap22_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.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 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.2 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.
It is recommended that you use the IBM Web
Administration for IBM i GUI
to configure the httpd.conf file.
Use the following
example of the LoadModule and the WebSpherePluginConfig directives
as a model for configuring your file for IBM i:
LoadModule was_ap20_module
/QSYS.LIB/product_library.LIB/QSVTAP22.SRVPGM
where
product_library is
the name of the WebSphere Application Server product library, such
as QWAS8A or QWAS8B. See the topic
Directory conventions for
information about how to determine the product library name.
Use the following example of the LoadModule
and the WebSpherePluginConfig directives as a model for configuring
your file for IBM i Version 7.1 when group PTF SF99368 (IBM HTTP Server
for IBM i) level 16 is installed:
LoadModule was_ap20_module /QSYS.LIB/product_library.LIB/QSVTAP22LF.SRVPGM
where
product_library is
the name of the WebSphere Application Server product library, such
as QWAS8A or QWAS8B. See the topic
Directory conventions for
information about how to determine the product library name.
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 WebSphere Application Server product library, such as QWAS8A or
QWAS8B. See the topic
Directory conventions 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 /QIBM/UserData/WebSphere/AppServer/V8/
ND/profiles/profile1/config/cells/my_cell/nodes/
my_managednode/servers/webserver1/plugin-cfg.xml
Local
standalone example:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V8/
ND/profiles/profile1/config/cells/my_cell/nodes/
webserver1_node/servers/webserver1/plugin-cfg.xml
Remote
example:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V8/
ND/profiles/httpprofile1/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_ap22_module /usr/IBM/WebSphere/Plugins/bin/mod_was_ap22_http.so
Local
distributed example: WebSpherePluginConfig
profile_root/config/cells/
dmgrcell/nodes/managednode/servers/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 your file:
LoadModule
was_ap22_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap22_http.so
Local
distributed example:WebSpherePluginConfig
profile_root/config/cells/
dmgrcell/nodes/managednode/servers/webserver1/plugin-cfg.xml
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.2, 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_ap22_module /usr/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap22_http.so
- Configure entries in the httpd.conf file.
Use the following example of the LoadModule and the WebSpherePluginConfig
directives as a model for configuring your file:
LoadModule
was_ap22_module /opt/IBM/WebSphere/Plugins/bin/mod_was_ap22_http.sl
Local
distributed example:WebSpherePluginConfig
profile_root/config/cells/
dmgrcell/nodes/managednode/servers/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 your file:
LoadModule was_ap22_module
drive:\IBM\WebSphere\Plugins\bin\mod_was_ap22_http.dll
Local
distributed example:WebSpherePluginConfig
profile_root\config\cells\
dmgrcell\nodes\managednode\servers\webserver1\plugin-cfg.xml
Results
The Apache 2.2 Web Server is re-configured.
What to do next
The native GSKIT Secure Sockets Layer
(SSL) encryption library is used.
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, 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.