IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Monitoring > Enabling and configuring service component monitoring > Monitoring service component events

Monitoring service components with the Common Event Infrastructure server

You can choose to have service component monitoring results published to a Common Event Infrastructure (CEI) server. Service component event points can be specified for monitoring with the CEI server on a permanent basis for viewing and managing application flow, or on an temporary basis for troubleshooting problems.

You can use monitoring to publish the data in service component event points within service component events that are fired across the CEI bus. This approach to monitoring allows you much more flexibility in analyzing your service component activities on your system. You can also use browsers optimized for CEI events, such as the Common Base Event browser.

The events are structured identically to the events sent to loggers, but they are stored on a database which can be accessed by viewers designed specifically for analyzing service component events. Service component event points can be specified within an application when it is created, for continual monitoring at all times after the application is deployed and running on a server (a method known as "static" monitoring). Use static monitoring on service component event points that are of particular importance in the proper flow of component processing on your system. With this information, you can easily oversee the actions of, and interactions between, the service component processes running on your system. You can also quickly detect deviations from the normal flow of these processes, which can indicate that your service components are not working properly.

To configure static monitoring of service components, use Integration Designer to select the service component event points in your applications. The selections are specified in the form of an XML file with a .mon extension that is deployed along with the application. After you have deployed the application on a running server, you cannot turn off or lower the detail level of the monitoring for events specified in the .mon file of the application. To stop this monitoring, you must stop the server and remove the application.

You can also select service component event points for "dynamic" monitoring, which can be enabled and disabled on an application already deployed to a running server. The rationale for performing dynamic monitoring using the CEI server is essentially the same as that for logging: to diagnose and troubleshoot problems on your system. The output is essentially the same as the output that is published to loggers, with Common Base Event elements that make up the structure for each event fired across the CEI bus. Also, like logging data, the differences in detail levels affect only how much of the payload is encoded within the event.

• Configure service component event monitoring using the administrative console
  Use the administrative console to dynamically specify the monitoring function to publish service component events to the Common Event Infrastructure server.
• Tutorial: Using the Common Event Infrastructure server for event monitoring
  This tutorial guides you through an example of setting up monitoring with the CEI server, and how to view events stored in the database.

Monitoring service component events

Related concepts:
Event catalog

Related tasks:
Viewing events with the Common Base Event browser:
Administer Common Event Infrastructure: