Configuring IBM HTTP Server for WSRR

If you use IBM® HTTP Server, you must complete additional mapping steps for WSRR.

Before you begin

Before you configure IBM HTTP Server to work with Business Space, complete the following steps:
  1. Install IBM HTTP Server (follow the related link for guidance).
  2. Make sure that Secure Sockets Layer (SSL) is enabled for IBM HTTP Server.
  3. Make sure that the web server definition for IBM HTTP Server has been added to the application server.

    During the installation of the IBM HTTP Server plug-in, a configureWeb_server script is produced by the install process on the web server machine. The configureWeb_server script is intended to map web application modules to the web server. Therefore, run this script after the generation of the deployment environment.

  4. Configure entries in the httpd.conf file to specify plugin details. Complete the steps given in Configuring IBM HTTP Server Version 8.0 in the WebSphere Application Server Information Center.

Procedure

  1. Make sure that modules are mapped to the web server. For each of the applications required by WSRR, verify that the web server is one of the selected targets.
    1. Log in to the administrative console as an administrative user.
    2. Click Applications > Application Types > WebSphere enterprise applications.
    3. From the Enterprise Applications panel, click the name of the application. Check the following applications:
      • ServiceRegistry
      • WSRRReportViewer (for all products)
    4. For each application, on the Configuration tab, under Modules, click Manage Modules.
    5. On the Manage Modules page for your application, make sure that the web server is one of the selected targets for each of your modules. In the table, check the Server column for each module to make sure that the web server is one of the selected targets for each of your modules. For example, for the ServiceRegistry application, look for the web server to be displayed in the Server column. In the following example, the web server name is httpserver:
      WebSphere:cell=qaxs41Cell02,node=qaxs41Node03,server=httpserver 
      WebSphere:cell=qaxs41Cell02,cluster=Golden.WebApp.

      If you need to add the web server, select the check box next to the name of the module. Then, in the Clusters and servers list, use the Ctrl key to select multiple targets. For example, to have a web server serve your application, press the Ctrl key and then select the application server cluster and the web server together. Click Apply, OK and Save to save any changes.

  2. Verify that the host name alias default_host contains the correct information for every cluster member, web server, or proxy server.
    1. Log in to the administrative console as an administrative user.
    2. Click Servers > Server Types > WebSphere application servers.
    3. For every cluster member, click the name of the application server to view the port number for the WC_defaulthost port name.
      • Under Communications, expand Ports.
      • For the port name WC_defaulthost, remember its port number.
    4. From the left navigation area of the administrative console, click Environment > Virtual hosts.
    5. Click the default_host name.
    6. Under Additional Properties, click Host Aliases.
    7. If the host name and port number for the cluster members is not displayed on the list, click New to add the missing entry to the list. The wildcard character * (asterisk) is supported for the host name.
    8. If you add a new entry, click Save and Synchronize.