If you use Process Portal in a three cluster
topology with Process Server and Process Portal on different clusters,
they must both be accessible using the same domain and port number.
The configureProxyServer script provides a simple
way to create the routing server functionality that is mandatory for IBM® BPM Process
Portal configuration.
If you prefer, you can use any
other proxy server or HTTP server. This information describes how
to configure the WebSphere proxy server by using the administrative
console. For information about configuring a different proxy server
or an HTTP server, see the documentation for the product that you
use.
Before you begin
If you have an existing server that can be used to route requests,
decide whether you want to use that server. If you will use the WebSphere
proxy server, decide whether you want to configure it manually or
by running a script.
Tip: The script uses defaults that
are suitable for creating a proxy server in a simple environment.
The script is not suitable for more complex environments, for example
if the proxy must run in a DMZ without normal access to the rest of
the cell, or if you do not want to use the default values that are
used by the script.
About this task
The reason why you need a routing server for three 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 web browser's
same origin policy will prevent 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.
Procedure
- If you want to configure a WebSphere proxy server by running
a script, perform the following actions.
- Change to the directory were the proxy scripts are located.
- cd install_root/BPM/Lombardi/tools/proxy
- cd install_root\BPM\Lombardi\tools\proxy
This directory contains the following scripts.- configureProxyServer.py
- configureProxyServer.sh
- configureProxyServer.bat
The .sh and .bat files
provide a convenient way to run the .py script.
- Create and configure the WebSphere proxy server by running
one of the following commands.
- wsadmin -f configureProxyServer.py options
- configureProxyServer.sh options
- configureProxyServer.bat options
Where options can include any of the following
parameters:- -d, --deployment-environment environment_name
- Optionally specifies the name of the deployment environment to
configure a proxy server for. If you do not specify a deployment environment,
a proxy server will be created for each deployment environment.
- -n, --node node_name
- Optionally specifies the name of the node to deploy the proxy
servers to. If you do not specify a node, one will be selected for
you.
- --no-save
- Optionally specifies not to save changes to the configuration.
- --no-sync
- Optionally specifies not to synchronize changes across all nodes.
- You must restart all clusters in the deployment environment
after running the configureProxyServer script.
- If you want to configure a WebSphere proxy server manually,
perform the following actions.
- Decide which node will host the proxy server. If
necessary, create and federate a new managed node. Make a note of
the node's host name as proxy_host_name.
- Create the proxy server using the administrative
console by clicking .
- Identify the proxy server's port numbers. Click and note the port values 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 80 and 443,
skip to step 2.h.
- 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 cluster in your deployment environment, note the port value
of the end point named WC_defaulthost_secure as cluster_member_https_port.
- Add rewrite rules. Click , then for each value of cluster_member_https_port that
you noted in step 2.f,
add the following re-writing rule to the proxy server that you created
in step 2.b:
- From URL Pattern: https://proxy_host_name:cluster_member_https_port/*
- To URL Pattern: https://proxy_host_name:proxy_https_port/*
- Set the cache.query.string custom
property. Click , 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.
- If you will configure a different type of routing server
or an existing routing server, such as a web server, proxy server,
or reverse proxy server, use the following resources to plan the routing
changes necessary for Process Portal.
- The documentation for the product that you are using for routing
requests.
- Verifying Process Portal provides
a list of the applications that Process Portal depends on and the
clusters on which they normally run.
- If you are using a third-party authentication product,
make sure that it works correctly with the new proxy. For more information,
see Configuring third-party authentication products.
Results
You have a suitably configured routing server to support Process
Portal in a three cluster topology.