top of page

Setting Up Cross Cell Communication Between IBM Business Monitor and IBM Business Process Manager

The following describes how to configure cross cell communication between IBM Business Monitor and IBM Business Process Manager when the products are installed into separate cells.

Before running through these steps, you should already have a successful installation completed of both Business Process Manager and Business Monitor. All cluster members should be able to start successfully in each of the cells before continuing with these steps. Some areas of pictures are blocked out for privacy reasons.

Cross SSL Setup

Follow steps outlined here to enable SSL between Monitor and BPM cells. These steps will need to be completed on both the Monitor cell and the BPM cell.

On the Monitor cell, provide the BPM server and secure port of the BPM.AppTarget. On the BPM cell, provide the Monitor server and the secure port of the Monitor.AppTarget. Click Retrieve Signer Information and then click OK. Repeat this for any DNS names as well.

Ensure that the Override inherited values box is not checked for all nodes.

Enabling Identity Assertion

Follow the steps outlined here for both cells:

Ensure Use identity assertion is selected and the Trusted identities are set to *.

Ensure Use identity assertion is selected and Use server trusted identity is selected.

Sharing LTPA keys between cells

Follow the steps outlined here for both cells:

Provide a password (can be anything you want) and export the keys from both cells.

Provide the keys you exported from the BPM cell to the Monitor cell and Import. Likewise, provide the Monitor keys to the BPM cell and Import.

Restart both Monitor and BPM cells.

Configure Table-Based Event Delivery

To configure the BPM cell to use table-based delivery, follow the steps outlined here:


You will need to first create an Authentication Alias called MONITOR and set the user name and password to the DB username and password for the Monitor database.

After the Auth Alias is created, you can edit the /ems_source/scripts/monitor/ script for your Monitor environment. You will then run the following command on the BPM cell to configure the table-based events: -lang jython -f “/ems_source/scripts/monitor/”

To verify, check under your JDBC datasources and look for MONITOR_Cellname_Routing_Database datasource

Configure Queue-Based Event Delivery (for Lombardi)

On the Monitor cell, you will need to perform the outlined steps here:


On the Monitor server, edit the properties file found in D:\IBM\WebSphere70\01\AppServer\scripts.wbm\crossCell\configureRemoteMonitorBus.props for the given environment you are working with.

Then open a command prompt and execute the following command from D:\IBM\WebSphere70\01\AppServer\scripts.wbm\crossCell:

Here you are providing the property file you previously edited.

If asked to trust the ssl store, select yes:

Ensure successful completion:

In BPM cell, create an Authentication Alias called EventEmitterAlias (Any valid user id and password combination should do):

Copy the following files from Business Monitor to BPM installations (preserving the directory structure below WAS_HOME): WAS_HOME/installableApps.wbm/EmitterServices.ear (here you will need to create the installableApps.wbm directory first) WAS_HOME/plugins/ WAS_HOME/plugins/

Restart the entire BPM cell and Monitor cell before continuing.

Run the following commands on the BPM cell:

./ –lang jython (when prompted, provide your username and password that you would log into the WAS console with)

AdminTask.wbmConfigureEventEmitterFactory([“-cluster”, “BPM.Support”])

AdminTask.wbmDeployBPMEmitterService([“-cluster”, “BPM.Support”])

Navigate to Service Integration > Common Event Infrastructure > Event Service > Map security roles to users or groups, change all Roles to use Special Subject of Everyone

Restart the entire BPM cell.

Share this:

  1. Facebook

  2. LinkedIn

  3. Twitter

  4. Email

12 views0 comments
bottom of page