Professional Documents
Culture Documents
Configuring IBM Business Process Manager Advanced Edition V8.5, Part 1
Configuring IBM Business Process Manager Advanced Edition V8.5, Part 1
Configuring IBM Business Process Manager Advanced Edition V8.5, Part 1
This three-part article series describes the installation and configuration steps to establish a
typical IBM® Business Process Manager V8.5 clustered environment for the Advanced Edition
of the product. The first article of this series focuses on the recommended topology for non-
production deployments that is referred to as the "single cluster” topology.
Introduction
This three-part series guides you in establishing a business process management environment
with commonly used topologies, using IBM Business Process Manager (BPM) Advanced Edition
V8.5. This series starts with a quick overview of the key components of an IBM BPM topology and
guides you through different installation and configuration approaches.
This series uses both Process Center and Process Server to provide guidance in setting up both
these environments.
The following installation scenarios for IBM BPM Advanced are covered in this series:
Figure 1 shows the complete setup of a IBM BPM environment that we will be creating at the end
of this series.
Deployment Manager Administrative component of a cell that is used to manage all the
constituents of a cell. Each cell contains a Deployment Manager.
Deployment Manager is often referred to as "DMgr".
Node Agent Administrative component in a specific node that is used to manage the
constituents of a node. Each node contains a node agent.
Deployment Environment A collection of servers or clusters that are managed together. The
Deployment Environment is often referred to as "DE".
IBM BPM V8.5 introduced first-class support to create multiple DEs in a
cell.
Figure 2 shows the topology we are going to install and configure in this article.
The topology shown in Figure 2 consists of a single physical node hosting three JVMs:
• Deployment manager
• Node agent
• Server instance
Why are we setting up a network deployment environment? Isn't the standalone Server Profile
that we are used to in the previous versions a better option for development servers? Standalone
servers are no longer available (unless we work with the Express Edition of the product or
looking at the Integrated/Unit Test Environment in IBM Integration Designer). For ease of use, the
Integrated/Unit Test environment is referred to as "UTE" and IBM Integration Designer is referred
to as Integration Designer in this article series.
Table 2 summarizes the profile types that are supported in Advanced Edition.
Product installation
This article assumes that the database used by IBM BPM to store its configuration and runtime
information is a pre-installed DB2® database. If you decide to install DB2 Express as part of your
IBM BPM installation, you should kick-start the installation process using an "Administrative" user
ID. If you perform your installation as a non-administrative user, then the option to install DB2
Express cannot be selected. The choice of user names and passwords are left to the discretion of
the reader.
cellAdministrator <password of your choice> Cell Administrators can perform any cell-wide
administration activity.
db2admin <password of your choice> Credentials that the IBM BPM server uses to
connect to the DB2 database.
Note: The administrative accounts in IBM BPM V8.5 are now separated into multiple levels. You
have administrative privileges for a cell, which is specified in the Cell administrative account
1. Specify the appropriate database credentials and database names and click Next. In this
case, we have chosen to reuse an existing DB2 installation (Figure 5). The installation
process creates and initializes the required databases.
Figure 5. DB2 database related information
Note: The database specified here can either be a local database or a remote database.
However, the databases can only be created locally. This restriction is not new and has
existed in the previous versions of the product.
2. You are presented with the Installation Summary. Read and accept the license agreement
and notices. You can opt to specify a "support account" credentials. This is the IBM ID and
password that you would typically use to download fixes and patches from repositories
such as Fix Central. We chose not to include updates with this installation. Click on Install
Software to proceed as shown in Figure 6.
Note: It has been observed that when you choose to include updates along with the
installation, you experience failures on a few occasions. It is a good idea to uncheck this box
and apply the appropriate fixes as a separate activity.
3. The installation starts and its progress is indicated by the progress bar. The key installation
information is available for printing during this process, as shown in Figure 7.
Figure 7. Installation progress
Note: The "Show passwords" is turned on intentionally in Figure 7 to demonstrate that you
can view the password by checking this box. Use the Print button in this window to preserve
a copy of the installation information.
4. A successful installation results in the following window popping up (Figure 8).
Figure 8. Installation results
Note: The "First Steps" window (in the previous versions) is replaced with a "Quick Start" window
that allows you to work with a deployment environment (instead of individual servers).
Note: This topology results in three JVMs running on a single physical box imposing considerable
demands on memory and CPU. Starting the DE could be slow in low-end machines. Ensure that
the machines have adequate hardware specifications before attempting to install and start the
Deployment Environments.
The first steps window of previous versions is replaced with this new Quick Start window.
1. Launch the Quick Start window by clicking on Process Center Quick Start (Start >
Programs > IBM > Business Process Manager Advanced 8.5 > Process Center Quick
Start).
Note: The short cut to "ProcessCenter Quick Start" does not appear in Microsoft® Windows®
Server 2012 or Windows 8. This is a known issue.
2. A command window (Figure 9) shows up and it is followed by the actual Quick start window.
3. In contrast to the previous versions, where the first steps window was not secured, the Quick
Start window is protected. You need to provide the relevant credentials before starting and
stopping the deployment environments.
Note: If an incorrect userid/password combination is specified, then the cluster member
server does not start even though this does not affect the start of the deployment manager
and node agent. The logs contain the error information, but the Quick Start window does not
provide any clues that the credentials were incorrect or did not have the required privileges to
complete this operation.
4. Once the login is successful, the Quick Start window provides an option to start the
deployment environment (DE), as shown in Figure 10.
Figure 10. Quick Start window
5. Click on Start the Process Center Deployment Environment to start the DE.
6. A command window (Figure 11) contains the command line options that are used to start
the components of the DE. The process starts with a start command for the Deployment
Manager.
Figure 11. Deployment environment start up window
7. Once the DE is started, the Quick Start window contents change. A number of links are now
available along with the option to stop the DE.
Note: Once the servers are started, the window in Figure 11 shows this message: "Press any
key to continue". Press one of the keys in this window as the Quick Start window refreshes only
after this activity is performed. Also, it has been observed that a considerable time elapses before
the status check operation returns and the additional options show up in the Quick Start window
(Figure 12).
Figure 12. Quick Start window with links to consoles and tools
1. Click on WebSphere Application Server Administrative Console in the Quick Start window
to open the Integrated Solutions Console.
2. Log in using the credentials of <cell administrator>/<cell admin password>.
3. Expand Servers and click Deployment Environments.
Figure 13. Deployment environment
4. Notice that a DE named "ProcessCenter" is created and is in "Started" status signified by the
green arrow as shown in Figure 13.
5. Click on ProcessCenter to see the constituents of the deployment environment (Figure 14).
6. Click on SingleCluster. This opens up the Configuration tab for this deployment environment.
Click on the Local Topology tab (Figure 15) and expand the plus sign to the left of the single
cluster to view the constituents of this topology.
Figure 15. View of the single cluster topology
Note:The default names are used for cluster, node, and server names as shown in Table 4.
Table 4. Default names
Component Default name
Node Node1
Cluster SingleCluster
7. Click on the ProcessCenter breadcrumb and click on Authentication Aliases to see the
credentials that are defined (Figure 16).
The number of roles has changed. A typical installation uses a single authentication alias,
DeAdminAlias, for all these user roles. The alias refers to the deployment environment
administrative account that you specified during the installation process.
Note: A separate article in the future will cover this area in detail about the choice of
authentication aliases that are appropriate for a hardened production environment.
8. In the navigation frame of the console, expand Service Integration and click Buses. This
displays the SI Buses that are present in this topology.
Figure 17. SI Bus that is used by the deployment environment
Notice that only a single SI Bus is present. This is a significant change from the earlier versions
where a number of SI Buses were used, depending on the topology that was created.
1. Let's examine the database tables that are created and verify that the expected number of
tables exist in the three databases:
a. In a command prompt window, type db2cmd.
b. In the resulting command prompt window, issue the following commands:
db2 connect to CMNDB user db2admin using xxxxxxx
db2 list tables for schema DB2ADMIN> commondbtables.txt
c. View the file commondbtables.txt using a text editor. There should be 282 tables. Nine of
these tables are listed in Table 5 should start with the prefix "SIB". These are related to
the Messaging Engine.
Table 5. List of Messaging Engine related tables
Table/View Schema Type
SIB000 DB2ADMIN T
SIB001 DB2ADMIN T
SIB002 DB2ADMIN T
SIBCLASSMAP DB2ADMIN T
SIBKEYS DB2ADMIN T
SIBLISTING DB2ADMIN T
SIBOWNER DB2ADMIN T
SIBOWNERO DB2ADMIN T
SIBXACTS DB2ADMIN T
LSW_COLUMN DB2ADMIN T
LSW_DATA_TRANSFER_ERRORS DB2ADMIN T
LSW_LOAD_TRACE DB2ADMIN T
LSW_OPTIMIZER_DATA DB2ADMIN T
LSW_PRI_KEY DB2ADMIN T
LSW_SNAPSHOT DB2ADMIN T
LSW_SYSTEM DB2ADMIN T
LSW_SYSTEM_SCHEMA DB2ADMIN T
LSW_TABLE DB2ADMIN T
LSW_TASK DB2ADMIN T
LSW_TIMING_INTERVAL DB2ADMIN T
LSW_TIMING_INTERVAL_BOUND DB2ADMIN T
LSW_TIMING_INTERVAL_VALUE DB2ADMIN T
LSW_TRACKED_FIELD DB2ADMIN T
LSW_TRACKED_FIELD_USE DB2ADMIN T
LSW_TRACKING_GROUP DB2ADMIN T
LSW_TRACKING_POINT DB2ADMIN T
LSW_TRACKING_POINT_VALUE DB2ADMIN T
LSW_USER_MAPPINGS DB2ADMIN T
LSW_USR_XREF DB2ADMIN T
LSW_VIEW DB2ADMIN T
PS_WLSTORE DB2ADMIN T
6. Let's now try out the Process Admin Console. Click on the Process Admin Console link in
the Quick Start window. The Process Admin Console opens up in a web browser.
Note: You might not be challenged for your credentials as you are already logged in the
administrative console as a cell administrator. It is a good idea to log out as cell administrator
and log in as DE administrator for all activities that are related to the IBM BPM environment
and use the cell administration account for typical WebSphere Application Server-related
administration activities.
7. Let's explore the list of predefined users defined in the environment. Expand User
Management and click on User Management:
a. Enter * in the Retrieve Profile field and click on Retrieve to get all the users that are
defined.
b. Observe that there are only two users defined - cellAdministrator and deAdministrator -
as shown in Figure 18.
10. A number of process applications should be present in Process Center (Figure 19). Download
Process Designer and play with the sample applications to ensure that the set up is
functional.
11. Let's conclude our verification steps by launching the Process Portal using the Quick Start
window link:
a. The dashboard should be empty. Click on Standard HR Open New Position to launch a
process instance.
b. Work with Process Portal to complete the tasks and then work through the various
process steps to ensure that the Hiring Sample application functions as expected.
Conclusion
Part 1 of this series described the process of setting up a single cluster topology that reflects the
default configuration for development environments of IBM BPM V8.5 by using a typical installation
process. In Part 2, we guide you through the set up of a single-cluster Process Server environment
using the custom installation approach.
Acknowledgments
The author would like to thank Volker Hoss, Xiang Wu, and Neil Kolban for their valuable input
and review of this article series.
Related topics
• IBM Business Process Manager Advanced detailed system requirements
• Technote: Starting or stopping the IBM BPM deployment environment from the Quick Start
console does not work with incorrect username and password
• Technote: IBM BPM V8.5 does not support running with WebSphere Application Server ND
V8.5 Java 7
• Technote: IBM Installation Manager V1.6.3 or later is required before installing IBM BPM on
Solaris 11
• IBM Redbook: Business Process Management Deployment Guide Using IBM Business
Process Manager V8.5
• IBM Business Process Manager Developer Center
• IBM developerWorks Middleware: Get the latest technical resources on IBM BPM and other
middleware solutions, including downloads, demos, articles, tutorials, events, videos, and
more.