How do you enable monitoring?

This section gives a brief overview of the different ways that you can specify service component event points for monitoring, depending on the type of monitoring you are planning to do on the process server.

Performance statistics
Use the Performance Monitoring Infrastructure (PMI) section of the administrative console to specify the particular event points and their associated performance measurements that you wish to monitor. After you start monitoring service component performance, the generated statistics are published at certain intervals to the Tivoli® Performance Viewer. You can use this viewer use to watch the results as they occur on your system, and, optionally, log the results to a file that can be later viewed and analyzed within the same viewer.
Common Base Events for problem determination and business process monitoring
You can specify, at the time you create an application, to monitor service component event points — along with a certain level of detail for those events — on a continual basis after the application is deployed on a running server. You can also select event points to monitor after the application has been deployed and the events invoked at least once on the process server. In both cases, the events generated by monitoring will be fired across the Common Event Infrastructure (CEI) bus. These events can be published to a log file, or to a configured CEI Server database. WebSphere® Process Server supports two types of Common Base Event enablement for problem determination and business process monitoring:
Static
Certain events points within an application and their level of detail can be tagged for monitoring using the WebSphere Integration Developer tooling. The selections indicate what event points are to be continuously monitored, and are stored in a file with a .mon extension this is distributed and deployed along with the process server application. Once the process server is configured to use a CEI server, the monitoring function will begin firing Common Base Events to a CEI server whenever the specified services are invoked. As long as the application is deployed on the process server, the service component event points specified in the .mon file will be constantly monitored until the application is stopped. You can specify additional events to be monitored in a running application, and increase the detail level for event points that are already monitored. But as long as that application remains active you cannot stop, or lower the detail level of, the monitored event points specified by the .mon of the deployed application.
Dynamic
If additional event points need to be monitored during the processing of an application without shutting down the server, then you can use dynamic monitoring. Use the administrative console to specify service component event points for monitoring, and set detail level for the payload that will be included in the Common Base Event. A list is compiled of the event points that have been reached by a processed service component after the process server was started. Choose from this list individual event points or groups of event points for monitoring, with the Common Base Events directed either to the logger or to the CEI server database.

The primary purpose of the Dynamic enablement is for creating correlated Common Base Events that are published to logs, which allow you to perform problem determination on services. Common Base Events can be large — depending on how much data is being requested — and can tax database resources if you choose to send events to the CEI server. Consequently, you should publish dynamically monitored events to the CEI server only if you need to read the business data of the events, or if you otherwise need to keep a database record of the events.

Related concepts
Monitoring performance
Related tasks
Enabling and configuring service component monitoring
Related information
Configuring the Common Event Infrastructure
Enabling Common Base Events and the audit trail

Terms of use |

Last updated: Thu Apr 27 14:31:34 2006

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