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 callback with synchronous implementation

You can obtain Application Response Measurement (ARM) statistics when callback requests and callback executions use different threads on a synchronous 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 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, as 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.}

Invocation of request and return result

Type	Statistics	Formula	ARM Transaction
Common	TotalResponseTime	t 2 - t 0	X 0.X 1
RequestDeliveryTime	t' 0 - t 0	X 1.X 2
ResponseDeliveryTime	t 2 - t' 1
GoodRequests	Count EXIT
BadRequests	Count FAILURE
ResponseTime	t 3 - t 2
Reference	GoodRefRequest	Count EXIT	X 1.X 2
BadRefRequests	Count FAILURE
RefResponseTime	t' 1 - t' 0

Figure 1. Diagram of an asynchronous callback with a synchronous implementation

Invocation of callback

Type	Statistics	Formula	ARM Transaction
Callback	GoodCB	Count EXIT	X 1.X 3
BadCB	Count FAILURE
CBTime	t 3 – t 2

Application Response Measurement statistics for the Service Component Architecture