setting up a clustered topology for ibm business part1

Setting up a clustered topology for IBM BusinessProcess Manager V7.5, Part 1: A step-by-stepguide for BPM StandardSkill Level: Introductory

Michele Chilanti ([email protected])Consulting IT SpecialistIBM

Mangalaganesh Balasubramanian ([email protected])IT ArchitectIBM

07 Sep 2011

This article provides steps to set up a typical IBM® Business Process ManagerStandard V7.5 clustered environment. The article focuses on the recommendedtopology for production deployments – known as the “remote messaging andsupport” topology.

Introduction

This article describes how to create the recommended production topology for IBMBusiness Process Manager (IBM BPM) V7.5 Standard. This topology is known asthe "Remote Messaging and Remote Support" (RMRS) topology. The article focusesexclusively on setting up an environment for IBM BPM V7.5, and does not considerthe case where IBM Business Monitor is installed on top of the IBM BPM product. Inthat case, the steps for configuring the recommended topology results in anadditional cluster being created for the purpose of supporting certain webapplications, such as Business Space. A four-cluster topology is also known as a"Remote Messaging, Support, and Web" topology.

Figure 1 shows the topology that we are going to describe in the article.

Figure 1. The topology that we intend to create

Setting up a clustered topology for IBM Business Process Manager V7.5, Part 1: A step-by-step guide forBPM Standard

Trademarks

© Copyright IBM Corporation 2011 of 30

mailto:[email protected]

mailto:[email protected]

http://www.ibm.com/developerworks/ibm/trademarks/

http://www.ibm.com/legal/copytrade.shtml

The topology shown in Figure 1 consists of two physical nodes and a DeploymentManager process running in another physical machine.

Across the two nodes, we create three clusters of application servers:

1. One for the messaging infrastructure.

2. One for the process applications – this cluster runs the business processengine that executes the Business Process Model and Notation (BPMN)processes.

3. One for the Performance Data Warehouse monitoring infrastructure andother support applications. This cluster's primary objective is to run theembedded monitoring infrastructure provided by IBM BPM.

Each cluster has a member on each of the two nodes, for a total of six clustermembers.

Note: Figure 1 depicts a cell that comprises three different physical machines. Theprocedure to create a cell with a different number of physical machines is similar to

developerWorks® ibm.com/developerWorks


Trademarks




the approach detailed here. For purposes of simplicity, we use a single physicalmachine to create this topology. The databases are also hosted in this machine. In aproduction environment, you would isolate the databases on a separate set ofphysical boxes.

At a high level, the creation of this topology involves the following steps:

• Create the profiles and federating the nodes.

• Create a deployment environment using the pre-defined pattern ("remotemessaging and support").

• Create the required databases.

• Generate the deployment environment.

• Populate (or "bootstrap") the database with system information.

• Verifying the deployment environment.

Creating the profiles and federate the nodes

This section describes how to create the Deployment Manager and custom profilesnecessary for our topology, and how they need to be federated to the cell.

Note: This article assumes the usage of the 64-bit architecture version of IBM BPM.The database used by BPM to store its configuration and runtime information isDB2® UDB. The steps outlined in this article work well for both the 32-bit and 64-bitversion of the product. It also assumes the following authentication credentials:

• The DB2 administrator user and password (bpmadmin/xxxxxx in thetext).

• The Business Process Manager Administrator user and password(bpmadmin/bpmadmin in the text).

The article also assumes that the product binaries for IBM BPM Standard havealready been installed, along with the appropriate version of DB2, and that noexisting profiles have been created yet.

Creating the Deployment Manager profile

Let's start with the creation of the Deployment Manager profile.

Note: Unlike 32-bit versions of the IBM BPM product, the 64-bit versions do notprovide the Profile Management Tool (PMT), which is a graphical interface for profilecreation and management. You need to use the manageProfiles command line utility

ibm.com/developerWorks developerWorks®


Trademarks




when working with the 64-bit version of the product.

1. Open a command prompt and change directories to<BPM_INSTALL>\bin.

2. Copy the file PCDmgrProfileCreation.template from the Appendix to acustom directory, such as c:\BPM\responseFiles.

3. Open the file PCDmgrProfileCreation.template in a text editor andchange the values of the following attributes:

• templatePath=D:/IBM/WebSphere/Standard/AppServer/profileTemplates/BPM/dmgr.procctr

• profilePath=D:/IBM/WebSphere/Standard/AppServer/profiles/PCStdDmgr01

• hostName=MyBPMServer

The host name needs to be a resolvable value. The paths used here are not thedefault directories. You should choose the paths that are applicable to your machineor setup.

1. In the command prompt window, type the following command, and thenpress Enter:

manageprofiles -response C:\BPM\responseFiles\PCDmgrProfileCreation.template

2. The Profile creation takes a few minutes. Once the profile creation iscompleted, the following text appears on the command prompt window:

INSTCONFSUCCESS: Success: Profile PCStdDmgr01 now exists. Please consultD:\IBM\WebSphere\Standard\AppServer\profiles\PCStdDmgr01\logs\AboutThisProfile.txtfor more information about this profile.

Creating the first custom profile

1. Open a command prompt and change directories to<BPM_INSTALL>\bin.

2. Copy the contents of PCCustom01Profile.template from the Appendix toa custom directory, such as c:\BPM\responseFiles.

3. Open the file PCCustom01Profile.template in a text editor and changethe values of the following attributes:



Trademarks




• templatePath=D:/IBM/WebSphere/Standard/AppServer/profileTemplates/BPM/managed.procctr

• profilePath=D:/IBM/WebSphere/Standard/AppServer/profiles/PCStdCustom01

• hostName=MyBPMServer

4. In the command prompt window, type the following command, and thenpress Enter:

manageprofiles -response C:\BPM\responseFiles\PCCustom01ProfileCreation.template

5. The Profile creation takes a few minutes. Once the profile creation iscompleted, the following text appears on the command prompt window:

INSTCONFSUCCESS: Success: Profile PCStdCustom01 now exists. Please consultD:\IBM\WebSphere\Standard\AppServer\profiles\PCStdCustom01\logs\AboutThisProfile.txtfor more information about this profile.

Creating the second custom profile

1. Perform the same steps as the creation of the first custom profile. UsePCCustom02Profile.template instead ofPCCustom01Profile.template that you used in the creation of thefirst custom profile.

2. Once the profile creation is completed, the following similar text appearson the command prompt window:

INSTCONFSUCCESS: Success: Profile PCStdCustom02 now exists. Please consultD:\IBM\WebSphere\Standard\AppServer\profiles\PCStdCustom02\logs\AboutThisProfile.txtfor more information about this profile.

You now have three profiles:

• PCStdDmgr01

• PCStdCustom01

• PCStdCustom02

3. You can verify this by using the listProfiles command. In the commandprompt window, type manageProfiles –listProfiles and pressEnter.The command window displays the following results:



Trademarks




[PCStdDmgr01, PCStdCustom01, PCStdCustom02]

The profiles are currently disjointed from each other. You need to federate thePCStdCustom01 and PCStdCustom02 profiles to PCStdDmgr01 so that all of thembelong to a single cell: pcstdcell01. This is the cell where you create the RemoteMessaging and Remote Support topology.

Federating the nodes to the Deployment Manager to form a cell

1. Start the Deployment Manager process. On a command prompt, changethe current directory to <BPM_INSTALL>\profiles\PCStdDmgr01\binand issue this command: startManager.

2. Once the Deployment Manager starts up, change the current directory to<BPM_INSTALL>\profiles\PCStdCustom01\bin and federate this nodeto the cell by issuing this:

addNode localhost 8879 -conntype SOAP -username bpmadmin -password bpmadmin

Note: By default, the Deployment Manager runs on port 8879 for SOAPconnections. If this port was unused in the machine during the creation ofDeployment Manager, this is the port that is used by the DeploymentManager. The userid/password of bpmadmin/bpmadmin was usedduring the creation of the Deployment Manager. If the port number andcredentials are different in your setup, then you need to specify theappropriate values here.

3. The process is complete with a successful completion message, similar tothe following:

ADMU0003I: Node PCStdCustomNode01 has been successfully federated.

4. Repeat the federation for the PCCustom02 profile by changing directoriesto <BPM_INSTALL>\profiles\PCStdCustom02\bin and issuing again:

addNode localhost 8879 -conntype SOAP -username bpmadmin -password bpmadmin

Similar to the federation of PCStdCustomNode01, this command shouldalso complete successfully.

You have federated the two custom profiles to the cell and are ready to create the



Trademarks




deployment environment to represent a clustered topology.

Creating a deployment environment

In this section, you are going to create the deployment environment thatcorresponds to the clustered topology that you want to set up. Keep in mind that theDeployment Environment object is just a description of the topology. When youcreate one, you do not implicitly create all the resources that are necessary tophysically implement the topology.

The generation of those resources is a separate step, which we are going toillustrate in Generating the deployment environment.

To create a new deployment environment by using the console:

1. Open a web browser and direct it to the administrative console. If youfollowed the steps to the letter, the URL ishttp://localhost:9060/admin.

2. Log in using the credentials bpmadmin/bpmadmin to administer via theconsole.

3. Expand Servers and click Deployment Environments.

4. On the Deployment Environments panel, click New.

5. Leave the radio button Create a new deployment environmentselected, and type MyTopology for the Deployment environment namefield. Make sure that Detailed: Show all steps is also selected, as shownin Figure 2.Figure 2. Creating a new deployment environment (initial screen)



Trademarks




6. Select the BPMSC feature for the deployment environment as shown inFigure 3 and click Next.Figure 3. Selecting the BPMSC Feature for the deploymentenvironment

7. Select Remote Messaging and Remote Support as shown in Figure 4.Figure 4. Selecting the "Remote Messaging and Remote Support"topology



Trademarks




8. Click Next. You are presented with a series of steps. The first step isabout adding the nodes to the topology that you want to create. You havetwo separate nodes in the cell. Let's add them both to the deploymentenvironment by checking their checkboxes, as shown in Figure 5.Figure 5. Adding the nodes to the topology

9. Click Next. The second step is about defining the distribution of themembers of the three clusters you want to create. This screen allows youto specify how many cluster members of a certain type you want to createon each node. Our target topology has three clusters:

• Application Deployment Target cluster: This is where your BPMNprocess definitions will be executed when you playback processesfrom the Process Designer, or run them from the Process Portal. Thiscluster also hosts other applications, such as Process Portal and the



Trademarks




Process Admin console.

• Messaging Infrastructure cluster: This cluster hosts the messagingengines for the two Service Integration (SI) Buses required by BPMStandard.

• Support Infrastructure cluster: This is where the out-of-the-boxmonitoring components process the tracking events produced by theBPMN processes. This component also interacts with thePerformance Data Warehouse database.

Since you only have two nodes, you will assign a member of each clusterto each node to ensure failover. Each node will run three clustermembers, as shown in Figure 6.

Figure 6. Defining the location of the three clusters

10. Click Next. This leads you to the section where the names of clustermembers are specified. The cluster members are predefined using thefollowing naming convention:

<TopologyName>.<ClusterType>.<NodeName>.<running number>

Note: Though the wizard generates default names based on this namingconvention, you can change these values to adhere to the namingconventions that are adopted in your organization. In our scenario, weused the default names for all the cluster members.

11. The first step in naming the clusters involves specifying the names ofApplication Deployment Target cluster as shown in Figure 7.Figure 7. Cluster Naming for the Application Deployment Target



Trademarks




12. The second step in naming the clusters involves specifying the names ofthe Messaging Infrastructure cluster as shown in Figure 8.Figure 8. Cluster Naming for the Messaging Infrastructure

13. The third step in naming the clusters involves specifying the names of theMessaging Infrastructure cluster as shown in Figure 9.Figure 9. Cluster Naming for the Supporting Infrastructure



Trademarks




14. The next set of steps involves the database settings. It is important tohave a clear idea of how many databases you are going to need, whichschemas go into the various databases, and which credentials to use forthe authentication to those databases. Table 1 provides brief informationabout the databases and the role they play in this topology.

Table 1. Databases and brief descriptionDatabase name Description

BPMDB (Business Process Database) This database contains the process definitionmodels and stores the state and tasks of eachprocess instance.

PDWDB (Process Data Warehouse Database) This database stores the historical informationthat helps create dashboards and reports.

MEDB (Messaging Engine Database) This database is used by the messaginginfrastructure to make messages persistent forassured delivery and recovery.

15. There are a couple of ways to specify the database settings. Click Nexton the import database configuration step.Note: In our scenario, we are not using the Database Design Tool (DDT).A future article will discuss the topologies for BPM Advanced and provideinformation on using the DDT.

16. Our database configuration includes the following databases:

a. Process Server (MYBPMDB).

b. Performance Warehouse Database (MYPDWD)



Trademarks




c. Messaging Engine DB (MYMEDB). You want a single database forboth messaging engines (a common configuration). Eachmessaging engine has its schema in the database:

i. The MEDPE00 schema for the Performance DataWarehouse messaging engine.

ii. The MEDPS00 schema for the Process Server messagingengine.

Note: In our scenario, we have used the prefix "MY" for the databasenames. You can choose a name that is appropriate for your environment.You can work with your database administrators to ensure that you set upthe databases that are appropriate for your environment. For example,you might want to have multiple database instances instead of theapproach adopted here, where all the three databases are hosted in asingle DB2 instance.

To reflect the settings discussed above, we have made the followingchanges to the database and schemas parameters, as shown in Figure10.

Figure 10. Defining the databases and schemas

Ensure that the credentials specified for authentication match the set upof DB2. Finally, make sure that the Create Tables checkbox is checkedfor all three databases.

17. Click Next. Review the summary and if everything is as expected, clickFinish.Note: Do not click Finish and Generate Environment at this time. You



Trademarks




need to complete some database configuration before you can generatethe environment.

Figure 11. Summary page for the deployment environment

18. Save your work.

To review what you have created so far:

1. The console now shows MyTopology in the list of deploymentenvironments. If you hover with your mouse over the Status icon, you seethat the status is now "Not configured" see Figure 12). This means thatthe deployment environment exists, but the actual resources have notbeen generated yet.Figure 12. The deployment environment is not yet configured



Trademarks




2. Click MyTopology. The screen shows you a summary of the deploymentenvironment. In particular, it shows the status of each of the clusters thatbelong to it. Since you have not generated any resources yet, the statuswill be Not configured for every element. Notice at the bottom of Figure13, there is the Generate Environment button that allows you togenerate the resources.Figure 13. Details of the deployment environment prior to generatingthe resources

3. Click Data source. The database configuration screen appears again,showing not only the database names and schema names you havedefined in the previous step, but also the JNDI name for a number of datasources. At this point, you can still make changes and save thosechanges in the deployment environment. Any change that you make nowwill be reflected on the actual resources.



Trademarks




4. Click Cancel.

Completing the database configuration

For the deployment environment generation to succeed, you need to make sure thatthe database instances exist. The databases are not created by the GenerateEnvironment command. The Generate Environment command creates the requiredtables as you have "Checked" the create tables as part of the deploymentenvironment setup.

Here, you are going to create the instances of all the necessary databases and relyas much as possible on the automatic creation of tables. For production machines,we recommend to choose the appropriate database elements like tablespaces andso on. Work with your database administrators to ensure that suitable values arechosen for the database configuration.

1. Create the MYPDWDB database for the Performance Data Warehouse:

a. Open a command prompt and issue the following command:db2cmd.

b. On the resulting command prompt, issue:

db2 CREATE DATABASE MYPDWDB AUTOMATIC STORAGE YES ON 'C:\' DBPATH ON 'C:\'USING CODESET IBM-1252 TERRITORY US COLLATE USING SYSTEM PAGESIZE 32768 WITH'Standard Perf Data WarehouseDB'

2. Create the MYBPMDB database for Process Server:

a. On the database command prompt, issue:

db2 CREATE DATABASE MYBPMDB AUTOMATIC STORAGE YES ON 'C:\' DBPATH ON 'C:\'USING CODESET IBM-1252 TERRITORY US COLLATE USING SYSTEM PAGESIZE 32768 WITH'Standard BPMDB'

3. Create the MYMEDB database:

a. On the same command prompt as above, issue:

db2 CREATE DATABASE MYMEDB AUTOMATIC STORAGE YES ON 'C:\' DBPATH ON 'C:\'USING CODESET IBM-1252 TERRITORY US COLLATE USING SYSTEM PAGESIZE 32768 WITH'ME DB'



Trademarks




Note: In our scenario, the scripts above were used to create the databases. You canexplore the usage of the Database Design Tool (DDT) or the database scripts thatare bundled along with the product, which are available at this location,<BPM_INSTALL_DIR>/dbscripts/.

The database scripts are grouped under these two categories:

• PerformanceDW

• ProcessServer

The database scripts are available for all the supported databases: DB2, Oracle®,and SQL Server. Figure 14 shows the list of database scripts that are available forDB2 to work with the Process Server database.

Figure 14. DB2 database scripts for Process Server

Generating the deployment environment

Now that you have the databases created, let's go back to the console and generatethe deployment environment:

1. Go back to the administrative console, expand Servers, and then clickDeployment Environments.

2. Click MyTopology. On the subsequent screen, click GenerateEnvironment.



Trademarks




3. When the generation is complete (it may take a few minutes), save yourwork. A successful generation has the following lines:

CWLDB9051W: Deployment environment MyTopology is successfully generated.The configuration has ended.

4. Notice that the topology is now configured, and the status is Stopped, asindicated in Figure 15.Figure 15. Deployment Environment in the stopped status

5. Click MyTopology. Now, the status of each of the clusters is Stopped, asshown in Figure 16.Figure 16. Stopped clusters in the deployment environment

Notice that you can still click on Deployment Topology and Datasources. However, if you make any changes there, those changes arenot reflected on the actual resources that you have already generated.



Trademarks




6. Let's take a quick look at some of the resources that you have generated.Expand Servers, expand Clusters, and click WebSphere applicationserver clusters. You see the three clusters that you have generated, asshown in Figure 17.Figure 17. The three clusters that are part of the topology

7. Each cluster has two cluster members (one on each node). Click Servers> Server Types > WebSphere application servers. You see the sixservers that were generated, as shown in Figure 18.Figure 18. Cluster members in the topology

8. Make sure the data sources were created. Navigate to Resources >JDBC > Data sources. You see a list of seven data sources as shown inFigure 19.Figure 19. Data sources created as part of the topology generation



Trademarks




9. Check out the SI Buses. Navigate to Service Integration > Buses andmake sure that you see the two buses as shown in Figure 20.Figure 20. SI Buses in the topology

10. Click on one of the buses (for example, PROCSCVR.pcstdcell01.bus).Navigate to Messaging Engines, and then click the messaging engine.

11. Click Message Store. You see the schema name that you defined for it(MEDPS00), the JNDI name of the data source that was generated, andthe Create tables checkbox should be checked (Figure 21).



Trademarks




Figure 21. Data store settings for the SI Buses in the topology

12. Finally, let's review the applications that were installed. Navigate toApplications > Application Types > WebSphere enterpriseapplications. You see the following applications shown in Figure 22.Notice that their name shows an indication of where they have beeninstalled.Figure 22. Enterprise applications installed as part of the topology

Bootstrapping the database with system data

The deployment environment is created, but it still does not have the required data inthe various databases. The databases need to be populated with the required data



Trademarks




manually by executing the bootstrapProcessServerData script before the serversin the topology are started.

This bootstrap process performs three key activities:

• Imports the system data: The system toolkit that contains the predefineddata definitions are added to the database to be used by the variousprocess applications.

• Imports the resource bundle groups: The process portal application,which end users would use, supports multiple languages (depending onwhat is chosen during the installation process). The resource bundlesrepresenting the various locales are imported to the database.

• Imports the samples: A sample application, "Hiring Application", isavailable and you can use this to test the deployment environment.

Perform the bootstrap process by issuing the following commands:

1. Open a command prompt and change to the bin directory of thedeployment manager:<BPM_INSTALL_DIR>\profiles\PCStdDmgr01\bin.

2. On the resulting command prompt, issue:

bootstrapProcessServerData -profilePath <BPM_INSTALL_DIR>/profiles/PCStdDmgr01-dbType DB2_UNIVERSAL -dbJDBCClasspath <BPM_INSTALL_DIR>//jdbcdrivers/DB2-nodeName PCStdCustomNode01 -serverName MyTopology.AppTarget.PCStdCustomNode01.0

3. Replace <BPM_INSTALL_DIR> with the directory of the BPM installationdirectory, such as D:/IBM/WebSphere/Standard/AppServer.

Verifying the deployment environment

Now you are ready to start the deployment environment and test some of thefunctions. Keep in mind that the node agent processes must be up and running forthis step to be successful.

Note: This step may be difficult to carry out on a single system because of memoryconstraints. Keep in mind that you have the Deployment Manager, two Node Agents,and six application servers running on the same box. We mention these steps forillustration purposes. We recommend that you read through Step 1, and then skip toStep 2 for an alternate way to test the topology.

Step 1: Start all the servers that are part of the deployment environment



Trademarks




1. Navigate to Servers > Deployment Environments. Check the checkboxclose to MyTopology and click Start.

2. Very quickly, the status of the Deployment Environment changes toPartial Start, as shown in Figure 23.Figure 23. Deployment environment in Partial Started status

3. Click MyTopology. You also see that the status of the individual clustersis Partial Start, as shown in Figure 24.Figure 24. The cluster members in Partial Start status

4. Wait a couple of minutes, and then refresh the status of the clusters. Waituntil all three clusters are up and running.

Step 2: Start all servers on a single node of the deployment environment

Here is another way to test the topology considering the memory constraints.



Trademarks




1. Navigate to Servers > Server Types > WebSphere application servers.All the servers are stopped now.

2. Select all the servers that are configured to run on Node 1. The easiestway is to sort the nodes based on their names, select all the servers inPCStdCustomNode01, and click Start as shown in Figure 25.Figure 25. Starting only some members to cope with memoryconstraints

3. Wait a couple of minutes, and then refresh the status of the clusters. Waituntil all three servers are up and running.

4. Let's now make sure that the topology is functional. First, ensure that thetables for the Messaging Engines have been created:

5. In a command prompt window, type the following command: db2cmd.

6. In the resulting command prompt window, issue the following commands:

db2 connect to MYMEDB user bpmadmin using xxxxxxxdb2 list tables for schema MEDPE00> medpe00tables.txt

7. View the file medp00tables.txt using a text editor. There are nine tableslike the ones shown in Table 2 below. There are another nine tables withthe same names under the schema MEDPS00 in this database.

Table 2. List of tables for schema MEDPE00



Trademarks




Table/View Schema Type

SIB000 MEDPE00 T

SIB001 MEDPE00 T

SIB002 MEDPE00 T

SIBCLASSMAP MEDPE00 T

SIBKEYS MEDPE00 T

SIBLISTING MEDPE00 T

SIBOWNER MEDPE00 T

SIBOWNERO MEDPE00 T

SIBXACTS MEDPE00 T

8. Verify that the messaging engines are up and running. In theadministrative console, navigate to Service Integration > Buses. Clickon one of the SI Buses (for example,MyTopology.Messaging.000-PROCSVR.pcstdcell01.Bus).

9. Click Messaging Engines. The status is now active, as shown in Figure26.Figure 26. Messaging Engine in Started state

10. Let's check the tables for the BPM database. In a command promptwindow, type the following command: db2cmd.

11. In the resulting command prompt window, issue the following commands:

db2 connect to MYBPMDB user bpmadmin using xxxxxxxdb2 list tables for schema BPMADMIN > bpmtables.txt

12. View the file bpmtables.txt using a text editor. There are 185 tablesunder the schema bpmadmin as shown in a partial list in Figure 27.Figure 27. Partial list of tables from the MYBPMDB table



Trademarks




Note: The tables are created under the identity of bpmadmin, which wasspecified as username during the deployment environment setup process.

13. Let's now try out the Process Center web application. This application(IBM BPM Repository) runs on the Application Target cluster. Open a webbrowser and direct it to the URL:http://localhost:9080/ProcessCenter/. You may need to findout what port your Application Target cluster uses for inbound HTTPtraffic. Generally, if you kept all the defaults, the Application Target serveron Node 1 uses port 9080. Close the Welcome window and you now seetwo process applications as shown in Figure 28.Figure 28. Process Center Console web application

14. You cannot start the Hiring Sample from the process portal as thisprocess is not "exposed for start" via the Process Portal. You will run thissample application using Process Designer. If you do not have ProcessDesigner installed on your machine, you can install it by clicking on theDownload Process Designer link in the Process Center web application,



Trademarks




as shown in Figure 29.Figure 29. Download Process Designer

15. After installing Process Designer or changing the configuration of ProcessDesigner to point to this clustered process center, launch ProcessDesigner.

16. Click on Open in Designer in the Hiring Sample (HSS) row as shown inFigure 30. This opens the Hiring Sample application.Figure 30. Open Hiring Sample in Process Designer

17. Click on Processes and double-click on HR Open New Position. Clickon the Run Process button to start an instance of this Business ProcessDiagram (BPD) as shown in Figure 31.Figure 31. Run Hiring Sample in Process Designer

18. The BPD process is now in a running state. Let's use the Process Portalweb application to perform additional steps with this BPD. Like theProcess Center console application, this application runs on the



Trademarks




Application Target cluster.

19. Open a web browser and direct it to this URL:http://localhost:9080/portal. Replace 9080 with the port that isappropriate for your environment.

20. The Process Portal applications appear as shown in Figure 32.Figure 32. Process Portal web application

An instance of "Employee Requisition for ..." is displayed as shown inFigure 32. Click on Run to execute the task "Submit requisition".

Figure 33. Create Job Requisition step

Appendix: Response files for profile creation

The response files that are required to create the three profiles are provided in thissection:

• Dmgr

• CustomProfile01

• CustomProfile02

You should change some of these values to ensure that they are appropriate foryour environment.

Contents of the PCDmgrProfileCreation.template response file:



Trademarks




createtemplatePath=D:/IBM/WebSphere/Standard/AppServer/profileTemplates/BPM/dmgr.procctrprofilePath=D:/IBM/WebSphere/Standard/AppServer/profiles/PCStdDmgr01profileName=PCStdDmgr01cellName=pcstdcell01nodeName=pcstdDmgrNodeserverType=DEPLOYMENT_MANAGERenableAdminSecurity=trueadminUserName=bpmadminadminPassword=bpmadminhostName=MyBPMServerenableService=false

Contents of the PCCustomProfile01Creation.template response file:

createtemplatePath=D:/IBM/WebSphere/Standard/AppServer/profileTemplates/BPM/managed.procctrprofilePath=D:/IBM/WebSphere/Standard/AppServer/profiles/PCStdCustom01profileName=PCStdCustom01cellName=PCCustomcell01nodeName=PCStdCustomNode01hostName=MyBPMServerdbType=DB2_UNIVERSALdbJDBCClasspath=D:/IBM/WebSphere/Standard/AppServer/jdbcdrivers/DB2

Contents of the PCCustomProfile02Creation.template response file:

createtemplatePath=D:/IBM/WebSphere/Standard/AppServer/profileTemplates/BPM/managed.procctrprofilePath=D:/IBM/WebSphere/Standard/AppServer/profiles/PCStdCustom02profileName=PCStdCustom02cellName=PCCustomcell02nodeName=PCStdCustomNode02hostName=MyBPMServerdbType=DB2_UNIVERSALdbJDBCClasspath=D:/IBM/WebSphere/Standard/AppServer/jdbcdrivers/DB2

Conclusion

This article described the process of setting up a simple clustered topology thatreflects the recommended configuration for production environments in IBM BPMV7.5. While this article provided a simple example of such a setup, you can nowextrapolate the steps that are necessary to create more complex or slightly differenttopological scheme, and adapt the steps to a number of different circumstances.



Trademarks




Resources

• IBM Business Process Manager V7.5 Information Center

• Article: IBM Business Process Manager V7.5 development topologyrecommendations

• Whitepaper: IBM Business Process Manager Advanced V7.5: Configuring aclustered Process Server

• IBM Business Process Management family page

• developerWorks Business Process Management zone

About the authors

Michele ChilantiMichele Chilanti is a Client Technical Professional with the World WideBusiness Process Management Technical Sales organization at IBM.He has over 20 years of experience working with a variety of productsand software technologies, especially in the areas of business processmodeling, implementation, and deployment of Business ProcessManagement and services-oriented solutions. Michele presentsregularly at technical conferences worldwide, and has authored orco-authored a number of technical publications.

Mangalaganesh BalasubramanianMangalaganesh Balasubramanian is an IT Architect with IBMSoftware Services for WebSphere. Manglu has been consulting withcompanies in the Asia Pacific region for more than 14 years. Hespecializes in the Business Process Management space, particularlywith solutions based on WebSphere Process Server and WebSphereLombardi Edition.



Trademarks


http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/index.jsp

http://www.ibm.com/developerworks/websphere/bpmjournal/1106_pacholski/1106_pacholski.html?ca=drs-

http://www.ibm.com/developerworks/websphere/bpmjournal/1106_pacholski/1106_pacholski.html?ca=drs-

http://www-01.ibm.com/support/docview.wss?uid=swg27022332

http://www-01.ibm.com/support/docview.wss?uid=swg27022332

http://www-01.ibm.com/software/info/bpm/index.html

http://www.ibm.com/developerworks/websphere/zones/bpm/

http://www.ibm.com/developerworks/websphere/services/

http://www.ibm.com/developerworks/websphere/services/



setting up a clustered topology for ibm business part1

Documents