IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On Windows > Network deployment environment > Configure profiles and create an ND environment > Create an ND environment > Use the administrative console > Configure components > Configure additional components > Configure Process Portal > Configure the Business Space component for Process Portal > Configure the Business Space component for ND environments > Configure a proxy server or load-balancing server to use with the Business Space component for Process Portal
Configure a WebSphere Application Server proxy server for the Business Space component for Process Portal
If you use a WebSphere Application Server proxy server, make sure that all the modules are enabled for the proxy server so that Process Portal works in your IBM BPM environment.
Before you configure WebSphere Application Server proxy server to work with Process Portal:
- Verify that you have applied the latest version of WebSphere Application Server.
- Create a proxy server (click Servers > Server Types > WebSphere proxy servers). See
Set up the proxy server in the WebSphere Application Server information center.
- Verify that the HTTP protocol is selected.
Procedure
- Optional: Verify that modules are mapped to the WebSphere Application Server proxy server. For each of the applications that the Business Space component for Process Portal requires, verify that the modules are enabled for the proxy server.
- Log on to the administrative console as an administrative user.
- Select Applications > Application Types > WebSphere enterprise applications.
- From the Enterprise Applications panel, select 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 BPM, 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
- For each application, if you click the name of the application, then Virtual hosts, verify that it uses the value default_host.
- For each application, on the Configuration tab, under Modules, click Manage Modules, then on the Manage Modules page for the application, click each module, and select Web Module Proxy Configuration and verify that Enable Proxy is selected.
- Verify that the host name alias default_host contains the correct information for every cluster member, web server, or proxy server.
- Log on to the administrative console as an administrative user.
- Select Servers > Server Types > WebSphere application servers.
- For every cluster member, select the name of the application server to view the port number for the WC_defaulthost port name.
- Under Communications, expand Ports.
- If the port number for the WC_defaulthost port.
- From the left navigation area of the administrative console, select Environment > Virtual hosts.
- Click default_host.
- Under Additional Properties, click Host Aliases.
- If the host name and port number for the cluster members is not displayed in the list, click New to add the missing entry to the list. You can use the wildcard character * (asterisk) for the host name.
- If you add a new entry, click Save and then click Synchronize.
- To use HTTP protocol, configure the WebSphere Application Server proxy server.
- Log on to the administrative console as an administrative user.
- Select Servers > Server Types > WebSphere proxy servers, and then select the proxy server that you previously created.
- Expand HTTP Proxy Server Settings and click Proxy settings.
- Click Custom Properties and add a new property with a name of cache.query.string for a name and a value of true.
- Click Save, and then restart the proxy server.