Configuring IBM HTTP Server for the Business Space component for Process Portal

If you use IBM® HTTP Server, you must complete additional mapping steps so that Process Portal works in your IBM Business Process Manager environment.

Before you begin

Before you configure IBM HTTP Server to work with Process Portal, complete the following steps:

Install IBM HTTP Server
Make sure that Secure Sockets Layer (SSL) is enabled for IBM HTTP Server.
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 installation 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.

Procedure

Make sure that modules are mapped to the web server. For each of the applications required by the Business Space component and Process Portal, 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 Process Manager, select the following applications:
    - BPCExplorer_nodename_servername (only for IBM BPM Advanced)
    - BPEContainer_nodename_servername (only for IBM BPM Advanced)
    - BPMAdministrationWidgets_nodename_servername (only for IBM BPM Advanced)
    - HumanTaskManagementWidgets_nodename_servername (only for IBM BPM Advanced)
    - IBM_BPM_Help_nodename_servername
    - IBM_BPM_PerformanceDW_nodename_servername
    - IBM_BPM_Portal_nodename_servername
    - IBM_BPM_ProcessAdmin_nodename_servername
    - IBM_BPM_Process_Portal_Notification_nodename_servername
    - IBM_BPM_Process_Portal_nodename_servername
    - IBM_BPM_Repository_nodename_servername (only for Process Center)
    - IBM_BPM_Teamworks_nodename_servername
    - IBM_BPM_WebAPI_nodename_servername
    - REST Services Gateway Dmgr (only for IBM BPM Advanced)
    - TaskContainer_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.
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.
When using an HTTP server front end to work with the Business Space component for Process Portal, 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.