| < Day Day Up > |
|
You can choose IBM HTTP Server or Apache HTTP Server provided by a Linux distribution as a Web server.
If you decide to use the Apache HTTP Server instead of the IBM HTTP Server, use the same installation procedures described in Chapter 2, but set the features shown in Figure 2-7 on page 18 as follows:
Deselect IBM HTTP Server.
Select the Apache module plug-in instead of the IBM HTTP plug-in.
After successful installation, the following lines are automatically added at the end of the configuration file (/etc/httpd/httpd.conf) to plug in the WebSphere Application Server.
LoadModule app_server_http_module /<WAS_HOME>/bin/mod_app_server_http.so WebSpherePluginConfig /<WAS_HOME>/config/cells/plugin-cfg.xml
In addition, you need to change the Apache configuration to work with Apache Server and WebSphere Application Server V5.0.2 for Linux on iSeries. This section covers how to configure your Apache Server. (For the purpose of this discussion, we used SUSE Linux.)
The steps to configure your Apache Server:
Edit the configuration file suse_addmodule.conf using the following command:
# vi/etc/httpd/suse_addmodule.conf
Remove mod_perl.c, as shown in Figure 4-12.
# # Automatically generated by SuSEconfig on Mon Oct 6 16:38:49 PDT 2003 # # PLEASE DO NOT EDIT THIS FILE! # AddModule mod_php4.c #AddModule mod_perl.c AddModule mod_python.c AddModule mod_userdir.c
Edit configuration file suse_loadmodule.conf using the following command:
# vi /etc/httpd/suse_loadmodule.conf
Remove libperl.so, as shown in Figure 4-13.
# # Automatically generated by SuSEconfig on Mon Oct 6 16:38:49 PDT 2003 # # PLEASE DO NOT EDIT THIS FILE! # LoadModule php4_module /usr/lib/apache/libphp4.so #LoadModule perl_module /usr/lib/apache/libperl.so LoadModule python_module /usr/lib/apache/mod_python.so LoadModule userdir_module /usr/lib/apache/mod_userdir.so
Edit the configuration file httpd.conf using the following command:
# vi /etc/httpd/httpd.conf
Add the following two statements at the beginning of the block shown in Figure 4-14.
# LoadModule foo_module libexec/mod_foo.so LoadModule app_server_http_module /opt/WebSphere/AppServer/bin/mod_app_server_http.so WebSpherePluginConfig /opt/WebSphere/AppServer/config/cells/plugin-cfg.xml LoadModule mmap_static_module /usr/lib/apache/mod_mmap_static.so LoadModule vhost_alias_module /usr/lib/apache/mod_vhost_alias.so
LoadModule app_server_http_module /opt/WebSphere/AppServer/bin/mod_app_server_http.so WebSpherePluginConfig /opt/WebSphere/AppServer/config/cells/plugin-cfg.xml
Add the following statement after ALL other modules are added, as shown in Figure 4-15.
# Again, the following file is generated by SuSEconfig for modules that actually # have been installed AddModule mod_app_server_http.c # # ExtendedStatus controls whether Apache will generate "full" status # information (ExtendedStatus On)or just basic information (ExtendedStatus # Off) when the "server-status" handler is called. The default is Off. #
AddModule mod_app_server_http.c
Start Apache server using the following command.
# apachectl start
| < Day Day Up > |
|