Method, system and program product for configuring an event management system

• US 20060036713A1
• Filed: 08/10/2004
• Published: 02/16/2006
• Est. Priority Date: 08/10/2004
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Nastacio, Denilson, Cornpropst, Jason H., Araujo, Carlos Cesar F.
• Application Number:
  US10/914,914
• Publication Number:
  US 20060036713A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

An improved solution for configuring an event management system. In particular, a correlation rule can be deployed based on metadata for the correlation rule and/or a correlation engine. The metadata can describe one or more capabilities of the corresponding correlation rule/correlation engine. As a result, the combined capabilities can be readily considered when deploying the correlation rule.

Claims

1. A method of configuring an event management system, the method comprising:

obtaining rule metadata for at least one correlation rule, wherein the rule metadata describes a capability of the at least one correlation rule;

obtaining engine metadata for at least one correlation engine, wherein the engine metadata describes a capability of the at least one correlation engine; and

configuring the event management system based on the rule metadata and the engine metadata.

2. The method of claim 1, wherein the configuring step includes deploying the at least one correlation rule to the at least one correlation engine based on at least one of the rule metadata and the engine metadata.

3. The method of claim 1, wherein the configuring step includes determining if a combination of the at least one correlation engine and the correlation rule provides a desired function.

4. The method of claim 1, wherein the configuring step includes determining a number of the at least one correlation engine at which the at least one correlation rule is deployed.

5. The method of claim 1, further comprising deploying a plurality of correlation engines in a distributed event management system.

6. The method of claim 1, wherein the configuring step includes automatically generating a deployment recommendation based on at least one of the rule metadata and the engine metadata.

7. The method of claim 1, further comprising generating the at least one correlation rule.

8. The method of claim 1, wherein the obtaining rule metadata step includes:

generating the rule metadata based on the at least one correlation rule; and

associating the rule metadata with the at least one correlation rule.

9. The method of claim 1, wherein the obtaining engine metadata step includes:

generating the engine metadata based on the at least one correlation engine; and

associating the engine metadata with the at least one correlation engine.

10. A method of deploying a correlation rule, the method comprising:

obtaining rule metadata for the correlation rule, wherein the rule metadata describes a capability of the correlation rule;

obtaining engine metadata for at least one correlation engine, wherein the engine metadata describes a capability of the at least one correlation engine; and

deploying the correlation rule to the at least one correlation engine based on at least one of the rule metadata and the engine metadata.

11. The method of claim 10, wherein the deploying step includes determining if a combination of each of the at least one correlation engine and the correlation rule provides a desired function.

12. The method of claim 11, wherein the deploying step further includes automatically deploying the correlation rule to each of the at least one correlation engine for which the combination provides the desired function.

13. The method of claim 10, wherein the deploying step includes:

determining a number of correlation engines at which the correlation rule is deployed; and

generating a deployment recommendation based on the number and the rule metadata.

14. A system for managing events, the system comprising:

a rule system for obtaining rule metadata for a correlation rule, wherein the rule metadata describes a capability of the correlation rule;

an engine system for obtaining engine metadata for a correlation engine, wherein the engine metadata describes a capability of the correlation engine; and

a deployment system for deploying the correlation rule to the correlation engine based on at least one of the rule metadata and the engine metadata.

15. The system of claim 14, further comprising a plurality of distributed correlation engines, wherein each of the plurality of distributed correlation engines has associated engine metadata.

16. The system of claim 14, wherein the events comprise at least one of business events and network events.

17. The system of claim 14, further comprising at least one event server for forwarding an event to the correlation engine.

18. The system of claim 14, further comprising at least one event source for generating an event.

19. A program product stored on a recordable medium for deploying a correlation rule, which when executed comprises:

program code for obtaining rule metadata for the correlation rule, wherein the rule metadata describes a capability of the correlation rule;

program code for obtaining engine metadata for at least one correlation engine, wherein the engine metadata describes a capability of the at least one correlation engine; and

program code for deploying the correlation rule to the at least one correlation engine based on at least one of the rule metadata and the engine metadata.

20. The program product of claim 19, wherein the program code for deploying includes program code for determining if a combination of each of the at least one correlation engine and the correlation rule provides a desired function.

21. The program product of claim 20, wherein the program code for deploying further includes program code for automatically deploying the correlation rule to each of the at least one correlation engine for which the combination provides the desired function.

22. The program product of claim 19, wherein the program code for deploying includes:

program code for determining a number of correlation engines at which the correlation rule is deployed; and

program code for generating a deployment recommendation based on the number and the rule metadata.

23. A system for deploying an application for configuring an event management system, the system comprising:

a computer infrastructure being operable to;

obtain rule metadata for at least one correlation rule, wherein the rule metadata describes a capability of the at least one correlation rule;

obtain engine metadata for at least one correlation engine, wherein the engine metadata describes a capability of the at least one correlation engine; and

configure the event management system based on the rule metadata and the engine metadata.

24. Computer software embodied in a propagated signal for configuring an event management system, the computer software comprising instructions to cause a computer system to perform the following functions:

obtain rule metadata for at least one correlation rule, wherein the rule metadata describes a capability of the at least one correlation rule;

obtain engine metadata for at least one correlation engine, wherein the engine metadata describes a capability of the at least one correlation engine; and

configure the event management system based on the rule metadata and the engine metadata.