Performance Monitoring Infrastructure statistics

You can monitor 28 different performance statistics in WebSphere Process Server.

Three performance statistics are available from earlier versions WebSphere® Process Server, which you can use to monitor performance for certain process server events. Additionally, you can now monitor 25 additional performance statistics in WebSphere Process Server version 6.0.2. These new statistics differ from the process server statistics in that they measure the performance of Service Component Architecture (SCA) processes. The SCA is the layer where your applications are actually processed, which differs from the process server events that are handled by the Common Event Infrastructure. The SCA-specific statistics are calculated from service invocations of an application, which may be comprised of one or more service components. You can use the SCA-specific statistics to assess a variety of performance measurements of the processing of your applications.

All performance measurements are either counters (a cumulative number of the firings of a given event point), or timers (the duration, measured in milliseconds, between the firings of two event points).

Process server events

These statistics are limited to service component events with ENTRY, EXIT, and FAILURE natures. Each statistic is created for a single event of a given process server-specific event type (such as a particular business rule event) in an application. The following table lists the statistics for process server events:
Table 1. Service component event statistics
Statistic name Type Description
BadRequests Counter Number of failed invocations of the event.
GoodRequests Counter Number of successful invocations of the event.
ResponseTime Timer Elapsed time for event completion.
Each event kind (and their relevant elements) that can be monitored are listed below:
  • Business process
    • Process
  • Human task
    • Task
  • Business rule
    • Operation
  • Business state machine
    • Transition
    • Guard
    • Action
    • EntryAction
    • ExitAction
  • Map
    • Map
    • Transformation
  • Mediation
    • OperationBinding
    • ParameterMediation
  • Resource adapter
    • InboundEventRetrieval
    • InboundEventDelivery
    • Outbound

Service Component Architecture-specific statistics

The SCA-specific statistics shown in the following tables are — in a very simplified manner — time and count measurements of caller invocations to the SCA layer, and the results returned from a service. There are, in fact, a number of service invocation patterns that vary between synchronous and asynchronous implementations of deferred responses, results retrievals, callbacks, and one-way invocations. All of these, however, have traits that you can understand are between the caller, and a service, or, in some cases, a datasource, with the SCA layer interposed in between.
Table 2. Common. These statistics are common to all service invocation patterns.
Statistic name Type Description
GoodRequests Counter Number of server invocations not raising exceptions.
BadRequests Counter Number of server invocations raising exceptions.
ResponseTime Timer Duration measured on the server side between the reception of a request and computing the result.
TotalResponseTime Timer Duration measured on the caller side, from the time a caller requests a service to the time when the result is available for the caller. Does not include the processing of the result by the caller.
RequestDeliveryTime Timer Duration measured on the caller side, from the time a caller requests a service to the time when the request is handed over to the implementation on the server side. In a distributed environment the quality of this measurement depends on the quality of synchronization of system clocks.
ResponseDeliveryTime Timer The time required to make the result available to the client. In the case of deferred response this time doesn’t include the result retrieve time. In a distributed environment the quality of this measurement depends on the quality of synchronization of system clocks.
Table 3. Reference. These statistics occur when a caller makes an invocation to the SCA layer or a datasource, without a response from the service.
Statistic name Type Description
GoodRefRequests Counter Number of caller invocations to the SCA layer that do not raise exceptions.
BadRefRequests Counter Number of caller invocations to the SCA layer that do raise exceptions.
RefResponseTime Timer Duration measured on the caller side, from the time the caller makes a request to the SCA layer and the time when the results of that call are returned to the caller.
BadRetrieveResult Counter Number of caller invocations to a datasource that do raise exceptions.
GoodRetrieveResult Counter Number of caller invocations to a datasource that do not raise exceptions.
RetrieveResultResponseTime Timer Duration measured on the caller side, from the time the caller makes a request to the datasource and the time when the datasource response is returned to the caller.
RetrieveResultWaitTime Timer  
Table 4. Target. These statistics occur when there are requests that originate between the service and the SCA or a datasource.
Statistic name Type Description
GoodTargetSubmit Counter Number of SCA invocations to the service that do not raise exceptions.
BadTargetSubmit Counter Number of SCA invocations to the service that do raise exceptions.
TargetSubmitTime Timer Duration measured on the server side, from the time the SCA makes a request to the service and the time when the results of that call are returned to the SCA.
GoodResultSubmit Counter Number of service invocations to the datasource that do not raise exceptions.
BadResultSubmit Counter Number of service invocations to the datasource that do raise exceptions.
ResultSubmitTime Timer Duration measured on the server side, from the time the service makes a request to the datasource and the time when the results of are returned to the service.
Table 5. Callback. These statistics occur when a callback (a "sibling" of the original call) is present on the caller.
Statistic name Type Description
GoodCB Counter Number of SCA invocations to the callback that do not raise exceptions.
BadCB Counter Number of SCA invocations to the callback that do raise exceptions.
CBTime Timer Duration from the time the SCA makes a request to the callback, and the time when the results from the callback are returned to the SCA.
GoodCBSubmit Counter Number of invocations from the service to the SCA handling the callback that do not raise exceptions.
BadCBSubmit Counter Number of invocations from the service to the SCA handling the callback that do raise exceptions.
CBSubmitTime Timer Duration from the time the service makes a request to the SCA handling the callback, and the time when the results from the SCA to the service.

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