US 7,523,463 B2
Technique to generically manage extensible correlation data
Harm Sluiman, Scarborough (Canada); Eric Labadie, Toronto (Canada); Abdolreza Salahshour, Raleigh, N.C. (US); and Douglas Andrew Wood, Raleigh, N.C. (US)
Assigned to International Business Machines Corporation, Armonk, N.Y. (US)
Filed on Nov. 06, 2003, as Appl. No. 10/703,036.
Claims priority of application No. 2424006 (CA), filed on Mar. 28, 2003.
Prior Publication US 2004/0237093 A1, Nov. 25, 2004
Int. Cl. G06F 3/00 (2006.01); G06F 9/44 (2006.01); G06F 9/46 (2006.01); G06F 13/00 (2006.01)
U.S. Cl. 719—318  [719/313; 709/224] 2 Claims
OG exemplary drawing
 
1. A correlator service being stored on a computer readable storage medium for correlating a series of events, the correlator service comprising:
a mechanism which when executed by a processor for generating a first Globally Unique Correlator (GUC) adapted to uniquely identify one or more occurrences of an event among the series of events wherein the first GUC comprises a globally unique identifier (GUID) to uniquely identify the one or more occurrences of the event, wherein the first GUC further comprises two or more sequence counters, said correlator service adapted to maintain the two or more sequence counters for identifying a sequence of the one or more occurrences of the event;
a mechanism which when executed by the processor, generating a correlator, the generated correlator comprising an event identifier and a temporal identifier for the event wherein a first characteristic of the event is defined by a process generating the event and wherein one of the two or more sequence counters defines a process sequential counter responsive to the first characteristic to sequentially order all executions of the process and wherein the temporal identifier comprises a count of the process sequential counter, wherein a second characteristic of the event is defined by a thread of the process generating the event and wherein another one of the two or more sequence counters defines a thread sequential counter responsive to the second characteristic to sequentially order all executions of the thread of the process and wherein the temporal identifier comprises a count of the thread sequential counter, wherein a third characteristic of the event is defined by a provider requiring the generated correlator and wherein the thread sequential counter is further responsive to the third characteristic to sequentially order all executions of the thread for the provider; and
said correlator service adapted to provide the GUC for defining a key for associating one or more extensible correlators for each occurrence of the event, wherein one of the extensible correlators comprises a transport correlator for including in a first communication adapted to transport the transport correlator for associating the first GUC with a second GUC identifying an occurrence of a second event having a relationship with the event and wherein said transport correlator is configured to minimally impact the transport of the communication, wherein the first communication comprises a second communication for causing the occurrence of the second event, wherein the first communication is facilitated by a middleware and wherein the correlator service is adapted to provide the transport correlator to said middleware.