Manually configuring Apache HTTP Server V1.3

This topic describes how to change configuration settings for Apache HTTP Server Version 1.3.

This topic is one of the optional procedures in Manually configuring supported Web servers.

Perform the step that configures the Apache HTTP Server 1.3 Web server that you intend to use, with or without support for extended API (EAPI) on a Linux, UNIX, or Windows platform.

Examples and messages are sometimes shown on more than one line for ease of presentation. Verify that each directive in a Web server configuration file is on one line.

Most Apache Web servers are not compiled with EAPI support. If you see a message similar to one of the following examples when starting the Web server with the mod_app_server_http.so plug-in module, use the EAPI version of the module.

Linux and UNIX-based platforms

[warn] Loaded DSO /opt/WebSphere/AppServer/bin/mod_app_server_http.so 
uses plain Apache 1.3 API, this module might crash under EAPI! 
(please recompile it with -D EAPI)

The installation root, /opt/WebSphere/AppServer, can vary per operating system platform. For example, the AIX installation root is /usr/WebSphere/AppServer/ for Version 5.

Windows platforms

[warn] Loaded DSO C:\WebSphere\AppServer\bin\mod_app_server_http.dll 
uses plain Apache 1.3 API, this module might crash under EAPI! 
(please recompile it with -D EAPI)

Ignore the preceding message on SuSE Linux Enterprise Server 8.0. You must configure the Apache 1.3 httpd.conf file to run on SLES 8.0 as described in the first step.

1. (Optional)   Configure the entries in the httpd.conf file of Apache HTTP Server 1.3 without EAPI support to run on a SuSE Linux Enterprise Server 8.0 platform.

   Use the Apache 1.3 Web server that ships with SuSE Linux Enterprise Server (SLES) 8.0 if you comment the PHP directives in the httpd.conf file. Also, update the version of Apache 1.3 that ships with SLES 8 and comment the PHP directives to use the binary plug-in module that supports EAPI.

2. (Optional)   Configure the entries in the httpd.conf file of Apache HTTP Server 1.3 without EAPI support on other Linux platforms or on a UNIX-based platform.

   Use the following examples of the LoadModule and WebSpherePluginConfig directives as models for configuring your file

   LoadModule app_server_http_module/opt/WebSphere/AppServer/bin/mod_app_server_http.so
   WebSpherePluginConfig /opt/WebSphere/AppServer/config/cells/plugin-cfg.xml"
   
   

3. (Optional)   Configure the entries in the httpd.conf file of Apache HTTP Server 1.3 without EAPI support on a Windows platform.

   Use the following examples of the LoadModule and WebSpherePluginConfig directives as models for configuring your file

   LoadModule ibm_app_server_http_module 
        drive:\WebSphere\AppServer\bin\mod_app_server_http.dll
   WebSpherePluginConfig 
        drive:\WebSphere\AppServer\config\cells\plugin-cfg.xml
   
   

4. (Optional)   Configure the entries in the httpd.conf file of Apache HTTP Server 1.3 with EAPI support on a Linux or UNIX-based platform.

   Use the following examples of the LoadModule and WebSpherePluginConfig directives as models for configuring your file

   LoadModule app_server_http_module/opt/WebSphere/AppServer/bin/mod_app_server_http_eapi.so
   WebSpherePluginConfig /opt/WebSphere/AppServer/config/cells/plugin-cfg.xml"
   
   

5. (Optional)   Set the LD_LIBRARY_PATH variable.On some installations of Apache on a Linux machine, it is necessary to manually set the LD_LIBRARY_PATH variable to /usr/lib before starting Apache with a plug-in configured for SSL. For example, in the korn shell, issue the following command before invoking the command to start Apache

   'export $LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH' 
   

6. (Optional)   Configure the entries in the httpd.conf file of Apache HTTP Server 1.3 with EAPI support on a Windows platform.

   Use the following examples of the LoadModule and WebSpherePluginConfig directives as models for configuring your file

   LoadModule ibm_app_server_http_module 
        drive:\WebSphere\AppServer\bin\mod_app_server_http_eapi.dll
   WebSpherePluginConfig 
        drive:\WebSphere\AppServer\config\cells\plugin-cfg.xml
   
   

You can configure the Apache 1.3.x Web server to work with WebSphere Application Server, V5.

To continue preparing your e-business network, return to Manually configuring supported Web servers.

 

See Also

Manually configuring Apache HTTP Server V2.0
Manually configuring Lotus Domino V5
Manually configuring Lotus Domino Version 6
Manually configuring IBM HTTP Server powered by Apache 1.3
Manually configuring IBM HTTP Server powered by Apache 2.0
Manually configuring Microsoft Internet Information Services (IIS)
Manually configuring Sun ONE Web server

 

---