Configuring IBM HTTP Server for dashboards

If you use IBM® HTTP Server, you must complete additional mapping steps so that dashboards work in your IBM Business Monitor environment.

1. Make sure that modules are mapped to the web server. For each of the applications required by dashboards, 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. You might have some or all applications in this list, based on which products you are using with Business Space.

      • For all products, select the following applications:
        • BSpaceEAR_nodename_servername
        • BSpaceForms_nodename_servername
        • BSpaceHelp_nodename_servername
        • BusinessSpaceHelpEAR_nodename_servername
        • REST Services Gateway
        • mm.was_nodename_servername
        • PageBuilder2_nodename_servername
      • For IBM Business Monitor, select the following applications:
        • HumanTaskManagementWidgets_nodename_servername
        • WBMDashboardWeb_nodename_servername
   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 mm.was_nodename_servername application, look for the web server to be displayed in the Server column: 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.
3. When using an HTTP server front end to work with dashboards, you must set Accept content for all requests to true for the web server plug-in in the WebSphere Application Server administrative console under Web servers > webserver1 > Plug-in properties > Request and response.