Configuring IBM HTTP Server

You can manually configure IBM HTTP Server.

Before you begin

[IBM i] IBM HTTP Server Version 9.0 is not supported on IBM® i.

[AIX Solaris HP-UX Linux Windows] The plug-in Configuration Tool (PCT) is the primary way to configure the IBM HTTP Server to load the WebSphere Application Server web server plug-in.

The Plug-in Configuration Tool (PCT) automatically configures the IBM HTTP Server. The following steps are the manual instructions for configuring the IBM HTTP Server. Other procedures in Editing web server configuration files describe configuring other supported web servers.

About this task

Examples and messages are shown on more than one line for clarity. Place each directive in a web server configuration file on one line.

Product installation paths are examples only.

[AIX Solaris HP-UX Linux Windows] The web server Plug-in Configuration Tool (PCT) installs a dummy plugin-cfg.xml file during installation, but this file requires periodic propagation from the real file on the application server.

Procedure

Determine the correct web server plug-in module to load, typically 32-bit on Windows, and 64-bit elsewhere, by determining the architecture of the web server.
```
/opt/IBM/HTTPServer/bin/versionInfo.sh | grep Architecture
```
```
c:\IBM\HTTPServer\bin\versionInfo.bat | findstr Architecture
```

Load the web server plug-in by appending the following line to the httpd.conf file, taking note of the architecture specified in the path.

LoadModule 
     was_ap24_module /opt/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.so

LoadModule 
     was_ap22_module /opt/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.sl

LoadModule was_ap24_module
     c:/IBM/WebSphere/Plugins/bin/<arch>/mod_was_ap24_http.dll

In these examples, <arch> is 32bits or 64bits depending on the web server architecture.

Create the required directories and copy temporary configuration files.


      mkdir -p  /opt/IBM/WebSphere/Plugins/{logs,config}/webserver1          
      cp /opt/IBM/WebSphere/Plugins/etc/plugin-key* /opt/IBM/WebSphere/Plugins/config/webserver1/          
      cp /opt/IBM/WebSphere/Plugins/config/templates/plugin-cfg.xml /opt/IBM/WebSphere/Plugins/config/webserver1/


      mkdir c:\IBM\WebSphere\Plugins\logs\webserver1          
      mkdir c:\IBM\WebSphere\Plugins\config\webserver1          
      copy c:\IBM\WebSphere\Plugins\etc\plugin-key* c:\IBM\WebSphere\Plugins\config\webserver1\          
      copy c:\IBM\WebSphere\Plugins\config\templates\plugin-cfg.xml c:\IBM\WebSphere\Plugins\config\webserver1\

Register the web server with the application server.

For the plugin-cfg.xml configuration file to be useful, it must be generated by the application server environment to reflect configured servers and deployed applications. A definition can be created in the Administration Console on a Deployment Manager or stand-alone Application Server. See Web server definition.

When registered, the Administration Console can generate and propagate a plugin-cfg.xml file to the web server, replacing the initial plugin-cfg.xml file.

For web servers that are used with Liberty see, Configuring a web server plug-in for Liberty
Append a second directive to the httpd.conf file to identify the path to the plugin-cfg.xml file.
- Remote web servers, not co-located with any WebSphere management process, or web servers used with WebSphere Liberty:
```
WebSpherePluginConfig /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
```
- Web server registered with a stand-alone traditional application server:
```
WebSpherePluginConfig profile_root/standalone/config/cells/standalone/nodes/standalone/servers/webserver1/plugin-cfg.xml
```
- Web server registered with a co-located Deployment Manager:
```
WebSpherePluginConfig profile_root/config/cells/<var>dmgrcell</var>/nodes/managednode/servers/webserver1/plugin-cfg.xml
```

Results

This procedure results in editing and reconfiguring the IBM HTTP Server.

What to do next

The mod_was_ap24_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 workstation, you might not have the required GSKIT libraries for encrypting backend connections.

When a web server has been configured, you can install applications on it. See the Applications section of the knowledge center for more information.

Tip: To unconfigure a web server, reverse the manual steps and remove what was manually added in this procedure.