This topic describes how to change configuration settings for Apache
HTTP Server Version 2.0.
Before you begin
Important: If you
are running IBM HTTP Server (powered by Apache) on i5/OS, you can use the
manual configuration steps outlined below. However, it is recommended that
you use the IBM Web Administration for i5/OS GUI. See
Creating and configuring an HTTP server instance for more information.
Apache HTTP Server Version 2.0 is different from IBM
HTTP Server (powered by Apache). Apache HTTP Server is not supported on i5/OS.
For details on configuring IBM HTTP Server (Powered by Apache), see Configuring IBM HTTP Server powered by Apache 2.0.
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.
See Installing Web server plug-ins on i5/OS.
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.
Important:
- 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
The plug-in was tested with the threaded worker multiprocessing
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 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 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.
The name of the Web server definition in the
following steps is webserver1.
Procedure
Configure entries in thehttpd.conf file.
It is recommended that you use the IBM Web Administration for i5/OS
GUI to configure 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 /QSYS.LIB/QWAS6.LIB/QSVTAP20.SRVPGM
Local
distributed example (Network Deployment only - the Web server is configured
in a managed node:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V6/
ND/profiles/profile1/config/cells/my_cell/nodes/
my_managednode/servers/webserver1/plugin-cfg.xml
Local
stand-alone example:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V6/
ND/profiles/profile1/config/cells/my_cell/nodes/
webserver1_node/servers/webserver1/plugin-cfg.xml
Remote
example:
WebSpherePluginConfig /QIBM/UserData/WebSphere/AppServer/V6/
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_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
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]](../../solaris.gif)
On the Solaris SPARC 64-bit platform,
the Plug-ins installation wizard 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 reconfiguring the Apache 2.0 Web server.
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.