IBM Business Process Manager provides all the capabilities for the various phases of BPM, such as modeling, designing, executing, monitoring, and optimizing business processes. The components of Business Process Manager provide a unified repository, tooling for authors, administrators and users, and a runtime platform. Figure 1 shows a typical Business Process Manager configuration that includes a WebSphere Process Center repository, a WebSphere Process Server runtime environment, and authoring tools such as IBM Process Designer (hereafter called Process Designer) and IBM Integration Designer (hereafter called Integration Designer).
Figure 1. Typical Business Process Manager configuration
Figure 1 shows a full set of the components provided by Business Process Manager products. These components may vary for the different editions of IBM Business Process Manager, which include Express, Standard, and Advanced. Business Process Manager Express and Business Process Manager Standard provide fundamental integration capabilities and do not include Integration Designer. For more details about how different configurations support different levels of complexity, see IBM Business Process Manager V7.5 development topology recommendations.
A typical installation is the simplest way to set up a Business Process Manager environment. It provides many defaults and minimizes user input. It is suitable for setting up the environment for development, test, non-clustered staging, and simple production for new users.
This article focuses on a typical installation for runtime servers that include WebSphere Process Center (hereafter called Process Center) and WebSphere Process Server (hereafter called Process Server). Process Designer is also included as it will be installed together with Process Center on a Windows® platform. Instructions for a typical installation of Integration Designer are not within the scope of this article. For more details about Integration Designer, refer to the IBM Integration Designer Information Center. The operating system used in this article, including the screen captures, is Windows. It is similar for other operating systems when using a typical installation, with minor differences such as some defaults values or paths.
Setting up the Process Center environment
Process Center is the environment where all processes, services, and other assets created in the IBM Business Process Manager authoring tools, including Process Designer and Integration Designer, can run and playback. It includes the Process Center repository and runtime.
The Process Center repository is the central repository for all processes, services, and other assets created in the IBM Business Process Manager authoring environments. The Process Center runtime includes an integrated Process Center server and Business Performance Data Warehouse, allowing users working in Process Designer to run their process applications and store performance data for testing and playback purposes during development efforts. When the process design is finished and the processes are ready to deploy, the same processes can be installed and run on Process Server in the runtime environments.
There are two approaches to install the runtime Process Center server: typical installation and custom installation. The differences and conditions for each approach are addressed in the following section.
Operating systems and prerequisites
The supported operating systems are AIX®, Linux®, Solaris®, and Windows. In this article, the Windows system is used for reference. For a detailed list of operation system and software prerequisites, refer to Preparing the operating systems for product installation in the Business Process Manager Information Center.
Considerations for typical installation or custom installation
The typical installation option in Business Process Manager provides the simplest option for the runtime server setup. It provides many defaults and minimizes user input. It is suitable for setting up the environment for development, test, non-clustered staging, and simple production for new users. However, a custom installation provides more customization and scalability for runtime environments, including a clustered environment or a complex deployment environment.
There are a few situations in which a typical installation does not apply, in which you need to use a custom installation. You can use the Profile Management Tool (PMT) to build such complex deployment environments. Following are conditions where a typical installation does not apply:
- For a complex deployment environment requirement:
- A clustered environment is required.
- A customized deployment or database topology is required.
- The existing WebSphere Application Server package group is reused.
- Incompatible bit structure case; for example, a 32-bit product needs to be installed on a 64-bit system.
If the above constraints do not apply to your condition, congratulations! You can easily set up your runtime environment with only a few clicks. This creates a typical standalone profile for Process Center.
If you do not have any database requirements, a typical installation with an embedded DB2® Express is the best way. The installation process will install a DB2 Express database for you, and take care of the database creation and configuration automatically.
Note that the administrative user name and password on Windows® are
bpmadmin1. The Instance user name and password
on Linux are
bpminst1. Make sure the default password
complies with the password policy on your operating system, such as
Windows 2008 or Linux, before using the embedded database. If the default
password does not apply, or there is a specific database requirement such
as reusing existing database, you need to manually create the required
Process Server database and Process Data Warehouse in advance.
The supporting databases for Business Process Manager Express or Standard include Process Server and Performance Data Warehouse databases. For Business Process Manager Advanced, there is one more database called the common database. In the following sections, the configurations and steps are based on Business Process Manager Standard. If you are using Business Process Manager Advanced, creating the additional common database with the same parameters illustrated here in this article should also work.
Preparing databases for typical installation
If you plan to use the embedded DB2 Express database, you do not need to create the databases in advance. A typical installation will create the databases once the DB2 Express database is installed. However, if you choose any supported databases, including DB2, Oracle®, or SQL Server for your environment using a typical installation, you need to create the supporting databases for Process Center component in advance.
Depending on the databases used, choose one of the following steps for the database creation:
Creating databases with DB2
If you choose to install with DB2 databases, create the necessary databases before installing the Business Process Manager software. The necessary databases for Business Process Manager Standard are:
- BPMDB, the Process Server database
- PDWDB, the Performance Data Warehouse database
There is an additional CMNDB (the common database) to be created for Business Process Manager Advanced. The setup for Business Process Manager Standard is shown in the following steps.
The DB2 databases have a few requirements in order to make the Business
Process Manager software work. The page size for the database is
32 KB, and the databases encoding is
UTF-8 if non-ASCII characters are used.
- Copy the following script in Listing 1 to a text editor tool and save
it as a local file named
Listing 1. DB2 SQL scripts for Business Process Manager database creation
-- create the database: create database BPMDB automatic storage yes using codeset UTF-8 territory US pagesize 32768; -- connect to the created database: connect to BPMDB; --The following grant is used for databases without enhanced security. --For more information, review the Info Center for Enhancing Security for DB2. grant dbadm on database to db2admin; connect reset; -- create database PDWDB automatic storage yes using codeset UTF-8 territory US pagesize 32768; -- connect to the created database: connect to PDWDB; --The following grant is used for databases without enhanced security. --For more information, review the Info Center for Enhancing Security for DB2. grant dbadm on database to db2admin; connect reset;
- Open a DB2 command window and execute the above SQL script by issuing
db2 –tf createDatabase.sql. This creates the BPMDB and PDWDB databases, and grants the user
db2admindatabase administrator (DBA) authority for both databases.
Creating databases with Oracle
Different users are used to differentiate the configurations for the Process Center and Performance Data Warehouse databases. You need to enable the Oracle database with Unicode to support non-ASCII characters. Make sure your Oracle database is using the AL32UTF8 character set, which has full international support. Also, for the Process Center and Performance Data Warehouse database users, adequate authority, including the DBA role, is required.
In the following sample, you use the
user for Process Center and
Performance Data Warehouse. Assume that the Oracle instance ID is
- Create an Oracle database as follows:
- Login with user
oracleand launch the Database Configuration Assistant with command dbca.
- On the Welcome page, click Next.
- On the "Select the operation" page, choose Create a Database and click Next.
- On the "Templates Selection" page, keep the default "General Purpose or Transaction Processing" and click Next.
- On the "Oracle Database Name" page, set the Global Database
Name with ORCL and keep the System Identifier
(SID) with ORCL, as shown in Figure 2, and click
Figure 2. Set Oracle database name and SID
- On the "Enterprise Manager" page, keep the default and click Next.
- On the "Specify passwords" page, type the passwords for each
user separately, or choose Use the Same Administrative
Password for All Accounts, and enter one set of
the password, as shown in Figure 3, and click
Figure 3. Set administrative password
- On the "Storage type" page, keep all the defaults and click Next.
- On the "Recovery options" page, keep all the default and click Next.
- On the "Sample Schemas" page. Keep all the defaults and click Next.
- On the "Configuration for Memory, Sizing, Character Sets,
Connection Mode" page, click the Character
Sets tab, choose Use Unicode
(AL32UTF8), keep the defaults for the other tabs,
as shown in Figure 4, and click Next.
Figure 4. Set Character Sets to Unicode
- On the new page, click Finish to create the ORCL database.
- Login with user
- Create multiple schemas on the ORCL database:
- Copy the script shown in Listing 2 to a text editor tool. Save
it in a local file named
Listing 2. Oracle SQL scripts for users creation
REM create the Process Center user WBPPC00 with password wppcuser create user WBPPC00 identified by wppcuser; REM grant necessary roles to user grant connect, resource, unlimited tablespace to WBPPC00; grant execute on dbms_system to WBPPC00; grant javauserpriv to WBPPC00; GRANT "DBA" TO WBPPC00; REM create the Performance Data Warehouse user WBPDW00 with password wpdwuser create user WBPDW00 identified by wpdwuser; REM grant necessary roles to user grant connect, resource, unlimited tablespace to WBPDW00; grant execute on dbms_system to WBPDW00; grant javauserpriv to WBPDW00; GRANT "DBA" TO WBPDW00; REM Commit work COMMIT; EXIT
- Execute createDatabase.sql by typing the
following commands as the user
oracle. It creates the WBPPC00 and WBPDW00 users and grants users with the necessary roles to work correctly.
sqlplus sys/<yourPassword>@ORCL AS SYSDBA @createDatabase.sql
- Copy the script shown in Listing 2 to a text editor tool. Save it in a local file named
Creating databases with SQL Server
Make sure the server hosting the SQL Server has enabled XA transactions and configured the JDBC Distributed Transaction Components before creating the databases. The configuration steps are found at the online configuration instructions, depending on your SQL Server version. Only the "Running the MS DTC Service" and "Configuring the JDBC Distributed Transaction Components" steps need to be done before creating the databases. The "Configuring the User-Defined Roles" is done in Step 8 in grant the SqlJDBCXAUser role for the login user.
When using SQL Server, you need to create all the necessary databases before installing the Business Process Manager software. The necessary databases for Business Process Manager Standard are:
- BPMDB, the Process Server database
- PDWDB, the Performance Data Warehouse database
You also need to create an additional CMNDB, the common database for Business Process Manager Advanced. Note that CMNDB has a different "collation" setting with BPMDB and PDWDB, where CMNDB requires case-sensitive collation. However, BPMDB and PDWDB require case-insensitive collation.
The steps to create and configure these databases will be introduced in the following sections. You will use the name "BPMDB" for the Process Server database with the related database user "ppcuser", and "PDWDB" for the Performance Data Warehouse database name with the related database user "pdwuser".
Note the collation differences for CMNDB with BPMDB and PDWDB when creating the databases. You can use:
COLLATE SQL_Latin1_General_CP1_CI_ASfor BPMDB and PDWDB
- Launch the Microsoft® SQL Server Management Studio.
- Create the Login user "ppcuser" for the Process Server database by
selecting Security > Logins > New Login section for the
database server. Choose SQL Server
authentication and enter the password for ppcuser, as
shown in Figure 5.
Figure 5. New user for Process Center database
- Create the database
BPMDBfor the Process Center Server, as shown in Figure 6.
Figure 6. Create BPMDB for Process Center
- Click Options to edit the database options, including
setting the Collation field to
SQL_Latin1_General_CP1_CI_AS for BPMDB, and the
Parameterization option to
Forced, as shown in Figure 7. Click
OK to create the BPMDB database.
Figure 7. Set the database properties for BPMDB
- Expand BPMDB > Security > Users, right-click
and choose New User to open the "Database User – New"
window. Set the User name field to ppcuser and the
Login name field to ppcuser, and click
db_owner in the Database Role membership section,
as shwon in Figure 8.
Figure 8. Database User – New window
- Create the schema by selecting Security > Schemas
for the database named
ppcuserwith the same name as the Login user name, as shown in Figure 9.
Figure 9. Create schema with same name as Login user
- Right-click ppcuser under Security >
Logins and choose Properties. Click
User Mapping in the "Login Properties" window as
shown in Figure 10. Change the default schema from
dbo to ppcuser.
Figure 10. Change default schema of BPMDB
- Grant the SqlJDBCXAUser role to
ppcuser in the same Login Properties window as in
Figure 10. Select the checkbox for master, then
select the checkbox for SqlJDBCXAUser in the Database
role membership window, as shown in Figure 11.
Figure 11. Grant the SqlJDBCXAUser role for the Login User
- Repeat steps 2-8 to create the user pdwuser and the database PDWDB for
the Performance Data Warehouse settings.
Tip: You can simply replace ppcuser with pdwuser and PBMDB with PDWDB for steps 2 to 8.
Setting up the environment with a typical installation
Once the databases preparation is finished, you can install the BPM products with a typical installation. The difference is shown in the screen shots, depending on the databases you selected.
Setting up with the embedded DB2 Express is the simplest way to install BPM. It only takes six panels to make the running environment work.
Installing with embedded DB2 Express
- Start the installer with the Launchpad.
- The Welcome panel is displayed. Click Install using typical
installer, as shown in Figure 12.
Figure 12. IBM Business Process Manager Installer Welcome panel
- On the "Typical installation" panel, select Install Process
Center, as shown in Figure 13, and click
Figure 13. IBM BPM Typical installation panel
- On the "Install Process Center" panel, enter the hostname, choose an
installation location as shown in Figure 14, and click
Figure 14. Install Process Center panel
- On the "Select database configuration panel", choose Install
an embedded DB2 Express database, as shown in Figure 15,
and click Next.
Note: This panel does not display if the host machine has DB2 or DB2 Express installed already.
Figure 15. Select database configuration panel
- On the "Installation Summary" panel, select I have read and
accepted the license agreement and notices and click the
Install Software button, as shown in Figure 16.
Figure 16. Installation Summary panel
- On the "Installation information" panel shown in Figure 17, wait until
the installation completes successfully.
Figure 17. Installation information panel
Installing with existing databases
The installation steps are nearly the same as installing with the embedded DB2 Express, except for the selection in Step 5 and a new configuration for DB2 connection after that.
- Start the installer with the Launchpad.
- On the "Welcome" panel, click Install using typical installer.
- The "typical installation" panel is displayed. Select Install Process Center and click Next.
- On the "Install Process Center" panel, enter the hostname and choose an installation Location and click Next.
- On the "Database configuration panel", choose Use an existing
database (DB2, MSSQL, or Oracle), as shown in Figure 18,
and click Next.
Note: This panel does not display if the host machine has DB2 or DB2 Express installed already.
Figure 18. Select database configuration panel
- On the "Set up the existing database server" panel, enter one of the
following, depending on the database type you used:
- For DB2: Enter the hostname, username, and
password. Enter the port, Process Center database name,
Performance Data Warehouse database name, as shown in Figure
19, with the information that was created in Step 1 and click
Figure 19. Set up the existing database server panel for DB2
- For Oracle: Enter the hostname, Process
Center database system identifier field, check the port, enter
the username and password for the Process Server database and
Performance Data Warehouse database as
WBPPC00 and WBPDW00, as
shown in Figure 20. These were created in Step 1. Click
Figure 20. Set up the existing database server panel for Oracle
- For SQL Server: Select the "Type" as
MSSQL, enter the hostname, check the
port field, set the "Process Center
database name" to BPMDB, the "Performance
Data Warehouse database" to PDWDB. Enter the
username for the Process Server database as
ppcuser and Performance Data as
pdwuser, as shown in Figure 21.
Figure 21. Set up the existing database server panel for SQL Server
- For DB2: Enter the hostname, username, and password. Enter the port, Process Center database name, Performance Data Warehouse database name, as shown in Figure 19, with the information that was created in Step 1 and click Next.
- The "Installation Summary" panel is displayed. Check I have read and accepted the license agreement and notices and click the Install Software button.
- On the "Installation information" panel, wait until the installation completes successfully.
If you encountered errors during the typical installation, here are some tips to help you resolve them:
- Log locations for a typical install: The log files
for a typical install are placed into a randomly generated log folder
tempdirectory prefixed with "IBM_LaunchPad_Typical_Install". On the Unix platform, including Linux or AIX, it is the
/tmpfolder. On the Windows, you can get the temp folder address by opening a new command window and issuing the command
echo %TEMP%. In the following example, the temp folder is
C:\TEMP\1and the typical installer logs reside in
C:\Documents and Settings\Administrator>echo %TEMP% C:\Temp\1
The typical_install.log file contains necessary information for issue analysis and problem determination. Listing 3 shows an example of where it met an error during profile creation, which is the last step during the installation. This clearly indicates to open the profile creation log for further details and the root cause.
Listing 3. Typical install log example
1302575182965 I: Running install step 4 of 4 1302575182975 I: Running profile creation 1302575191046 E: Found INSTCONFFAILED error message in the manageprofile logs. 1302575191049 E: Installation failed on step 4 1302575191099 E: Installation failed with message Read the log file at /opt/WLE1502/logs/manageprofiles/ProcCtr01_create.log for further information. 1302575191100 E: Installation failed with message Read the log file at /tmp/IBM_LaunchPad_Typical_Install_1302574621273/manageprofiles.sysout for further information. 1302575191101 E: Installation failed with message Read the log file at /tmp/IBM_LaunchPad_Typical_Install_1302574621273/manageprofiles.syserr for further information.
- Profile creation issues: Most of the installation
failures happen at the last step of installation – profile creation.
You can get such information at the typical install log mentioned
above. The profile creation log needs to be opened for further
For the example, in the above section, you need to open the profile create log
/opt/WLE1502/logs/manageprofiles/ProcCtr01_create.logfor further information. Open it and search for the first error or exception, where you will find the root cause. The failure may be caused by the environment, or most likely caused by the database-related configuration.
If the failure is caused by a database-related configuration, you need to double-check the database configuration before creating the new profile. The following points need to be checked:
- For DB2: Make sure for all the databases the page size is 32 KB and the database encoding is UTF-8. Make sure the specified database user has DB2ADM for these databases.
- For Oracle: Make sure the Oracle instance is running. For the specified user, make sure it has DBA authority.
- For SQL Server: Make sure the collations for all databases are correct. BPMDB and PDWDB require case-insensitive collation and CMNDB requires case-sensitive collation. For each database, the related schema, which has the same name as the Login user, should be the default schema. Make sure the login user is the schema owner as well.
In case you failed at the profile creation phase, you do not need to install Business Process Manageragain. What you need to do is find the root cause for the profile creation failure, launch the Profile Management Tool (PMT), or use the manageprofiles command to create a new profile.
- Ulimit issues on UNIX platform: To install IBM BPM
products successfully on the Unix platform, such as Linux or
AIX®, the ulimit value is 8799 or higher.
If you receive the following warning message during the prerequisite checking, it means that you need to increase the ulimit number.
Current system has detected a lower level of ulimit than the recommended value of 8799. Please increase the ulimit number to minimum value of 8799 and re-start the installation.
You need to shutdown the installer first before fixing the problem. If you are a root user, open a command prompt and issue
ulimit -n 8799,and then restart the installer. If you are a non-root user, work with your system administrator to increase your
ulimit -n 8799, and then restart the installer.
Verifying the Process Center environment
Once the installation is success, verify that the Process Center functions
are set correctly. You can simply verify it by accessing all the Web pages
provided by Process Center. These URLs include Process Center, Process
Admin, and portal. Open a new browser and check that the following URLs
can open and you can sign in. The default username and password is
Http://pcserver:port/ProcessCenter Http://pcserver:port/ProcessAdmin Http://pcserver:port/portal
Tip: If your portal page is not shown correctly with the CSS format and only the pure text page is shown, it does not mean your Process Center environment is wrong. The problem is caused by your browser machine because it cannot resolve the Process Center machine to get the CSS format. Adding the Process Center machine in the host file of the browser machine can solve this issue. This tip applies to Process Server as well.
Setting up the Process Server environment
Setting up the Process Server is nearly the same procedure as Process Center. It only has a few more fields. Also, if you plan to install Process Server on the same machine with Process Center, it is not necessary to install the product again. You only need to launch the PMT to create another Process Server profile. Here, we only list different panels and verification steps for the Process Server environment.
Installing Process Server
If Process Server needs to be installed on a new machine, follow the same steps described in the Setting up the Process Center environment section. There is one difference, where the following "Install a Process Server" panel, as shown in Figure, replaces the previous "Install a Process Center" panel.
Figure 22. Install Process Server panel
You may notice there are two more categories than Process Center, one is the environment type and name, the other is the Process Center connection information. You need to provide the Process Center hostname and port, which are created during the Process Center setup. If you want to use the server offline, click the Use this server offline checkbox. When the offline server needs to be brought back online, follow the Bringing process servers back online guide to make it active.
Verifying the Process Server environment
You need to make sure all the Web pages provided by Process Server are
shown correctly as well. These URLs include ProcessAdmin and portal. Open
a new browser and check that the following URLs can open and you can sign
in. The default username and password is
Also, if Process Server is configured to connect to Process Center, you can
verify it by accessing the Process Center GUI page,
http://pcserver:port/ProcessCenter. Click the
Servers tab and you see that the status is connected,
as shown in Figure 23.
Figure 23. Process Server status
Setting up the Process Designer environment
Setting up Process Designer is simple after Process Center is available. It only requires downloading the package from Process Center and one click or command to install. Note that you already have a Process Designer tool in the same machine with the Process Center environment if you are using the typical installation approach with the Process Center setup on Windows.
Installing Process Designer
Following are steps to set up Process Designer:
- Open the browser. Enter and navigate to the Process Center URL, for
- On the "Welcome" page, on the bottom right of the "IBM Process
Designer" field, click the Download button, as shown
in Figure 24.
Figure 24. IBM Process Designer download panel
- Select a local folder to save the files. Click Save and the Process Designer download starts. Wait until the download completes.
- The downloaded file is named "IBM Process Designer.zip". Extract it to a folder.
- Go to the extracted folder, double-click
installProcessDesigner_admin.bat if you want to
install Process Designer to the default folder of
C:\IBM\ProcessDesigner\v7.5. Otherwise, open a command window and issue the following command to specify another folder, such as Password" fields. The default is
- Navigate to the install destination folder. Double-click eclipse.exe to start Process Designer. No additional configuration is required.
Verifying the Process Designer environment
Once Process Designer has installed successfully, you can verify it by accessing the basic functions of Process Designer:
- Double-click eclipse.exe to launch Process Designer.
- The IBM Process Designer login page is shown. Enter the "User Name"
and "Password" fields. The default is
admin. Click Login.
- The Process Designer console displays without any problems. In the default Process Apps tab, the default installed applications of "Hiring Sample" and "Process Portal" are shown.
- Click the Create New Process App button in the upper-right area of the window.
- On the "Create New Process App" window, enter
ProcApp1for the Process App Name,
PA1for the Acronym, and leave the description blank. Click Create.
- The creation completes successfully. There is one new entry named
"ProcApp1(PA1)" in the process application list, as shown in Figure
Figure 25. New process application in Process Designer
- Click the Open in Designer button to open it in the Designer tool.
Verifying the system
Once Process Center, Process Server, and Process Designer are set up successfully, you can verify the whole system by running some samples provided by BPM.
Verifying the running sample in Process Designer
Process Center has included a sample named "Hiring Sample". It is an executable running with Process Designer. Follow the instructions in Hiring Sample Tutorial for IBM Process Designer to open the sample and play back the process. You can also use it to verify the whole runtime environment. Make sure you have given users access to the Hiring Sample process application because it is required for the tutorial.
In this article, you learned how to set up a typical Business Process Manager environment for first time users. You also learned how to install the runtime servers, including Process Center and Process Server. The article also covered setting up specific database requirements for DB2, Oracle, or SQL Server. With this information, you can easily set up the typical Business Process Managerenvironment for first time users, solve issues during the setup, and verify your environment.
- IBM Business Process Manager V7.5 Information Center
- IBM Integration Designer V7.5 Information Center
- IBM Business Process Management Reference Information
- IBM Business Process Management zone on developerWorks
- IBM Business Process Management Journal
Dig deeper into WebSphere on developerWorks
Get samples, articles, product docs, and community resources to help build, deploy, and manage your cloud apps.
Experiment with new directions in software development.
Software development in the cloud. Register today to create a project.
Evaluate IBM software and solutions, and transform challenges into opportunities.