SYSTEM FOR MANAGING EVENTS IN A CONFIGURATION OF SOA GOVERNANCE COMPONENTS

• US 20110022439A1
• Filed: 07/22/2009
• Published: 01/27/2011
• Est. Priority Date: 07/22/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Arni, Majeed M., Kahan, Eduardo T., Selvage, Mei Y., Coldicott, Peter A.
• Granted Patent: US 8,386,282 B2
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change

Abstract

Embodiments of the invention are associated with a configuration comprising multiple integrated SOA governance components, and are generally concerned with monitoring and managing events that can or are likely to impact on different components of the configuration. One embodiment of the invention, directed to a method, comprises the steps of detecting a particular event that occurs at a particular SOA governance component of the configuration, and routing information pertaining to the detected event to a pre-specified storage location. The method further comprises operating a monitoring mechanism to selectively monitor the information routed to the location, and to determine from the monitored information that the particular event has occurred at the particular component of the configuration. Responsive to determining that the particular event has occurred at the particular component, the monitoring mechanism is further operated to query each of the remaining SOA governance components, in order to identify each of the remaining components in which the particular event does not exist.

Claims

1. In association with a configuration comprising multiple integrated service oriented architecture (SOA) governance components, a method comprising the steps of:

detecting a particular event that occurs at a particular SOA governance component of said configuration;

routing information pertaining to said detected event to a pre-specified storage location;

operating a monitoring mechanism to selectively monitor said information routed to said location, and to determine from said monitored information that said particular event has occurred at said particular component of said configuration; and

responsive to determining that said particular event has occurred at said particular component, further operating said monitoring mechanism to query each of the remaining SOA governance components of said configuration, in order to identify each of said remaining components in which said particular event does not exist.

2. The method of claim 1, wherein:

said monitoring mechanism is operated to determine whether said particular event exists in a given one of said remaining components by first determining whether said given remaining component has been notified of said particular event, and if so determining whether said given remaining component has been changed as a result of said particular event.

3. The method of claim 1, wherein:

each component has an associated plug-in and storage queue.

4. The method of claim 3, wherein:

responsive to the occurrence of an event at a given component, the given component routes a message providing notice of the event to the associated storage queue of the given component.

5. The method of claim 3, wherein:

said mechanism includes an event producer interface for communicating with each component through its associated plug-in and storage queue.

6. The method of claim 3, wherein:

said mechanism is operated to sequentially query the storage queue of each component, to detect messages contained therein that provide notice of the occurrences of events at respective components.

7. The method of claim 1, wherein:

the operation of said mechanism is directed by a specified SOA governance procedure.

8. The method of claim 7, wherein:

said specified SOA governance procedure corresponds to said particular event, and is selected from a set comprising multiple SOA governance procedures that each corresponds to a different event.

9. The method of claim 1, wherein:

responsive to determining that said service state change does not exist on at least one of said remaining components, implementing an action selected from a group of actions, wherein said group includes at least the actions of sending an email to a repository administrator, and creating a human task for administration.

10. The method of claim 1, wherein:

said particular event is selected from a group of events that includes at least a service state change, and the addition of a new SOA governance component to said configuration.

11. In association with a configuration comprising multiple integrated service oriented architecture (SOA) governance components, a computer program product executable in a computer readable medium comprising:

instructions for detecting a particular event that occurs at a particular SOA governance component of said configuration;

instructions for routing information pertaining to said detected event to a pre-specified storage location;

instructions for operating a monitoring mechanism to selectively monitor said information routed to said location, and to determine from said monitored information that said particular event has occurred at said particular component of said configuration; and

instructions responsive to determining that said particular event has occurred at said particular component, for further operating said monitoring mechanism to query each of the remaining SOA governance components of said configuration, in order to identify each of said remaining components in which said particular event does not exist.

12. The computer program product of claim 11, wherein:

said monitoring mechanism is operated to determine whether said particular event exists in a given one of said remaining components by first determining whether said given remaining component has been notified of said particular event, and if so determining whether said given remaining component has been changed as a result of said particular event.

13. The computer program product of claim 11, wherein:

each component has an associated plug-in and storage queue, and responsive to the occurrence of an event at a given component, the given component routes a message providing notice of the event to the associated storage queue of the given component.

14. The computer program product of claim 13, wherein:

said mechanism is operated to sequentially query the storage queue of each component, to detect messages contained therein that provide notice of the occurrences of events at respective components.

15. The computer program product of claim 11, wherein:

the operation of said mechanism is directed by a specified SOA governance procedure that corresponds to said particular event, and is selected from a set comprising multiple SOA governance procedures that each corresponds to a different event.

16. In association with a configuration comprising multiple integrated service oriented architecture (SOA) governance components, apparatus comprising:

means for detecting a particular event that occurs at a particular SOA governance component of said configuration;

means for routing information pertaining to said detected event to a pre-specified storage location;

a monitoring mechanism operable to selectively monitor said information routed to said location, and to determine from said monitored information that said particular event has occurred at said particular component of said configuration; and

means responsive to determining that said particular event has occurred at said particular component, for operating said monitoring mechanism to query each of the remaining SOA governance components of said configuration, in order to identify each of said remaining components in which said particular event does not exist.

17. The apparatus of claim 16, wherein:

said monitoring mechanism is operated to determine whether said particular event exists in a given one of said remaining components by first determining whether said given remaining component has been notified of said particular event, and if so determining whether said given remaining component has been changed as a result of said particular event.

18. The apparatus of claim 16, wherein:

each component has an associated plug-in and storage queue, and

responsive to the occurrence of an event at a given component, the given component routes a message providing notice of the event to the associated storage queue of the given component.

19. The apparatus of claim 18, wherein:

said mechanism is operated to sequentially query the storage queue of each component, to detect messages contained therein that provide notice of the occurrences of events at respective components.

20. The apparatus of claim 16, wherein:

the operation of said mechanism is directed by a specified SOA governance procedure.