Synchronous invocations

You can obtain Application Response Measurement (ARM) performance statistics from a simple Service Component Architecture (SCA) call to a service and the response from the service.

Parameters

Event monitoring for SCA components includes the event points that are shown in black Black event point , while the event points shown in blue Blue event point are used only to calculate and fire PMI/ARM statistics.

In Table 1 and Figure 1, the current ARM transaction (denoted as X₁) 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 then 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 document 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 they do not modify the SCA transaction lineage.

Table 1. ARM statistics for synchronous invocations of SCA
Statistics	Formula	ARM Transaction
TotalResponseTime	`t₃ - t₀`	`X₀ .X₁`
RequestDeliveryTime	`t₁ - t₀`	`X₁ .X₂`
ResponseDeliveryTime	`t₃ - t₂`
GoodRequests	`Count_EXIT`
BadRequests	`Count_FAILURE`
ProcessTime	`t₂ - t₁`

Diagram of ARM statistics obtained from an SCA call with a synchronous implementation — Figure 1. ARM statistics obtained from an SCA call with a synchronous implementation