WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Asynchronous one-way with synchronous implementation

ARM statistics when a call is submitted (fire and forget) with a synchronous implementation.

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 the table and diagram below, the "current" ARM transaction (denoted as X1) 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 will be used, or a new one will be created. If it is not the starting transaction it will have a parent. This is represented in the following table and diagram with the notation Xn.Xn+1. These are 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 this will not modify the SCA transaction lineage.

Table 1. Invocation of request and return result
Type Statistics Formula ARM Transaction
Common TotalResponseTime t1 - t0 X0.X1
RequestDeliveryTime t'0 - t0 X1.X2
ResponseDeliveryTime N/A N/A
GoodRequests CountEXIT X1.X2
BadRequests CountFAILURE
ResponseTime t'1 - t'0

Diagram of asynchronous one-way call with a synchronous implementation


reference Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/rmon_async_1way_sync_imp.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).