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

Monitoring service component events

IBM BPM monitoring can capture the data in a service component at a certain event point.

You can view each event in a log file, or you can use the more versatile monitoring capabilities of a Common Event Infrastructure server.

Applications that are deployed on the process server may contain a specification of service component events that will be monitored for as long as the application runs. If you developed the application using the WebSphere Integration Developer, then you can specify service component events to monitor continuously. This specification is included as part of the application, and comes in the form of file with a .mon extension that is read by the process server when the application is deployed. After the application is started, you will not be able to turn off monitoring of the service components specified in the .mon file. The documentation for the IBM BPM does not address this type of continuous monitoring. For more information about this subject, refer to the Integration Designer documentation.

You can use IBM BPM to monitor service component events that are not already specified in the .mon file of the application. You can configure the process server to direct the output of the event monitors to a log file, or to a Common Event Infrastructure server database. The monitored events will be formatted using the Common Base Event standard, but you can regulate the amount of information contained in each event. Use the monitoring facilities in IBM BPM to diagnose problems, analyze the process flow of your applications, or audit how your applications are used.

• Enabling monitoring of business process and human task events
  

  You must configure IBM BPM to support monitoring of business process and human task service components before you do any actual monitoring of those service component kinds.

• Configure logging for service component events
  

  You can choose to use the logging facilities of WebSphere Application Server to capture the service component events fired by process server monitoring. Use the loggers to view the data in events when you diagnose problems with the processing of your applications.

• 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.

• Session monitoring
  

  You can monitor multiple events that are part of the same session, by using the Common Base Event browser to find all events on the Common Event Infrastructure database that contain the identical session ID attribute.

Enabling and configuring service component monitoring

Related concepts:
Why use monitoring?
What do you monitor?