Contents


Configuring IBM Business Process Manager Advanced Edition V8.5, Part 3

Setting up a three-cluster topology

Comments

Content series:

This content is part # of # in the series: Configuring IBM Business Process Manager Advanced Edition V8.5, Part 3

Stay tuned for additional content in this series.

This content is part of the series:Configuring IBM Business Process Manager Advanced Edition V8.5, Part 3

Stay tuned for additional content in this series.

This article is the third in the series of installation and configuration guides for IBM Business Process Manager (IBM BPM) V8.5 Advanced Edition. In this article, you will set up the recommended three-cluster (also referred to as the Golden topology) Process Server topology. This production topology is connected to a Process Center. The Process Center installation and configuration are assumed to have been performed earlier as described in Part 1.

Figure 1 shows the topology you are going to install and configure in this article. Though the diagram shows the Deployment Manager on a separate machine, we used only two machines. You would need to extend these steps if you want to keep the Deployment Manager on a separate machine.

Figure 1. The Process Server (production) topology to be created
The Process Server (production)                     topology to be created
The Process Server (production) topology to be created

Installing the product

Both DB2® and IBM BPM 8.5 are assumed to be installed previously. A Process Center has been installed and its configuration information is available to use during this configuration process.

Creating and configuring the deployment environment using BPMConfig

You can use the BPMConfig utility to create this production topology. The BPMConfig utility is the recommended approach to build production environments in version 8.5. For more information about the BPMConfig utility, see Using the BPMConfig utility to build and manage deployment environments.

IBM BPM databases

The Advanced Edition of IBM BPM typically works with the following four databases:

  1. Cell level common database
  2. DE level common database
  3. Process Server database
  4. Performance Data Warehouse database

However, IBM BPM production environments support the usage of more than these four databases. A typical deployment environment (DE) level common database contains tables that relate to messaging, Business Space, and Business Process Choreographer. You can store the tables for the components in a separate database, which provides an opportunity to tune them for a better performing BPM runtime. As an example, applications that use a lot of messaging involving the Messaging Engine would benefit from the usage of a separate ME Database. In this article, we will demonstrate how to create seven databases instead of the default four databases.

  1. Cell level database
  2. Common database
  3. Messaging engine database
  4. Process Server database
  5. BPE database
  6. Business Space database
  7. Performance Data Warehouse database
Figure 2. Databases in our Process Server topology
Databases in our Process Server                     topology
Databases in our Process Server topology

The databases that we have used carry a suffix of "PS" to indicate that they are used for a Process Server environment. You are free to choose database names that are appropriate in your environment.

Table 1 shows the databases and the corresponding BPM components that use the information in these databases.

Table 1. Databases
Database nameInformation stored in the database
Cell Level Database
(CELLDBPS)
Application Scheduler, ESB Logger Mediation, Mediations, Relationships
Common Database
(CMNDBPS)
Failed Event Manager, ES
Process Server Database
(BPMDBPS)
Process Server, Embedded ECM
Performance Data warehouse Database (PDWDBPS) Performance Data warehouse
Business Process Choreographer Database (BPEDBPS) BPC
Messaging Engine Database (MEDBPS) Messaging Engine
Business Space Database (BSDBPS) Business Space

There is a cell level database referred to as "CellDBPS". This is a shared database used by one or more deployment environments that are created in this cell. All the other databases are used by the deployment environment.

The creation of these databases is detailed in the section called Database-related configuration.

Preparing the Properties file for deployment environment creation

We want to create a Process Server Golden topology (referred to as a three cluster topology) with a DB2 database using the Advanced Edition of the product. The sample file that you need to start with is: Advanced-PS-ThreeClusters-DB2.properties.

Note: All the sample properties files that are provided with the product support the creation of these four databases. The file in the Appendix is a property file that is based on Advanced-PS-ThreeClusters-DB2.properties and has been amended to support the creation of the three additional databases.

  1. Copy the file Advanced-PS-ThreeClusters-DB2-AdditionalDatabases.properties from the Appendix to a custom directory, such as /opt/bpminstall/configFiles.
  2. Open this copied file Advanced-PS-ThreeClusters-DB2- AdditionalDatabases.properties in a text editor and change the values that are appropriate for your environment. Table 2 captures the key elements that you need to change. It also shows some elements that would not be changed, but they are important for you to understand. The column property value shows the value that we have used. You should change them to values that are appropriate for your environment.
    Table 2. Typical property values to be changed
    Property nameProperty valueDescription
    bpm.de.name PSDE1 The name of the deployment environment.
    bpm.de.deferSchemaCreation true The database tables, schemas, and procedures are created independently. If you want these to be created as part of the BPMConfig execution, change this value to false.
    Note: If this value is set to false, ensure that the databases are created before executing the BPMConfig command.
    bpm.de.psServerName PROD-ProcessServer Any meaningful name for Process Server.
    bpm.de.psPurpose Production Create a production Process Server set up.
    bpm.de.psOffline false
    This Process Server is online and connected to the Process Center that already exists in your environment.
    bpm.de.psProcessCenterHostname vm025.aimsrv.net The host name of the Process Center. Always use the fully qualified domain name for the host names.
    bpm.de.psProcessCenterPort 20019 The port to connect to the Process Center server.
    bpm.de.authenticationAlias.1.user
    DEAdmin1 The user ID that would become the DE Administrator.
    bpm.de.authenticationAlias.1.password <Use your own password> The password for the DE Admin user.
    bpm.de.authenticationAlias.2.user DEAdministrator The user ID for the DE Administrator of the Process Center server to connect.
    bpm.de.authenticationAlias.2.password <Use your own password> The password for the DE Administrator of the Process Center server to connect.
    bpm.de.authenticationAlias.3.user db2inst1 The database user name that is used to connect to the BPM databases.
    bpm.de.authenticationAlias.3.password <Use your own password> The password for the database user specified above.
    bpm.cell.name PROD-PSCell The name of the cell that is created.
    bpm.cell.authenticationAlias.1.user PSCellAdmin The user name for the Cell Administrator.
    bpm.cell.authenticationAlias.1.password Celladmin The password for the Cell Administrator.
    bpm.dmgr.hostname vm023.aimsrv.net The host name of the machine where the deployment manager would reside.
    bpm.dmgr.installPath /opt/IBM/WebSphere/AppServer This should be the <BPM_INSTALL> directory.
    bpm.dmgr.initialPortAssignment 31000 This can be left empty. When specified, the ports that the Deployment Manager uses would be starting with this number.
    bpm.dmgr.soapPort 8879 Leave this as the default. This value is incorrect as the port number would be higher than 31000 (based on the initial Port Assignment value). This value should be changed before executing BPMConfig in the second node.
    bpm.de.cluster.1.name AppCluster The name of the first cluster.
    bpm.de.cluster.1.capabilities Application The cluster's capabilities are defined by this property.
    bpm.de.cluster.1.db ProcessServerDb,SharedDb,
    BPCDb,BusinessSpaceDb
    The databases that are used by the AppTarget cluster.
    Note: These are not the database names. These are the names used to identify the actual database further down in the Property file.
    bpm.de.cluster.2.name MECluster The name of the second cluster.
    bpm.de.cluster.2.capabilities Messaging The cluster's capabilities are defined by this property.
    bpm.de.cluster.2.db MessagingDb The database that is used by the Messaging cluster.
    bpm.de.cluster.3.name SupCluster The name of the third cluster.
    bpm.de.cluster.3.capabilities Support The cluster's capabilities are defined by this property.
    bpm.de.cluster.3.db PerformanceDb The database that is used by the Support cluster.
    bpm.de.node.1.name Node01 The name of the first node. In our case, the first node resides in the same machine as the Deployment Manager. Choose meaningful names and follow the naming conventions that are dictated in your environment.
    bpm.de.node.1.hostname vm023.aimsrv.net The host name of the first node. In our case, the first node resides in the same machine as the Deployment Manager.
    bpm.de.node.1.installPath /opt/IBM/WebSphere/AppServer This should be the <BPM_INSTALL> directory.
    bpm.de.node.1.profileName
    Node1Profile The name of the profile for the first node.
    bpm.de.node.1.initialPortAssignment 35000 The node agent would start using port numbers starting with this value.
    bpm.de.node.1.clusterMember.1.name AppClusterMember1 The name of the App Cluster member.
    bpm.de.node.1.clusterMember.1.initialPortAssignment
    36000 The App Cluster member would start using the port numbers starting with this value.
    bpm.de.node.1.clusterMember.2.name MEClusterMember1 The name of the Messaging Cluster member.
    bpm.de.node.1.clusterMember.2.initialPortAssignment 37000 The Messaging Cluster member would start using the port numbers starting with this value.
    bpm.de.node.1.clusterMember.3.name SupClusterMember1
    The name of the Support Cluster member.
    bpm.de.node.1.clusterMember.3.initialPortAssignment 38000 The Support Cluster member would start using the port numbers starting with this value.
    bpm.de.node.2.name Node02
    bpm.de.node.2.hostname vm025.aimsrv.net The host name of the second node.
    bpm.de.node.2.installPath /opt/IBM/WebSphere/AppServer
    This should be the <BPM_INSTALL> directory.
    bpm.de.node.2.profileName Node2Profile
    The name of the profile for the second node.
    bpm.de.node.2.initialPortAssignment 35000 The node agent would start using the port numbers starting with this value.
    bpm.de.node.2.clusterMember.1.name AppClusterMember2 The name of the App Cluster member.
    bpm.de.node.2.clusterMember.1.initialPortAssignment 36000 The App Cluster member would start using the port numbers starting with this value.
    bpm.de.node.2.clusterMember.2.name MEClusterMember2 The name of the Messaging Cluster member.
    bpm.de.node.2.clusterMember.2.initialPortAssignment 37000 The Messaging Cluster member would start using the port numbers starting with this value.
    bpm.de.node.2.clusterMember.3.name SupClusterMember2 The name of the Support Cluster member.
    bpm.de.node.2.clusterMember.3.initialPortAssignment 38000 The Support Cluster member would start using the port numbers starting with this value.
    bpm.de.db.1.databaseName CMNDBPS The name of the DE Level Common database
    bpm.de.db.1.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.1.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.1.schema db2inst1 The schema name for the Common Database tables.
    bpm.de.db.2.databaseName BPMDBPS The name of the Process Server database.
    bpm.de.db.2.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.2.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.2.schema db2inst1 The schema name for the BPM database tables.
    bpm.de.db.3.databaseName
    PDWDBPS
    The name of the Performance Data Warehouse (PDW) database.
    bpm.de.db.3.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.3.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.3.schema db2inst1 The schema name for the PDW database tables.
    bpm.de.db.4.databaseName CELLDBPS The name of the Cell Scoped database.
    bpm.de.db.4.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.4.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.4.schema db2inst1 The schema name for the CELLDB tables.
    bpm.de.db.5.name MessagingDb The key for the Messaging database. This key is used in the cluster configuration.
    bpm.de.db.5.dbCapabilities Messaging
    This indicates that this database will contain tables related to the Messaging capability.
    bpm.de.db.5.databaseName
    MEDBPS The name of the messaging database.
    bpm.de.db.5.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.5.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.5.schema db2inst1 The schema name for the Messaging DB tables.
    bpm.de.db.6.name BusinessSpaceDb The key for the Business Space database. This key is used in the cluster configuration.
    bpm.de.db.6.dbCapabilities BusinessSpace The capability of this database.
    bpm.de.db.6.databaseName BSDBPS The name of the Business Space database.
    bpm.de.db.6.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.6.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.6.schema db2inst1 The schema name for the Business Space tables.
    bpm.de.db.7.name BPCDb The key for the BPC database. This key is used in the cluster configuration.
    bpm.de.db.7.dbCapabilities BPC The capability of this database.
    bpm.de.db.7.databaseName BPCDBPS The name of the BPC Space database.
    bpm.de.db.7.hostname vm023.aimsrv.net The host name of the machine hosting the DB2 database.
    bpm.de.db.7.portNumber 50000 The port number to communicate with the DB2 database.
    bpm.de.db.7.schema db2inst1 The schema name for the BPC tables.
  3. Use the BPMConfig command to generate the deployment environment. Open a terminal window and change directories to <BPM_INSTALL>\bin. Issue the following command. The output is shown in Figure 3.
    ./BPMConfig.sh -create -de /opt/bpminstall/configFiles/ Advanced-PS-ThreeClusters-DB2- AdditionalDatabases.properties
    Figure 3. Output of BPMConfig
    Output of BPMConfig
    Output of BPMConfig
  4. Ensure that the last line at the completion of the BPMConfig command reads the same as shown in Figure 3. This creates a three-cluster Process Server topology in the first machine.

    We now have two profiles created in this machine:

    • DmgrProfile
    • Node1Profile
  5. You can verify this by using the listProfiles command. In a terminal window, type the following command and press Enter:
    ./manageprofiles.sh -listProfiles
  6. The terminal window displays the following results:
    [DmgrProfile, Node1Profile]

    Our topology should have another profile, Node2Profile, which is created in a second machine.

    The creation of Node2Profile has two pre-requisites:

    • The Deployment Manager is in a started state.
    • The port number that the Deployment Manager listens to for SOAP requests.

Start the Deployment Manager:

  1. In a terminal window, change directories to <BPM_INSTALL>/profiles/<DmgrProfileName>/bin.
  2. Issue the command ./startManager.sh. The Deployment Manager starts up.
  3. Change directories to:
    <BPM_INSTALL>/profiles//<DmgrProfileName>/config/cells/PROD-PSCell/nodes/Dmgr
  4. View the serverindex.xml file and locate the SOAP_CONNECTER_ADDRESS.
  5. Make note of the port number as shown in Figure 4. This is used in the property file while we create Node2Profile.
    Figure 4. Deployment Manager's SOAP connect port
    Deployment Manager's SOAP connect                     port
    Deployment Manager's SOAP connect port

Note: The value in your environment could be different from what you see in Figure 4.

You will create the Node2Profile after you create the databases and its associated tables and procedures.

Database-related configuration

BPMConfig also generates the database scripts as part of this process. These scripts are created under <BPM_INSTALL>/profiles/<DmgrProfileName>/dbscripts. This directory contains two sub-directories:

  • Cell scoped database: This is represented by the "PROD-PSCell" directory shown in Figure 5.
  • Deployment environment scoped databases: This is represented by the "PSDE1" in Figure 5.
Figure 5. Database scripts generated by BPMConfig
Database scripts generated by BPMConfig
Database scripts generated by BPMConfig

Copy the db scripts from <BPM_INSTALL>\profiles/<DmgrProfileName>/dbscripts to another directory, such as /opt/bpminstall/dbscripts.

Note: The createDatabase.sh script contains a step that grants database administrative privileges to the user ID that IBM BPM uses to connect to the databases. In our case, it is "db2inst1". If the script itself is executed using the db2inst1 user ID, then a warning message, An authorization ID cannot grant a privilege or authority to itself, is displayed. This script is typically executed by another user who has the appropriate privileges and has access to the DB2 executables to run DB2 commands. By default, the "root" user might not have privileges to run DB2 executables. If you use the root user ID to execute these database scripts, ensure that it has the right privileges/access setup before executing the following commands described below.

Create the cell level database and tables:

  1. Create the Cell Scoped Common database, CELLDBPS:
    1. Open a terminal and change the directory to /opt/bpminstall /dbscripts/<cellName>/DB2/CELLDBPS.
    2. On the command prompt, issue: ./createDatabase.sh. Ensure that the database is created successfully.
  2. Create the tables and indexes in the CELLDBPS database: Execute the following commands:
    db2 connect to CELLDBPS USER db2inst1 USING <password>
    db2 -tvf createSchema_Advanced.sql
    db2 connect reset
  3. Create the DE Scoped common database, CMNDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/CMNDBPS.
    2. Issue ./createDatabase.sh. Ensure that the database is created successfully.
  4. Create the tables and indexes in the CMNDBPS database. Execute the following commands:
    db2 connect to CMNDBPS USER db2inst1 USING <password>
    db2 -tvf createSchema_Advanced.sql 
    db2 connect reset
  5. Create the Messaging Engine database, MEDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/MEDBPS.
    2. Issue ./createDatabase.sh. Ensure that the database is created successfully.
  6. Create the tables and indexes in the MEDBPS database. Execute the following commands:
    db2 connect to MEDBPS USER db2inst1 USING <password>
    db2 -tvf createSchema_Messaging.sql
    db2 connect reset
  7. Create the Business Space database, BSDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/BSDBPS.
    2. Issue ./createDatabase.sh. Ensure that the database is created successfully.
  8. Create the tables and indexes in the BSDBPS database. Execute the following commands:
    db2 connect to BSDBPS USER db2inst1 USING <password>
    db2 -tvf createSchema_Advanced.sql
    db2 connect reset
  9. Create the Business Process Choreographer database, BPCDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/BPCDBPS.
    2. Issue ./createDatabase.sh. Ensure that the database is created successfully.
  10. Create the tables and indexes in the BPCDBPS database. Execute the following commands:
    db2 connect to BPCDBPS USER db2inst1 USING <password>
    db2 -tvf createSchema_Advanced.sql
    db2 connect reset
  11. Create the BPM database, BPMDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/BPMDBPS.
    2. Issue ./createDatabase.sh. Ensure that the database is created successfully.
  12. Create the tables and indexes in the BPMDBPS database. Execute the following commands:
    db2 connect to BPMDBPS  USER db2inst1 USING <password>
    db2 -tvf  createSchema_Advanced.sql
    db2 -tdGO -vf  createProcedure_Advanced.sql
    db2 connect reset
  13. Create the Performance Data Warehouse database, PDWDBPS:
    1. Change the directory to /opt/bpminstall/dbscripts/<DEName>/DB2/PDWDBPS.
    2. Issue ./createdatabase.sh. Ensure that the database is created successfully.
  14. Create the tables and indexes in the PDWDBPS database. Execute the following commands in the DB2 command prompt:
    db2 connect to PDWDBPS  USER db2inst1 USING <password>
    db2 -tvf  createSchema_Advanced.sql
    db2 connect reset

Bootstrapping the database with the system data

The deployment environment, databases, and database tables are now created, but they still do not have the required data in the various databases. You need to populate the databases with the required data manually by executing the bootstrapProcessServerData script before the servers in the deployment environment are started.

Note: This step is required as we have chosen to defer the schema creation in our configuration file.

This bootstrap process performs two key activities:

  • Imports the toolkits: A number of toolkits, such as the system toolkit and system coaches to name a few, are added to the database to be used by the various process applications.
  • Imports the resource bundle groups: The process portal application, which the end users would use, supports multiple languages (depending on what is chosen during the installation process). The resource bundles representing the various locales are imported to the database.

Note: This bootstrap process does not require the Deployment Manager or other servers to be running. The "wsadmin" command (used by the bootstrap process) runs in a disconnected mode.

Perform the bootstrap process by issuing the following commands:

  1. Open a terminal and change to the bin directory of the Deployment Manager:
    <BPM_INSTALL_DIR>\profiles\DmgrProfile\bin.
  2. On the terminal, issue:
    ./bootstrapProcessServerData.sh -clusterName AppCluster

    AppCluster is the name of the Application Target cluster.

Creating the Node02 profile

  1. Copy the file Advanced-PS-ThreeClusters-DB2.properties that you created in the first machine to the second machine, where Node02Profile would be created. Copy this to a custom directory, such as /opt/bpminstall/configFiles.
  2. Change this property in the Property file to the appropriate value identified earlier before executing the BPMConfig command on this machine.
    # Deployment manager soap port.bpm.dmgr.soapPort=31003

    Note: The port number specified above is what we found in the first machine when we performed our installation. Do not use this number as-is. Determine the corresponding value in your deployment manager and place this value here.

  3. Open a terminal and change directories to <BPM_INSTALL>\bin. Issue:
    ./BPMConfig.sh -create -de /opt/bpminstall/configFiles/ Advanced-PS-ThreeClusters-DB2-AdditionalDatabases.properties
    Figure 6. Output of BPMConfig
    Output of BPMConfig
    Output of BPMConfig

Similar to the results of the execution of BPMConfig in the first machine, observe and ensure that BPMConfig completed successfully.

Exploring the deployment environment

Switch over to the first machine and start the deployment environment and explore it using the administrative console.

  1. Open a terminal window and change to the bin directory of the Deployment Manager:<BPM_INSTALL_DIR>\profiles\<DmgrProfile>\bin.
  2. On the command prompt, issue ./BPMQuickStart.sh PSDE1 DmgrProfile.

    This starts the Quick Start window for the "PSDE1" deployment environment

  3. Click on the Start the Process Server Deployment Environment to start the DE.
  4. Once the DE is started, launch the admin console using the WebSphere Application Server Administrative Console link in the Quick start window.
  5. Log in using the credentials of <deadministrator>/<deAdminpassword>.
  6. Expand Servers and click Deployment Environments.
    Figure 7. Process Server deployment environment
    Process Server deployment                     environment
    Process Server deployment environment
  7. Observe from Figure 7 that the "PSDE1" deployment environment is in a partially started state. The start of the deployment environment can only start the servers that are hosted on this machine. Notice that the node agents and servers are not started in the second machine that hosts Node2Profile.
  8. Switch to the second machine and start the node agent:
    1. Open a terminal window and change directories to <BPM_INSTALL_DIR>\profiles\Node2Profile>\bin.
    2. Issue ./startNode.sh. Wait for the node agent to start completely before proceeding further.
  9. Select the check box to the left of PSDE1 and click on Start. This attempts to start the deployment environment (Figure 8).
    Figure 8. Deployment environment status is started
    Deployment environment status is started
    Deployment environment status is started

    Wait for a few minutes (at least 5-8 minutes) and click on Deployment Environments to see that the status has changed from partially started to a started state.

  10. Click on PSDE1 to see the constituents of the deployment environment as shown in Figure 9.
    Figure 9. Three-cluster deployment environment
    Three-cluster deployment                     environment
    Three-cluster deployment environment

    The message at the top seems to suggest that the deferred configuration steps have not been completed yet.

  11. Click on the Deferred Configuration link to examine the instructions.
    Figure 10. Deferred configuration
    Deferred configuration
    Deferred configuration

    We have already completed these three steps earlier and the configuration should have reflected this. Click on Configuration Done as shown in Figure 10 and save the changes to the master configuration.

    Figure 11. Deferred configuration is completed
    Deferred configuration                      is completed
    Deferred configuration is completed
  12. Click on Close (Figure 11) and explore the topology of the deployment environment. Refer to the Part 1 of this series for detailed instructions to explore the DE using the administrative console.

Verifying the deployment environment

The installation does not currently have any applications deployed on it. Launch the Process Center console to deploy a sample application before attempting to perform the verification steps.

  1. Login to the Process Center console.
  2. Click on the Hiring Sample Application and install it to Process Server.
  3. Use the instructions in the Verifying Deployment environment section in Part 1 of this series to complete the verification process.

Appendix

You can download the Advanced-PS-ThreeClusters-DB2.properties file to view its content.

Conclusion

Part 3 of this series described the process of setting up a three-cluster Process Server topology that you can use in production environments. This series described the setup of a typical IBM BPM 8.5 environment comprising of Process Centers and Process Servers. The series also introduced the BPMConfig utility and demonstrated how to set up both single-cluster and three-cluster Process Server environments.

Acknowledgments

The author would like to thank Volker Hoss, Xiang Wu, and Neil Kolban for their valuable input and review of this article series.


Downloadable resources


Related topics


Comments

Sign in or register to add and subscribe to comments.

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management
ArticleID=975825
ArticleTitle=Configuring IBM Business Process Manager Advanced Edition V8.5, Part 3: Setting up a three-cluster topology
publish-date=06302014