In a three- or four-cluster topology, Process Portal requires a routing server. Although you could use one of many different products, three possibilities are described in the product documentation.
The reason why you need a routing server for three and four cluster configurations is because Process Portal uses web components that are distributed across two clusters. If you do not configure a suitable server to redirect requests to the appropriate clusters, the same origin policy for the web browser prevents Process Portal from working correctly.
In a three-cluster configuration, Process Portal relies on applications on both the application deployment target cluster and the support cluster. In a four-cluster configuration, Process Portal relies on applications on both the application deployment target cluster and the web cluster.
The reason that the product documentation links to topics that describe how to configure a routing server for Business Space is because Process Portal uses the Business Space framework.
Resolving the problem
You can use any type of routing server, for example, an existing proxy server, any other web server, reverse proxy server, HTTP server, load balancer, or network layer IP sprayer.
Whichever product you decide to use, refer to the appropriate product documentation for more details about configuring it.
Refer to the Business Space topics linked to in the product documentation "Configuring Process Portal" topic for a list of Business Process Manager applications that, depending on your configuration, might need request mapping enabled.
For information about customizing the Process Server or Process Center cluster to work with a web server, see the product documentation "Customizing the PS or PC cluster for a web server" topic.
For information about using IBM HTTP Server as a routing server, see the product documentation "Load balancing and failover with IBM HTTP Server" topic.
Configuring a WebSphere proxy server using the administrative console
If you decide not to use a stand-alone product, the easiest solution is to configure the built-in WebSphere Proxy Server using the administrative console. This solution does not require you to install any other products or purchase extra licenses.
To configure a WebSphere Proxy Server for Process Portal, complete the following steps rather than the procedure that is described in the information center:
- Decide which node will host the proxy server. If necessary, create and federate a new custom node. Make a note of the host name for the node as proxy_hostname.
- Create the proxy server using the administrative console by clicking Servers > Server types > WebSphere proxy servers > New.
- Identify the port numbers for the proxy server. Click Servers > Server types > WebSphere proxy servers > your_proxy_server -> Ports and note the port values for proxy_http_port and proxy_https_port that correspond to the port values of the end points named
PROXY_HTTP_ADDRESS and PROXY_HTTPS_ADDRESS.
- If proxy_http_port and proxy_https_port are using the default values, which are 80 and 443, skip to step 9.
- Add the following host aliases to the default_host virtual host:
- Host name: * Port: proxy_http_port
- Host name: * Port: proxy_https_port
- For each cluster member in the application deployment and web deployment clusters in your deployment environment, note the port value of the end point named WC_defaulthost_secure as cluster_member_https_port.
- Click Servers > Server types > WebSphere proxy servers > your_proxy_server > HTTP Proxy Server Settings > Rewriting rules.
- For each value of cluster_member_https_port that you noted in step 6, add the following re-writing rule to the proxy server that you created in step 2:
- From URL Pattern: https://proxy_hostname:clustermember_https_port/*
- To URL Pattern: https://proxy_hostname:proxy_https_port/*
- Click Servers > Server types > WebSphere proxy servers > your_proxy_server > HTTP Proxy Server Settings > Proxy settings > Custom properties, and add the following custom property to the proxy server settings:
- Name: cache.query.string
- Value: true
- Restart all the clusters in your deployment environment.
- Start the proxy server.
- Access the Process Portal verification page at http://proxy_hostname:proxy_http_port/ProcessPortal/web_test or https://proxy_hostname:proxy_https_port/ProcessPortal/web_test
- Access Process Portal at http://proxy_hostname:proxy_http_port/portal or https://proxy_hostname:proxy_https_port/portal
IBM BPM Standard: Configure Process Portal
IBM BPM Advanced: Configure Process Portal
IBM BPM Advanced PS: Configure Process Portal
IBM BPM Advanced for z/OS PS: Configure Process Portal
Customizing the PS or PC cluster for a web server
Load balancing and failover with IBM HTTP Server
|Business Integration||IBM Business Process Manager Standard||Process Portal||AIX, Linux, Solaris, Windows||8.0.1, 8.0|