Method and apparatus for correlation of events in a distributed multi-system computing environment

• US 20060085798A1
• Filed: 10/04/2005
• Published: 04/20/2006
• Est. Priority Date: 05/05/2000
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Bristol Technology Inc (HP Inc.)
• Inventors: Bendiksen, Aage, Tseng, Benny, Lu, Zhongliang
• Granted Patent: US 7,996,853 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

There is provided a method that includes (i) examining first data from a first Application Program Interface (API) call and second data from a second API call to determine whether (a) the first API call sent a message, and the second API call received the message, or (b) the first API call was conducted in a transactional unit of work, and the second API was also conducted in the transactional unit of work, and (ii) employing the first data and the second data in a subsequent process, if either of (a) or (b) is true.

Claims

1-37. -37. (canceled)

38. A method comprising:

examining first data from a first Application Program Interface (API) call and second data from a second API call to determine whether;

(a) said first API call sent a message, and said second API call received said message, or

(b) said first API call was conducted in a transactional unit of work, and said second API was also conducted in said transactional unit of work; and

employing said first data and said second data in a subsequent process, if either of (a) or (b) is true.

39. The method of claim 38,

wherein said method is employed in a distributed data processing system that includes a first processor and a second processor,

wherein said first API call is invoked by a first process running on said first processor, and

wherein said second API call is invoked by a second process running on said second processor.

40. The method of claim 38, wherein said subsequent process comprises displaying said data.

41. The method of claim 38, further comprising:

before said examining;

intercepting said first API call; and

determining whether said first API call meets a criterion;

wherein said examining is contingent on said first API meeting said criterion.

42. The method of claim 41, wherein said intercepting includes operating a sensor that is automatically enabled for responding to an occurrence of an error condition or a change in program states or environments.

43. The method of claim 41, wherein said intercepting includes operating a sensor that is automatically enabled upon an occurrence of a pre-programmed triggering event, the sensor thereafter capturing all event data that satisfies a specific data collection filter.

44. A method comprising:

examining first data from a first Application Program Interface (API) call and second data from a second API call to determine whether said first API call sent a message, and said second API call received said message; and

employing said first data and said second data in a subsequent process, if said first API call sent said message, and said second API call received said message.

45. The method of claim 44,

wherein said method is employed in a distributed data processing system that includes a first processor and a second processor,

wherein said first API call is invoked by a first process running on said first processor, and

wherein said second API call is invoked by a second process running on said second processor.

46. The method of claim 44, wherein said subsequent process comprises displaying said first data.

47. The method of claim 44, further comprising:

before said examining;

intercepting said first API call; and

determining whether said first API call meets a criterion;

wherein said examining is contingent on said first API meeting said criterion.

48. The method of claim 47, wherein said intercepting includes operating a sensor that is automatically enabled for responding to an occurrence of an error condition or a change in program states or environments.

49. The method of claim 47, wherein said intercepting includes operating a sensor that is automatically enabled upon an occurrence of a pre-programmed triggering event, the sensor thereafter capturing all event data that satisfies a specific data collection filter.

50. A method comprising:

examining first data from a first Application Program Interface (API) call and second data from a second API call to determine whether said first API call was conducted in a transactional unit of work, and said second API was also conducted in said transactional unit of work; and

employing said first data and said second data in a subsequent process, if said first API call was conducted in said transactional unit of work, and said second API was also conducted in said transactional unit of work.

51. The method of claim 50,

wherein said method is employed in a distributed data processing system that includes a first processor and a second processor,

wherein said first API call is invoked by a first process running on said first processor, and

wherein said second API call is invoked by a second process running on said second processor.

52. The method of claim 50, wherein said subsequent process comprises displaying said first data.

53. The method of claim 50, further comprising:

before said examining;

intercepting said first API call; and

determining whether said first API call meets a criterion;

wherein said examining is contingent on said first API meeting said criterion.

54. The method of claim 53, wherein said intercepting includes operating a sensor that is automatically enabled for responding to an occurrence of an error condition or a change in program states or environments.

55. The method of claim 53, wherein said intercepting includes operating a sensor that is automatically enabled upon an occurrence of a pre-programmed triggering event, the sensor thereafter capturing all event data that satisfies a specific data collection filter.