IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Use business monitoring with process applications > Monitoring events

Configure event flow to a remote server

In a server environment where IBM BPM and IBM Business Monitor are installed in the same cell, communication between IBM BPM, which is emitting events, and Business Monitor, which is monitoring the events, is automatically configured during installation of Business Monitor. However, if IBM BPM and Business Monitor are not installed in the same cell, and a remote Business Monitor is monitoring the emitted events, then advanced configuration is required to enable emitted events to flow to the remote Business Monitor server.

Before completing this task configure queue-based event management in a multi-cell environment. Refer to the related link "Configuring queue-based event management in a multiple-cell environment."

The following information applies when you configure event flow to a remote server:

• Perform the steps in this task when IBM BPM is sending events to a remote Business Monitor server.

• The monitor model deployed in an environment that includes IBM BPM and a remote Business Monitor server is a custom monitor model generated in IBM Integration Designer. This monitor model is different from the auto-generated monitor model that is used by Process Designer.

• When you publish a process application to IBM BPM after configuring event flow to a remote server, the process application cannot contain a monitor model.

• The monitor model must be manually deployed using the administrative console on the monitor server.

• You must configure the manually deployed monitor model to use the same CEI event service that the IBM_BPM_EMITTER_SERVICE is using, which is the CEI event service in the Business Monitor cell. See the Configure the CEI event service topic in the related links for more information.

You must configure event flow to a remote server in the following situations:

• You do not want to use the default messaging provider.

  For example, you want use WebSphere MQ as the messaging provider instead.

• You want to use the default messaging provider, but the destination Business Monitor server is in a separate cell from IBM BPM.

  For example, you want to connect to a remote Business Monitor server using an SI bus link.

• You want to use table-based delivery to send events from IBM BPM Advanced to Business Monitor. You make use of the Comment Event Infrastructure (CEI) event service that is already configured within the IBM BPM Advanced cell.

Procedure

Configure the IBM BPM and Business Monitor resources, customizing them as necessary for your environment.

• WebSphere MQ:

  Create a queue in your messaging provider to receive the raw XML events emitted from IBM BPM. You can use WebSphere MQ as the messaging provider, as shown in the diagram and the following steps. In this configuration, IBM BPM and Business Monitor can be in separate cells.

  

  1. Deploy the BPM emitter service in the Business Monitor cell. The BPM emitter service deployment creates SI bus resources for all the JMS artifacts. You must re-configure the resources to point to MQ resources. For more information, refer to the related link "Configuring the JMS event emitter service to use the WebSphere MQ messaging provider."

  2. In the Business Monitor cell, re-configure the JMS queue with a JNDI name of jms/com.ibm.lombardi/JMSEmitterInput to point to an MQ queue.

  3. In the Business Monitor cell, re-configure the JMS queue connection factory with a JNDI name of jms/com.ibm.lombardi/JMSEmitterInputQueueFactory to point to the MQ queue manager.

  4. In the Business Monitor cell, re-configure the JMS activation specification named jms/com.ibm.lombardi/JMSEmitterInputActivationSpec so that it points to the same MQ queue reference as the jms/com.ibm.lombardi/JMSEmitterInput JMS queue. For more information about the JMS activation specification, refer to the related link "Using a JMS activation specification to put the event XML into a WebSphere MQ queue."

  5. In the IBM BPM cell, define a JMS queue with the JNDI name jms/com.ibm.lombardi/EventEmissionQueue. The JMS queue must point to the destination queue, or its corresponding foreign destination.

  6. In the IBM BPM cell, define a JMS queue connection factory with the JNDI name jms/com.ibm.lombardi/EventEmissionQueueFactory. The connection factory must connect to the messaging destination referenced in the previous step.

• Multiple-cell environment with a service integration (SI) bus link: If you are not using WebSphere MQ as the messaging provider, you can configure event flow between cells in a multiple-cell environment using an SI bus link, as shown in the diagram and the following steps. For more information about setting up the SI bus link, refer to the related topic "Configuring queue-based event management in a multiple-cell environment."

  

  1. Deploy the BPM emitter service in the Business Monitor cell. The BPM emitter service deployment creates an SI bus destination named LombardiEventEmitterInputQueue in the monitor SI bus.

  2. Configure server-to-server SSL, as described in Configure server-to-server SSL in multiple-cell environments.
  3. Share LTPA keys, as described in Sharing LTPA keys.
  4. Enable identity assertion, as described in Enabling identity assertion.

  5. Configure the remote MONITOR bus in the IBM BPM cell and the link to the MONITOR bus in the Business Monitor cell by following the procedure in Configure queue-based event delivery in a multiple-cell environment.

  6. The SI bus destination named LombardiEventEmitterInputQueue was created by the BPM emitter service deployment, but create a corresponding foreign destination in the IBM BPM cell.

     1. In the administrative console, click Service integration > Buses > monitor.cellname.bus > Destinations.

     2. Create a new destination, selecting Foreign as the destination type, and specifying LombardiEventEmitterInputQueue for the remote monitor bus.

  7. The destination roles for a foreign destination are different from the local bus roles. Only users that have been assigned the Sender role for the foreign destination can place messages in the foreign destination queue. To assign a user with the Sender role to the foreign destination:

     AdminTask.addUserToDestinationRole('[ -type foreignDestination 
        -role Sender 
        -bus MONITOR. bpmCell.Bus 
        -foreignBus MONITOR. monitorCell.Bus 
        -destination LombardiEventEmitterInputQueue 
        -user  user_id ]') 

     For more information about adding a user to the Sender role of the corresponding foreign bus and destination, refer to the related topic "Completing the deployment of a monitor model in a secured queue-based environment."

  8. Add the administrative user to the Sender role for the foreign bus by entering the following command:

     AdminTask.addUserToForeignBusRole ('[ -role Sender
     -bus MONITOR. bpmCell.Bus
     -foreignBus MONITOR. monitorCell.Bus
     -user  user_id ]')

  9. In the IBM BPM cell, define a JMS queue with the JNDI name jms/com.ibm.lombardi/EventEmissionQueue. The JMS queue must point to the LombardiEventEmitterInputQueue foreign destination queue.

  10. In the IBM BPM cell, define the security settings for emitting events. The BPM events are emitting using the user ID and password defined by the MonitorBusAuth J2C authentication alias. Verify that the user specified in the MonitorBusAuth alias has the Sender role for the LombardiEventEmitterInputQueue foreign destination.

      1. If you used the scripts provided by Business Monitor to create the SI bus link, then the MonitorBusAuth J2C authentication alias already exists. If the alias does not exist, you can create the alias manually, or edit a property in the BPM server common configuration files to define the alias, as described in the following steps.
         1. Edit the j2c-authentication-alias property in the monitor-event-emission property, located in the IBM BPM server common configuration file, 100Custom.xml. This file is located in the following directory:

            PROFILE_HOME\config\cells\ cell_name\nodes\ node_name\servers\ server_name\ profile-type\config

            where profile-type is one of the following values:

            • process-center
            • process-server

         2. Copy the following property settings into the 100Custom.xml file as a child of the <common> element.

            <monitor-event-emission>
              <enabled>true</enabled>
              <j2c-authentication-alias> MonitorBusAuth</j2c-authentication-alias>
            <monitor-event-emission>

  11. In the IBM BPM cell, define a JMS queue connection factory with the JNDI name jms/com.ibm.lombardi/EventEmissionQueueFactory. Specify the local monitor bus.

  12. When you deploy the custom monitor model to a Monitor server, set the Location option for the CEI destination to Local.

• Multiple-cell environment with the BPM event emitter service in the IBM BPM Advanced cell:

  You can have events emitted to the CEI event service that is already configured within the IBM BPM Advanced cell.

  You then configure your Business Monitor model to receive the events that were emitted to the CEI event service by way of table-based event delivery.

  1. Configure IBM BPM Advanced.

     After the configuration, a CEI event service is deployed.

  2. Configure server-to-server SSL, as described in Configure server-to-server SSL in multiple-cell environments.
  3. Share LTPA keys, as described in Sharing LTPA keys.
  4. Enable identity assertion, as described in Enabling identity assertion.

  5. Configure table-based event delivery, as described in Configure table-based event delivery in a multiple-cell environment.

  6. Configure the remote MONITOR bus in the IBM BPM cell by following the procedure in Configure queue-based event delivery in a multiple-cell environment.

     This step creates a MONITOR bus in the IBM BPM cell and a link to the MONITOR bus in the Business Monitor cell.

     You can still choose between table-based and queue-based event delivery when you are installing a Business Monitor model.

  7. Create a J2C authentication alias named EventEmitterAlias.

     You can use any valid user ID and password combination.

  8. Copy the following files from Business Monitor to the IBM BPM Advanced installation (preserving the directory structure below WAS_HOME):

     WAS_HOME/instalableApps.wbm/EmitterServices.ear
     WAS_HOME/plugins/com.ibm.wbimonitor.admin.command.jar
     WAS_HOME/plugins/com.ibm.wbimonitor.restconfig.jar

  9. After restarting the dmgr, start a wsadmin console and run the following commands. Specify the -lang jython option to use the jython syntax.

     AdminTask.wbmConfigureEventEmitterFactory(['-cluster', 'support_cluster_name']) 
     AdminTask.wbmDeployBPMEmitterService(['-cluster', 'support_cluster_name']) 
     AdminConfig.save()

  10. Restart the IBM BPM Advanced topology.

Monitoring events

Related concepts:
Event flow

Related tasks:
Configure the JMS event emitter service to use the WebSphere MQ messaging provider
Configure queue-based event management in a multiple-cell environment
Use a JMS activation specification to put the event XML into a WebSphere MQ queue
Completing the deployment of a monitor model in a secured queue-based environment
Configure the CEI event service

Related information:
Configure table-based event delivery in a multiple-cell environment