TRACKING DISCRETE ELEMENTS OF DISTRIBUTED TRANSACTIONS
First Claim
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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
23 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
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. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
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. - View Dependent Claims (16, 17, 18, 19, 20)
-
-
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. - View Dependent Claims (22, 23)
-
Specification