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

Event flow

IBM BPM emits monitoring events, which are sent to a Java Messaging Service (JMS) queue and then used by Business Monitor. The JMS queue and a corresponding JMS queue connection factory are created automatically during installation of Business Monitor. When IBM BPM detects the presence of the JMS queue and the JMS queue connection factory, IBM BPM begins to emit events while executing a process application that has been enabled for business monitoring.

The flow of a monitoring event from IBM BPM to Business Monitor is illustrated in the following diagram.

When Business Monitor and IBM BPM are installed and configured into the same stand-alone server or ND environment, the JMS resources required to enable the flow of events from IBM BPM to Business Monitor are automatically configured. The configuration occurs during profile creation in the case of a stand-alone server profile. In a ND environment, the configuration occurs after configuring and generating a deployment environment. In both cases, the JMS resources are configured to use the default messaging provider. You can manually reconfigure the JMS resources to point to a different messaging provider, such as WebSphere MQ.


Default JMS queue in IBM BPM

IBM BPM looks for a JMS queue and JMS queue connection factory with the following JNDI names:

Events are emitted only when the JMS queue and connection factory are present and available to IBM BPM.


Default JMS queue configured as an input queue in Business Monitor

Business Monitor includes an application called IBM_BPM_EMITTER_SERVICE, which reads events from a JMS queue and submits them to Business Monitor. To ensure that events in the JMS queue can flow to Business Monitor, the following queue, queue connection factory, and activation specification must point to the same JMS queue ( jms/com.ibm.lombardi/EventEmissionQueue) that is the destination for events emitted by IBM BPM:

For more information about configuring the IBM_BPM_EMITTER_SERVICE, refer to the related topic "Configure the environment using wsadmin commands."


Event flow configuration

When IBM BPM Standard and Business Monitor are deployed in separate WebSphere Application Server cells, advanced configuration of the JMS resources is required so that the queue with the events is accessible from both cells. You can create this configuration using either an external messaging provider, such as WebSphere MQ, or using the default messaging provider and an SI bus link. For more information about this advanced configuration, refer to the related topic "Configuring event flow to a remote server."

When IBM BPM Advanced and Business Monitor are deployed in separate WebSphere Application Server cells, you can use the techniques described for IBM BPM Standard. However, you have an additional configuration option, which is to have events emitted to the Comment Event Infrastructure (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. For more information about this advanced configuration, refer to the related topic "Configuring event flow to a remote server."


Disabling event flow

You can prevent IBM BPM from emitting events for a specific process application, or you can prevent the server from emitting events. By default, events are emitted if any of the following conditions are true for the process application:

To disable event emission for a process application, you must clear the Enable for Business Monitoring check box in the Process Apps Settings page, turn off auto-tracking in the process application, and remove any auto-tracking events from the business process definition. Also, if a custom monitor model exists, use IBM Integration Designer to disassociate it from the process application.

To disable event emission for the server, update the 100Custom.xml configuration file, as described in the following steps:

  1. Locate the 100Custom.xml file 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 configuration property and paste it into the 100Custom.xml file as a child of the <common> element: 
    <monitor-event-emission>
  <enabled merge="replace">false</enabled>
</monitor-event-emission>

    If the <common> element is not already in the file, add it. The following is an example of the file: 

    <properties>
 <common merge="mergeChildren">
  <monitor-event-emission>
    <enabled merge="replace">false</enabled>
  </monitor-event-emission>
 </common>
</properties>
  3. Restart the server so that the changes will take effect.

Monitoring events


Related tasks:
Configure event flow to a remote server
Configure the environment using wsadmin commands


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