Monitoring service component events

WebSphere Process Server monitoring can capture the data in a service component at a certain event point. These events are formatted in a standard called the Common Base Event. You can have the process server publish these events to the logging facilities, or you can utilize the more versatile monitoring capabilities of a Common Event Infrastructure server.

As noted elsewhere in this documentation, 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. Once 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 WebSphere Process Server does not address this type of continuous monitoring. For more information on this subject, refer to the WebSphere Integration Developer documentation.

You can use WebSphere Process Server 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 WebSphere Process Server to diagnose problems, analyze the process flow of your applications, or audit how your applications are used.


(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)