Browse Prior Art Database

An approach to construct the topology diagram for asynchronized transactions in SOA system Disclosure Number: IPCOM000181021D
Original Publication Date: 2009-Mar-24
Included in the Prior Art Database: 2009-Mar-24
Document File: 6 page(s) / 78K

Publishing Venue



Use a foreign-key-like method to correlate the asynchronized transactions and construct of really-happened invocations in the complex SOA system.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 42% of the total text.

Page 1 of 6

An approach to construct the topology diagram for asynchronized transactions in SOA system

In SOA system, many services can work together to finish an invocation . Especially in a large-scale distributed system , in order to response a request, the amount of invoked services is increased largely . The service invocation becomes more and more complex so that it is really hard to know what happen inside the system . The administrator needs to use some monitoringtools to discover the real invocation topology from the system . But up to now, no product supports SOA invocation topology view very well ,especially there are many asynchronized invocations in topology . In fact, there are some problems when monitoring SOA system .

In SOA system, client side and server side are not in the same process /machine. It makes transactiontracking difficult .


For flexibility and performance , SOA supports asynchronized invocation . It will make the invocation topology view reconstruction very



For the current monitoring solution , no one can monitor the asynchronized transactions very well .
Industry standard - ARM. ARM (Application Response Measurement ) is the industry standard for monitoring . But it's not designed to

support SOA transaction.

ITCAM for SOA. ITCAM for SOA can monitor SOA system without asynchronized invocation very well , and display the topology of the

transaction flow. If there is asynchronized invocation in transaction flow , ITCAM for SOA displays the topology through considering the asynchronized invocation as synchronized invocation .

The ITCAM for SOA solution to construct the topology diagram by the following methods :
propagate the correlation information along the request /response flow, for example, the id of service flow, the sequence number.


collect the information of request /response in the client side , server side, and the information of the neighboring service .


build topology of system based on the information above .


Some solution implements it as below . For each invocation, 4 metric logs is recorded at the following intercept points , after client send request, before server received request , after server return response , before client get response . In each intercept point, correlator program interchanges information with the intercept points before it , after it, and peer of it. The information, including ID of service flow (TransactionID), the sequence number, the ID of the service, is recorded in each interception point . Then, the analysis program can rebuild the topology of the request flow based on the correlator information in each intercept point .

For example, in the following chart, 8 metric logs are recorded . For the red intercept point , the intercept point before it is the yellow one, the intercept point after it is the green one , and the intercept...