IBM BPM, V8.0.1, All platforms > Measuring and improving business processes > Monitoring > Enabling and configuring service component monitoring > Monitoring performance > Application Response Measurement statistics for the Service Component Architecture
Asynchronous one way with asynchronous implementation
Application Response Measurement (ARM) statistics when a call is submitted (fire and forget) with an asynchronous implementation.
Parameters
Event monitoring for SCA components includes the event points
that are shown in black 
, while the event points shown in blue 
are used only to calculate and fire PMI/ARM statistics.
In Table 1 and in Figure 1, the "current" ARM
transaction (denoted as X 1) is created when the calling service component was invoked for the first time.
If the caller is not a service component, the current ARM transaction is used, or a new one is created. If it is not the starting transaction, it has a parent. This relationship is represented in the following table and diagram with the notation X n.X n+1.
The notation is used to show the transaction lineage. Every SCA invocation
starts a new transaction, which is parented by the current transaction of the caller. You can create new transactions and you can access the current transaction, but you cannot modify the SCA transaction lineage.
Figure 1. An asynchronous one-way call with an asynchronous implementation
Application Response Measurement statistics for the Service Component Architecture
Type
Statistics
Formula
ARM Transaction
Common
TotalResponseTime
t 1 - t 0
X 0.X 1
RequestDeliveryTime
t' 0 - t 0
X 1.X 2
ResponseDeliveryTime
N/A
N/A
GoodRequests
Count EXIT
X 1.X 2
BadRequests
Count FAILURE
ResponseTime
t 2 - t 0
Reference
GoodRefRequest
Count EXIT
X 0.X 1
BadRefRequest
Count FAILURE
RefResponseDuration
t 1 - t 0
