You can choose to have service component monitoring results published to a Common Event Infrastructure server. These events are structured identically to the events sent to loggers, but 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 for monitoring with the Common Event Infrastructure server on a permanent basis for viewing and managing application flow, or on an ad-hoc basis for troubleshooting problems.
A unique capability of WebSphere® Process Server monitoring is its ability to publish the data in service component event points within service component events that are fired across the Common Event Infrastructure (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, which is included with the process server.
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. You would perform 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 overall actions of, and interactions between, the service component processes running on your system. You would also have the ability to quickly detect deviations from the normal flow of these processes, which may indicate that your service components are not working properly.
To configure static monitoring of service components, you would use WebSphere Integration Developer to select the service component event points in your applications that will be deployed on the process server. The selections are specified in the form of an XML file with a .mon extension that will be deployed along with the application. Once deployed on a running server, you will not be able to turn off or lower the detail level of the monitoring for events specified in the .mon file of the application; you must stop the server and undeploy the application to stop this kind of monitoring. Consult the WebSphere Integration Developer Information Center for details on creating and deploying applications with .mon files.
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 that which is published to loggers, with Common Base Event elements comprising 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.
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)