Expanding the IBM Business Process Manager V8.

5
topology by using multiple deployment environments
Yu Xiao Li (yuxiaoli@cn.ibm.com )
Advisory Software Engineer
IBM

30 June 2014

As your business requirement grows, you may want to expand the topology of IBM Business
Process Manager to run different processes independently. This article introduces how to
expand the IBM BPM V8.5 topology using multiple deployment environments.

Introduction
After you install and configure the runtime environment on IBM Business Process Manager
(BPM) and your business requirements continue to grow and change, you may want to run more
processes and isolate those processes. You can expand the environment by configuring multiple
deployment environments (DE) in this case. Each deployment environment can run different
processes and work independently.

Try the Workflow service

Create long-running, stateful workflows that orchestrate tasks and services with synchronous
or asynchronous event-driven interactions with the Workflow service from Bluemix. Try it for
free!

This article introduces how to expand IBM BPM V8.5 topology by using multiple deployment
environments, including topology planning, configuration methods according to your requirements,
configuration and post verification steps, and troubleshooting tips. You can use this article to plan
your multiple deployment environments and configure them for your environment.
This article is intended for IBM BPM users and administrators who have growing business
requirements, need to run more processes independently in their IBM BPM environment, and need
to isolate different IBM BPM deployment environments in the same cell.

Reasons to expand your topology

As your business requirement grows and changes, you may want to run more different business
processes on IBM BPM, and you may have more security requirements to isolate those
applications. You may have more performance requirements that need more servers, clusters, and
even deployment environments. In this case, you may need to expand your IBM BPM topology to
satisfy such requirements.
Copyright IBM Corporation 2014
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Trademarks
Page 1 of 22

developerWorks

ibm.com/developerWorks/

Different ways to expand your topology

There are several ways to expand your IBM BPM topology, such as adding cluster members, cells,
and deployment environments.

Adding cluster members

Adding cluster members is the easiest way to expand the IBM BPM topology. You can proceed
to the Admin console and select Servers > Deployment Environments > Your DE name >
Additional Properties > Deployment Topology (see Figure 1). In this page, you can add more
nodes and more cluster members to the existing DE.

Figure 1. Adding cluster members

Adding cluster members may not be suitable for all situations. For example, you may want to
isolate different applications. If you deploy different applications to the same DE, it may introduce
dependencies between those applications, such as maintenance schedules and application
availability. Also, you may already have many applications running on the existing DE. Adding
more applications to the same DE may result in too many modules, or heavily using your database
tables.

Adding cells
To expand your topology, you can also create a new cell, and then create a new DE in this new
cell. This method is the most flexible, and it can isolate applications in different DEs. However,
it requires more administration work. You will need to use different admin consoles to manage
different cells and DEs.

Adding deployment environments

If adding cluster members and adding cells cannot satisfy your requirement, you can choose
the third option: adding the deployment environment in the same cell. You can run different
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 2 of 22

ibm.com/developerWorks/

developerWorks

applications on different DEs independently, and you can manage them in the same admin
console.
However, in an IBM BPM network deployment environment, you can configure a routing server,
such as an IBM HTTP (IHS) Server, a WebSphere Application Server proxy server, or others, as
a proxy server for workload balancing and failover purposes. Instead of incoming HTTP requests
going directly to an application server, they go to the proxy server, which then distributes the
requests across multiple application servers that perform the work.
After configure IHS, you can use the IHS host name or IP to access all IBM BPM web-based tools,
such as Portal, Process Admin, BPC Explorer, Process Center, Business Space, and so on. But
for example, if you use the URL of http://IHSHostName/bpc to access the BPC Explorer, you
cannot distinguish the BPC Explorer of the two DEs. The URL is the same for the BPC Explorer of
the two DEs, as they are using the same IHS and in the same cell.
Therefore, you have to do some configurations to distinguish between the two DEs. There are two
ways to do it: by virtual host or by context root.

Distinguish different deployment environments by virtual host

By using a virtual host, you will not access web-based tools by the IHS host name. You will
use virtual host instead. You will configure a different virtual host for different DEs, then you
can distinguish the two DEs by different virtual hosts. For example, you will use "Golden1" and
"Golden2" as the virtual host for the two DEs. Then you will access the BPC Explorer of DE1 using
http://Golden1/bpc, and BPC Explorer of DE2 using http://Golden2/bpc. In this article, we will
introduce how to configure a double DE environment by a virtual host.

Distinguish different deployment environments by context root

By using a context root, you will change the context root of web based tools. For example, you can
add a prefix for the BPC Explorer of DE1, such as "de1". Then, you will access the BPC Explorer
of DE1 using http://IHSHostName/de1/bpc. Similarly, you can configure the BPC Explorer of DE2
as http://IHSHostName/de2/bpc. Then, you can distinguish the BPC Explorer from different DEs.
In IBM BPM V8.5, only BPC explorers support customized context root. Other tools such as
Portal and Business Space do not support it. You cannot configure context root prefixes for them.
Therefore, you cannot distinguish those tools of different DE using the context root. Because of it,
we will not introduce this method in this article.

Planning considerations for multiple deployment environments

Before configure multiple DEs, you need to plan your environment and topology. For example,
which nodes to use for each DE, how many clusters and servers can each DE use, which
applications can run on each DE, and which databases to use for each DE.

Considerations and assumptions before using multiple DEs

When planning for multiple DE environments, you need to consider some aspects and limitations
of multiple DEs:
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 3 of 22

developerWorks

ibm.com/developerWorks/

You cannot install the same SCA applications to both DEs because both DEs are in the same
cell, and there is only one admin console to manage them.
Only Process Server supports multiple DEs. Process Center does not support multiple DEs.
Each DE must have their own application cluster, and if you select to use a three cluster
topology, each DE must have their corresponding messaging and support clusters.
Each DE must use different databases. For example, if you are using DB2, you can use the
same DB2 instance. However, you need to use different databases for different DEs.
If there is an issue with one application in the cell, it is not possible to apply an interim fix only
to the affected application. Interim fixes affect all servers and clusters in the cell.

Multiple DE configurations
In this section, we will introduce how to configure double DEs using IBM BPM Advanced Edition.
We will use the IHS as proxy server and configure different virtual hosts for each DE.

Environment topology
In our sample environment, there will be double IBM BPM Advanced PS DEs. Both of them will
use the same IHS. The topology diagram is shown in Figure 2.

Figure 2. Topology diagram

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 4 of 22

ibm.com/developerWorks/

developerWorks

Create double DEs with the DE wizard

First of all, you need to install IBM BPM Advanced Edition V8.5 and create the Deployment
Manager and custom profiles according to your requirement. Then, you need to use the DE wizard
to create two DEs (see Figure 3). The DE wizard can only create one DE each time. You need to
run the DE wizard twice, and specify different DE names. On the configure database page, make
sure you are using different databases and schemas for each deployment environment. Detailed
steps in the DE wizard are not covered in this article.

Figure 3. Configure the database page in the DE wizard

Configure the IHS certificate

When configuring IHS, you need to configure the SSL as it is required by IBM BPM by default.
If you want to use the same IHS for double DEs and create the arm file, besides the host name,
you also need to add the virtual host of the double DEs in the DNS name field. In our example,
we will use "Golden1" as the virtual host of DE1, and "Golden2" as the virtual host of DE2. Add
Golden1,Golden2 in the DNS field as shown in Figure 4. The detailed IHS configuration steps are
not covered in this article.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 5 of 22

developerWorks

ibm.com/developerWorks/

Figure 4. IHS certificate configuration

Plan and update virtual host

As described before, we will use different virtual hosts for different deployment environments. In
the admin console, select Environment > Virtual hosts to define the virtual host and host alias. In
our example, we will use the virtual host shown in Table 1.

Table 1. Virtual host definitions

Virtual host

Host alias

Used by

Golden1

Golden1

DE1

proxy_host

Golden2

DE2

admin_host

Dmgr

default_host

Applications that are deployed on both DEs

Golden1 virtual host

You need to create a new virtual host, Golden1, for DE1. In the admin console, Environment >
Virtual hosts, create a virtual host and some host aliases, as shown in Figure 5.
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 6 of 22

ibm.com/developerWorks/

developerWorks

Figure 5. Golden1 virtual host

Proxy_host virtual host

You will use proxy_host as the DE2 virtual host as shown in Figure 6.

Figure 6. Proxy_host virtual host

Admin_host virtual host

Admin_host is used by some applications deployed on Deployment Manager, such as the REST
Services Gateway Dmgr application. Update admin_host as shown in Figure 7.

Figure 7. Admin_host virtual host

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 7 of 22

developerWorks

ibm.com/developerWorks/

Default_host virtual host

You will use default_host for some applications deployed on both DE1 and DE2, such as the
RemoteAL61 application. In default_host, add the host alias of IP and ports of the application
servers. Update default_host as shown in Figure 8.

Figure 8. Default_host virtual host

Update virtual host for applications deployed on different DEs

After defining the virtual host, update all applications to use the corresponding virtual host
according to which DE they are deployed on.

Update virtual host for DE1 applications

To set all applications deployed on DE1 to use Golden1 as a virtual host, start dmgr, and run the
"updateVirtualHost" command:
dmgr_profile\bin\updateVirtualHost.bat -d first_deployment_environment -v virtual_host_name

In our example, run the following command:

C:\BPM\AppServer\profiles\Dmgr01\bin>updateVirtualHost.bat -d DE1 -v Golden1

After running the commands, all applications deployed on DE1 will use the virtual host of
"Golden1" as shown in Figure 9.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 8 of 22

ibm.com/developerWorks/

developerWorks

Figure 9. Virtual host of DE1 applications

Update applications deployed on DE2

To set all applications deployed on DE2 to use proxy_host as virtual host, you need start dmgr, and
run the 'updateVirtualHost" command:
dmgr_profile\bin\updateVirtualHost.bat -d second_deployment_environment -v virtual_host_name

In our example, run the following command:

C:\BPM\AppServer\profiles\Dmgr01\bin>updateVirtualHost.bat -d DE2 -v proxy_host

After running the commands, all applications deployed on DE2 will use the virtual host of
"proxy_host", similar to Figure 9.

Update applications deployed on both DEs

For the RemoteAL61 application, because it is deployed on both DEs, you will map it to use
default_host. In the admin console, select Applications > Application Types > WebSphere
enterprise applications > RemoteAL61 > Web Module Properties > Virtual hosts and update
the virtual host to default_host.

Update the rest service gateway applications and rest service providers
Be default, the REST Services Gateway application is deployed on both DEs and it is impossible
to distinguish it for the different DEs. Deploy another REST Services Gateway application with a
different name, and map a different REST Services Gateway application to each DE. Also, you
need to update the other service providers.

Update the rest service gateway application for DE1

For DE1, you will use the existing rest service gateway application. First, update it to use the
virtual host of Golden1, which we used for the DE1 applications. In the admin console, select
Applications > Application Types > WebSphere Enterprise Applications > REST Services
Gateway > Virtual hosts and update the virtual host as shown in Figure 10.
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 9 of 22

developerWorks

ibm.com/developerWorks/

Figure 10. Virtual host of DE1 rest service gateway application

Second, map the application to the DE1 application cluster and web server. In the admin console,
select Applications > Application Types > WebSphere Enterprise Applications > REST
Services Gateway > Manage Modules and update the information as shown in Figure 11.

Figure 11. Map modules of DE1 rest service gateway application

Third, change the context root to "restPS1". The rest service gateway applications of the different
DEs must use different context roots; otherwise, some applications that use the rest APIs cannot
distinguish the two applications. In the admin console, select Applications > Application Types
> WebSphere Enterprise Applications > REST Services Gateway > Context Root for Web
Modules and update the information as shown in Figure 12.

Figure 12. Context root of the DE1 rest service gateway application

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 10 of 22

ibm.com/developerWorks/

developerWorks

To update the context root from default rest to "restPS1", besides updating in the admin console
as shown in Figure 12, you also need to run the following UpdateRESTServiceProvider wsadmin
command. Enter your user credentials when prompted.
wsadmin.bat -lang jython
wsadmin>AdminTask.updateRESTServiceProvider(['-clusterName', 'DE1.AppCluster', '-appName',
'REST Services Gateway', '-webModuleName', 'rest.gateway.war', '-contextRoot', '/restPS1'])
wsadmin>AdminConfig.save()

Deploy and update the rest service gateway application for DE2
To distinguish the rest service gateway applications of the different DEs, you must manually deploy
another rest service gateway application to DE2 and update the configurations:
1. First, deploy the rest service gateway application manually to DE2. The REST Services
Gateway application is found in the WebSphere Application Server installation as root/
installableApps/RESTServiceGateway.ear. Deploy it from the admin console by selecting
Applications > Application Types > WebSphere Enterprise Applications > Install. When
you deploy it (see Figure 13), you need to identify a different application name, such as
"REST Services Gateway PS2", to distinguish it from the existing REST Services Gateway
application of DE1.

Figure 13. Deploy the DE2 rest service gateway application

2. Second, when you deploy the application, map the application to DE2 and web server as
shown in Figure 14.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 11 of 22

developerWorks

ibm.com/developerWorks/

Figure 14. Map modules of the DE2 rest service gateway application

3. Third, update it to use the virtual host of "proxy_host", which you used for the DE2
applications. Similar to DE1, update the virtual host as shown in Figure 15.

Figure 15. Virtual host of DE2 rest service gateway application

4. Fourth, change the context root to "restPS2". Similar to what you did for DE1, update the
information as shown in Figure 16.

Figure 16. Context root of DE2 rest service gateway application

5. To update the context root from default rest to "restPS2", besides updating in
the admin console as shown in Figure 16, you also need to run the following

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 12 of 22

ibm.com/developerWorks/

developerWorks

UpdateRESTServiceProvider wsadmin command. Enter your user credentials when

prompted.
wsadmin.bat -lang jython
wsadmin>AdminTask.updateRESTServiceProvider(['-clusterName', ' DE2.SingleCluster', '-appName',
'REST Services Gateway', '-webModuleName', 'rest.gateway.war', '-contextRoot', '/restPS2'])
wsadmin>AdminConfig.save()

Update the rest service providers

In the admin console, select Services > REST services > REST service providers and update
all the rest service providers, except REST Services Gateway Dmgr as it is deployed on dmgr.
Update the host name or virtual host in a load-balanced environment to "Golden1" for all the DE1
rest service providers. Update it to "Golden2" for all the DE2 rest service providers. Update all the
ports to "443", as all the transactions will go through IHS and SSL. Table 2 shows the result after
updating the rest service providers.

Table 2. Rest service providers

Provider Application
REST Services Gateway

Scope

Host name or virtual host in

a load-balanced environment

Port

Cluster=DE2.SingleCluster

Golden2

443

IBM_BPM_Teamworks_DE2.SingleCluster
Cluster=DE2.SingleCluster

Golden2

443

BPEContainer_DE2.SingleCluster

Cluster=DE2.SingleCluster

Golden2

443

TaskContainer_DE2.SingleCluster

Cluster=DE2.SingleCluster

Golden2

443

REST Services Gateway Dmgr

Node=WINNo need to update

E6GDL89KDJDCellManager01,Server=dmgr

No need to update

REST Services Gateway

Cluster=DE1.AppCluster

Golden1

443

IBM_BPM_Teamworks_DE1.AppCluster
Cluster=DE1.AppCluster

Golden1

443

BPEContainer_DE1.AppCluster

Cluster=DE1.AppCluster

Golden1

443

TaskContainer_DE1.AppCluster

Cluster=DE1.AppCluster

Golden1

443

An example of updating rest service provider is shown in Figure 17.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 13 of 22

developerWorks

ibm.com/developerWorks/

Figure 17. Update the rest service providers

Update the Business Process Choreographer

In a double DE environment, you also need some updates for the Business Process
Choreographer and Human Task Manager.

Update the BPEContainer and TaskContainer context roots

After you create two DEs using the DE wizard, each DE will have their own BPEContainer and
TaskContainer applications, but the context roots are the same. You need to update the context
root, make sure each DE has a different context root. In our example, you only need to update the
context root for DE2.
In the admin console, select Applications > Application types > WebSphere enterprise
applications > BPEContainer_DE2.SingleCluster > Context Root for Web Modules, update
the context root, and add "PS2" as shown in Figure 18.

Figure 18. Update the DE2 BPEContainer context root

Similarly, update the context root for the DE2 TaskContainer application as shown in Figure 19.
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 14 of 22

ibm.com/developerWorks/

developerWorks

Figure 19. Update the DE2 TaskContainer context root

Update the REST service provider for Business Process Choreographer

Similar for the REST service gateway application, after changing the context root in admin
console, you also need run the following UpdateRESTServiceProvider wsadmin command. Enter
your user credentials when prompted.
wsadmin -lang jython
wsadmin>AdminTask.updateRESTServiceProvider(['-clusterName', 'DE2.SingleCluster', '-appName',
'BPEContainer_DE2.SingleCluster', '-webModuleName','bfmrestapi.war', '-contextRoot',
'/rest/bpm/bfmPS2/'])
wsadmin>AdminTask.updateRESTServiceProvider(['-clusterName', 'DE2.SingleCluster', '-appName',
'TaskContainer_DE2.SingleCluster', '-webModuleName','taskrestapi.war', '-contextRoot',
'/rest/bpm/htmPS2/'])
wsadmin>AdminConfig.save()

Update the REST API URLs

The BPC REST APIs are not part of the REST Services Gateway and the BPC Explorer does not
use the REST endpoints in config-rest.xml. You need to change the REST URLs that the BPC
Explorer is using in the admin console, both for DE1 and DE2.
For DE1, update the REST URLs to use the virtual host of Golden1. In the admin console, select
Servers > Clusters > WebSphere application server clusters > DE1.SupCluster > Business
Process Choreographer Explorer > BPCExplorer_DE1.SupCluster and update the information
as shown in Figure 20.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 15 of 22

developerWorks

ibm.com/developerWorks/

Figure 20. Update the DE1 BPC Explorer REST API URLs

For DE2, update the REST URLs to use the virtual host of Golden2, and add the context
root of PS2. In the admin console, select Servers > Clusters > WebSphere application
server clusters > DE2.SingleCluster > Business Process Choreographer Explorer >
BPCExplorer_DE2.SingleCluster and update the information as shown in Figure 21.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 16 of 22

ibm.com/developerWorks/

developerWorks

Figure 21. Update the DE2 BPC Explorer REST API URLs

Update the Business Space

You need to re-register the Business Space REST services endpoint for each DE. Make sure they
will use the virtual host of the corresponding DE, and contain the correct REST Service Gateway
context root of the corresponding DE.

Business Space REST services endpoint registration for DE1

In the admin console, select Servers > Clusters > WebSphere application server clusters >
DE1.AppCluster > REST service endpoint registration. All the information is already updated
automatically (Figure 22). The service endpoint target is DE1 clusters, the host name and port are
Golden1 and 443, and the REST Service Gateway context root is restPS1. Click OK and save it.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 17 of 22

developerWorks

ibm.com/developerWorks/

Figure 22. Business Space REST services endpoint registration for DE1

Business Space REST services endpoint registration for DE2

Similar to DE1, in the admin console, select Servers Clusters > WebSphere application server
clusters > DE2.SingleCluster > REST service endpoint registration. All the information is
updated automatically (Figure 23). Click OK to save it.

Figure 23. Business Space REST services endpoint registration for DE2

Update the hosts file

Update the hosts file on all the computers, including dmgr, custom nodes, and the browser
computers. Add the HTTP server IP address and virtual host of DE1 and DE2. In our example, IHS
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 18 of 22

ibm.com/developerWorks/

developerWorks

IP is "9.110.83.101" and the virtual hosts of DE1 and DE2 are "Golden1" and "Golden2". Add the
following two lines in the hosts file:
9.110.83.101 Golden1
9.110.83.101 Golden2

Update the virtual host info admin command

You also need to run the admin task to modify BPMVirtualHostInfo to let all the transactions go
through IHS, as shown below:
PS C:\BPM\AppServer\profiles\Dmgr01\bin> .\wsadmin.bat -conntype NONE -lang jython
wsadmin>vhs = AdminConfig.list('BPMVirtualHostInfo')
wsadmin>vh = vhs.split()[0]
wsadmin>AdminConfig.modify(vh, [['hostname', 'Golden1']])
wsadmin>AdminConfig.modify(vh, [['port', '443']])
wsadmin>vh = vhs.split()[1]
wsadmin>AdminConfig.modify(vh, [['hostname', 'Golden2']])
wsadmin>AdminConfig.modify(vh, [['port', '443']])
wsadmin>AdminConfig.save()

Update the IHS configurations

After the IBM BPM configurations are complete, generate and propagate the web server plug-in.
In the admin console, select Servers > Server types > Web servers, select your web server, click
Generate Plug-in, and then click Propagate Plug-in. This updates the web server plug-in.

Post configuration verifications

After all the configurations are complete, you need to restart IBM BPM and the IHS environment
and verify that everything works. Make sure that the BPC Explorer, Portal, Business Space, and
other web-based tools can be accessed by the virtual host and all of them work correctly.
In our example, we can access these tools with the following URLs.
For DE1:
BPC Explorer: http://Golden1/bpc
Process Portal: http://Golden1/portal
Business Space: http://Golden1/BusinessSpace
For DE2:
BPC Explorer: http://Golden2/bpc
Process Portal: http://Golden2/portal
Expanding the IBM Business Process Manager V8.5 topology by
using multiple deployment environments

Page 19 of 22

developerWorks

ibm.com/developerWorks/

Business Space: http://Golden2/BusinessSpace

Troubleshooting tips
During your configurations, there are some things you need to notice. Here are some
troubleshooting suggestions:
After you create two DEs, and before all other configurations, verify if your environment
works. For example, start your DE and check the error logs.
After you configure IHS, and before other configurations, verify if you can access all webbased tools via IHS. For example, if you can access them by http://IHSHostname/bpc, then
IHS is working. If you cannot access it, you can try to access web-based tools directly, not via
IHS, for example, http://BPMHostname:port/bpc. If you cannot access it, then the IBM BPM
configuration has problems.
Similarly, it is better to verify your configurations after each step. And if possible, backup your
environment before important configuration steps.
In a double DE environment, there will be more IBM BPM servers running so you may need
more powerful CPUs and more memory. Otherwise, it may take a significant amount of time to
start and stop the environment.
Make sure you update the hosts file on all the machines as we described before. Otherwise,
you may have problems accessing some of the web-based tools.

Conclusion
This article described how to expand the IBM BPM V8.5 topology by using multiple deployment
environments. It provided topology planning, configuration methods according to your
requirements, configuration and post verification steps, and troubleshooting tips.

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 20 of 22

ibm.com/developerWorks/

developerWorks

Resources

Business Process Manager V8.5 Information Center

IBM Redbooks on Business Process Manager
Business Process Manager Product Support
developerWorks BPM zone

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 21 of 22

developerWorks

ibm.com/developerWorks/

About the author

Yu Xiao Li
Xiao Li (Sandy) Yu is an Advisory Software Engineer at the China Software
Development Lab. She has more than 10 years experience in Business Process
Management, which includes system verification testing, function verification testing,
stress testing, and endurance testing.
Copyright IBM Corporation 2014
(www.ibm.com/legal/copytrade.shtml)
Trademarks
(www.ibm.com/developerworks/ibm/trademarks/)

Expanding the IBM Business Process Manager V8.5 topology by

using multiple deployment environments

Page 22 of 22