After you install and configure IBM® Business Process Manager, you
must customize your environment so that it can function properly as
a cluster with a web server.
Before you begin
Note: This page describes only the additional
IBM BPM configuration
that is required after configuring a web server in your WebSphere
Application Server cell, as described in
Implementing a web server plug-in. Also note
that some
IBM BPM applications
enforce HTTPS, and therefore also rely on a secure connection between
the web server and WebSphere Application Server. See the links under
"Related information" for more details.
Make sure that the
Process Server or Process Center has been installed and configured,
and that you have configured the deployment environment. You cannot
start the cluster until you have completed the procedures in this
topic.
About this task
If you use a web server as an entry point into your network,
you must configure virtual host information about the web server so
that IBM BPM generates
URLs that are based on the host name of the web server.
Procedure
The following procedure describes the steps to follow
for a simple configuration. For an advanced configuration, refer to
the topic "Configuring IBM BPM endpoints to match your topology."
- Stop the deployment manager.
- Start the wsadmin scripting client from the deployment
manager profile /bin directory:
wsadmin -conntype none -lang jython
- Get the deployment environment object.
Note: The
sample below assumes a deployment environment name of De1 .
This should be adapted to the deployment environment name you chose
during configuration.
dePath = '/Cell:/BPMCellConfigExtension:/BPMDeploymentEnvironment:De1/'
de = AdminConfig.getid(dePath)
print de
- Create the virtual host object for your web server:
webserver_vh = AdminConfig.create('BPMVirtualHostInfo',de, [['name','webserver_vh'],
['transportProtocol','https'],['hostname','webserver.example.com'],['port','443']], 'virtualHosts')
- Point to the newly created BPMVirtualHostInfoObject object
from either:
- Save your changes.
AdminConfig.save()
- Restart the deployment manager.