TRACKING DISCRETE ELEMENTS OF DISTRIBUTED TRANSACTIONS

• US 20070294224A1
• Filed: 06/16/2006
• Published: 12/20/2007
• Est. Priority Date: 06/16/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Heler, Jean-Jacques
• Application Number:
  US11/424,685
• Publication Number:
  US 20070294224A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3404 for parallel or distributed programming
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Methods and systems for grouping two or more communications on a computer network into a transaction. One embodiment includes a method of tracking an asynchronous communication between two applications. The method includes receiving a first and third event record associated with a first and third application, wherein the first and third event records indicate the occurrence of an interaction between the first and third applications. The method may further include receiving a second event record from a second application. The second event record may be used by a managing server to group the first and third interactions as belonging to a common transaction.

Claims

1. A computer-implemented method of tracking an asynchronous communication between two applications, comprising:

receiving a first event record associated with a first application, wherein the first event record indicates that the first application sent a first communication to a second application;

receiving a second event record associated with the second application, wherein the second event record indicates that the second application received a second communication from the first application;

determining whether the second communication corresponds to the first communication; and

receiving a third event record from a monitoring application configured to monitor communications between the first application and the second application, wherein the third event record includes a transaction identifier used to correlate the first and second event records as belonging to a group of one or more event records related to a common transaction.

2. The method of claim 1, wherein:

the first event record comprises a first application identifier and a first token;

the second event record comprises a second application identifier and a second token; and

the third event record further comprises a third token.

3. The method of claim 2, wherein determining whether the second communication received by the second application corresponds to the first communication sent by the first application comprises determining whether the first token and the second token match.

4. The method of claim 2, further comprising correlating the first and second event records with a group of one or more event records related to a common transaction, wherein correlating comprises:

determining whether the third event record corresponds to the first and second event records by determining whether the first, second, and third tokens match; and

if so, correlating the first and second event records with a group of one or more event records containing the same transaction identifier, thereby defining a transaction.

5. The method of claim 2, further comprising applying a rule to a third communication to generate the transaction identifier, wherein the third communication corresponds to the first communication sent by the first application if the first token and the third token match.

6. The method of claim 5, wherein the rule is an externally specified rule which dictates how the transaction identifier is generated from one or more of data contained within the third communication, a sending application of the third communication, a receiving application of the third communication, a path taken by the third communication through a computer network, and a size of the third communication.

7. The method of claim 1, wherein the asynchronous communication is one of a message and an invocation.

8. The method of claim 7, wherein the asynchronous communication is one of a Customer Information Control System (CICS®

) invocation, a Java®

application server method invocation, a WebSphere®

MQ application server message, an Information Management System (IMS) message, a Weblogic®

communication, and a WebSphere®

application server (WAS) invocation.

9. A computer program product comprising a computer useable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to perform an operation, comprising:

receiving a first event record associated with a first application, wherein the first event record indicates that the first application sent a first communication to a second application;

receiving a second event record associated with the second application, wherein the second event record indicates that the second application received a second communication from the first application;

determining whether the second communication corresponds to the first communication; and

receiving a third event record from a monitoring application configured to monitor communications between the first application and the second application, wherein the third event record includes a transaction identifier used to correlate the first and second event records as belonging to a group of one or more event records related to a common transaction.

10. The computer program product of claim 9, wherein:

the first event record comprises a first application identifier and a first token;

the second event record comprises a second application identifier and a second token; and

the third event record further comprises a third token.

11. The computer program product of claim 10, wherein determining whether the second communication received by the second application corresponds to the first communication sent by the first application comprises determining whether the first token and the second token match.

12. The computer program product of claim 10, wherein the operation further comprises correlating the first and second event records with a group of one or more event records related to a common transaction, wherein correlating comprises:

determining whether the third event record corresponds to the first and second event records by determining whether the first, second, and third tokens match; and

if so, correlating the first and second event records with a group of one or more event records containing the same transaction identifier, thereby defining a transaction.

13. The computer program product of claim 10, wherein the operation further comprises applying a rule to a third communication to generate the transaction identifier, wherein the third communication corresponds to the first communication sent by the first application if the first token and the third token match.

14. The computer program product of claim 13, wherein the rule is an externally specified rule which dictates how the transaction identifier is generated from one or more of data contained within the third communication, a sending application of the third communication, a receiving application of the third communication, a path taken by the third communication through a computer network, and a size of the third communication.

15. A system for monitoring communications between applications in a distributed computing environment, comprising:

a first application configured to send a first communication to a second application, wherein the first communication corresponds to a first event record;

the second application configured to receive a second communication from the first application, wherein the second communication corresponds to a second event record;

a managing server configured to;

determine whether the second communication corresponds to the first communication; and

receive a third event record from a monitoring application configured to monitor communications between the first application and the second application, wherein the third event record includes a transaction identifier used to correlate the first and second event records as belonging to a group of one or more event records related to a common transaction.

16. The system of claim 15, wherein:

the first event record comprises a first application identifier and a first token;

the second event record comprises a second application identifier and a second token; and

the third event record further comprises a third token.

17. The system of claim 16, wherein the managing server is further configured to determine whether the second communication corresponds to the first communication by being configured to determine whether the first token and the second token match.

18. The system of claim 16, wherein the managing server is further configured to:

determine whether the third event record corresponds to the first and second event records by determining whether the first, second, and third tokens match; and

if so, correlating the first and second event records with a group of one or more event records containing the same transaction identifier, thereby defining a transaction.

19. The system of claim 16, wherein the monitoring application is further configured to apply a rule to a third communication to generate the transaction identifier, wherein the third communication corresponds to the first communication sent by the first application if the first token and the third token match.

20. The system of claim 19, wherein the rule is an externally specified rule which dictates how the transaction identifier is generated from one or more of data contained within the third communication, a sending application of the third communication, a receiving application of the third communication, a path taken by the third communication through a computer network, and a size of the third communication.

21. A method of tracking discrete elements of a distributed transaction in an asynchronous processing environment, comprising:

monitoring a plurality of applications configured to process the distributed transaction; and

correlating an asynchronous data communication from a first application to a second application within the asynchronous processing environment as being a part of the distributed transaction, wherein the asynchronous data communication is a discrete element of the distributed transaction.

22. The method of claim 21, wherein monitoring comprises:

monitoring the asynchronous data communication between the first application and the second application;

generating an event record describing the communication;

sending the event record to a managing server; and

correlating the event record with related event records to describe the processing of the asynchronous data communication.

23. The method of claim 21, wherein correlating comprises:

comparing a first set of one or more event records which describe a first asynchronous data communication to a second set of one or more event records which describe other asynchronous data communications;

identifying a subset of event records from the second set of event records which contain a same transaction identifier as the first set of event records; and

if any such subset of event records exists, determining that the first asynchronous data communication and asynchronous data communications described by the subset of event records are parts of the distributed transaction.