METHOD AND SYSTEM FOR ENTERPRISE MONITORING BASED ON A COMPONENT BUSINESS MODEL

• US 20080189644A1
• Filed: 03/25/2008
• Published: 08/07/2008
• Est. Priority Date: 08/26/2005
• Status: Abandoned Application

• Current Assignee: Anil Nigam, David Bernard Flaxer, Guy Jonathan James Rackham, Hung-Yang Chang, John George Vergo, Jun-Jang Jeng, Vijay Sourirajan Iyengar
• Original Assignee: Anil Nigam, David Bernard Flaxer, Guy Jonathan James Rackham, Hung-Yang Chang, John George Vergo, Jun-Jang Jeng, Vijay Sourirajan Iyengar
• Inventors: Iyengar, Vijay Sourirajan, Rackham, Guy Jonathan James, Jeng, Jun-Jang, Vergo, John George, Nigam, Anil, Flaxer, David Bernard, Chang, Hung-yang
• Application Number:
  US12/054,645
• Publication Number:
  US 20080189644A1
• Time in Patent Office: Days
• US Class Current: 715/772
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
• CPC Class Codes: G06Q 10/0639 Performance analysis of employees; Performance analysis of enterprise or organisation operations

Abstract

A method and system for enterprise monitoring maps monitor events to elements of a component business model of the enterprise and displays the mapped events using the component business model. Rules are used to determine whether events captured from a monitor source are monitor events. An enterprise monitor metamodel linking monitor artifacts and elements of a component business model is used to annotate monitor events with data from the component business model of the enterprise.

Claims

1. A method for monitoring an enterprise, comprising:

mapping at least one message from a monitor source to at least one element of a component business model; and

presenting monitoring information from said mapping to a user of the enterprise.

2. A method as in claim 1, said mapping further comprising:

listening to a message from a monitor source;

capturing an event from said message;

using an event rule to determine if said event is a monitor event; and

if said event is a monitor event, annotating said monitor event with component business model data.

3. A method as in claim 1, said presenting further comprising displaying the monitoring information on a component business map of the enterprise.

4. A method as in claim 1, said presenting further comprising generating a report of the monitoring information, the report being sorted by elements of a component business model.

5. A method as in claim 2, said annotating being based on an enterprise monitor metamodel connecting said message from a monitor source to one or more elements of a component business model.

6. A method as in claim 5, wherein said metamodel includes a monitor artifact element, said monitor artifact element being further comprised of a status level element, a monitor data element, and a monitor correlator element.

7. A method as in claim 2, wherein said mapping is provided by a middleware service.

8. A system for monitoring an enterprise, comprising:

means for mapping at least one message from a monitor source to at least one element of a component business model; and

means for presenting monitoring information from said mapping to a user of the enterprise.

9. A system as in claim 8, said mapping means further comprising:

means for listening to a message from a monitor source;

means for capturing an event from said message;

means for using an event rule to determine if said event is a monitor event; and

means for annotating a monitor event with component business model data.

10. A system as in claim 8, said presenting means further comprising means for displaying the monitoring information on a component business map of the enterprise.

11. A system as in claim 8, said presenting means further comprising means for generating a report of the monitoring information, the report being sorted by elements of a component business model.

12. A system as in claim 9, said annotating means being based on an enterprise monitor metamodel connecting said message from a monitor source to one or more elements of a component business model.

13. A system as in claim 12, wherein said metamodel includes a monitor artifact element, said monitor artifact element being further comprised of a status level element, a monitor data element, and a monitor correlator element.

14. A system as in claim 9, wherein said mapping means is implemented by a middleware service.

15. Implementing a service for monitoring an enterprise, comprising the method of:

mapping at least one message from a monitor source to at least one element of a component business model; and

presenting monitoring information from said mapping to a user of the enterprise.

16. A method for implementing a monitoring service as in claim 15, said mapping further comprising:

listening to a message from a monitor source;

capturing an event from said message;

using an event rule to determine if said event is a monitor event; and

if said event is a monitor event, annotating said monitor event with component business model data.

17. A method for implementing a monitoring service as in claim 15, said presenting further comprising displaying the monitoring information on a component business map of the enterprise.

18. A method for implementing a monitoring service as in claim 15, said presenting further comprising generating a report of the monitoring information, the report being sorted by elements of a component business model.

19. A method for implementing a monitoring service as in claim 16, said annotating being based on an enterprise monitor metamodel connecting said message from a monitor source to one or more elements of a component business model.

20. A computer implemented system for monitoring an enterprise, comprising:

first computer code for mapping at least one message from a monitor source to at least one element of a component business model; and

second computer code for presenting monitoring information from said mapping to a user of the enterprise.

21. A computer implemented system as in claim 20, said first computer code for mapping further comprising:

third computer code for listening to a message from a monitor source;

fourth computer code for capturing an event from said message;

fifth computer code for using an event rule to determine if said event is a monitor event; and

sixth computer code for annotating a monitor event with component business model data.