US2013152106A1PendingUtilityA1

Managing events in a configuration of soa governance components

Assignee: IBMPriority: Jul 22, 2009Filed: Jan 22, 2013Published: Jun 13, 2013
Est. expiryJul 22, 2029(~3 yrs left)· nominal 20-yr term from priority
G06Q 10/06375G06F 9/542
58
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

One embodiment of the invention, directed to a method, comprises the steps of a computer detecting a predetermined type of event resulting from one of an addition of new component to the SOA infrastructure or a change to an existing component of the SOA infrastructure, wherein a notice of the detected event is stored in a repository associated with the component. In response to the detected event, the computer queries other components of the SOA infrastructure, and determines whether the other components have been updated based on the detected event and in response to determining the other components have not been updated based on the detected event, the computer automatically updates the other components of the SOA infrastructure based on the detected event.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for managing events in a service oriented architecture (SOA) infrastructure, the method comprising the steps of:
 a computer detecting a predetermined type of event resulting from one of an addition of a component to the SOA infrastructure or a change to a component of the SOA infrastructure;   responsive to the detected event, the computer determining another component of the SOA infrastructure that requires update based on the detected event and querying the other component of the SOA infrastructure, to determine whether the other component have been updated based on the detected event; and   responsive to determining that the other component has not been updated based on the detected event, the computer automatically updating the other component of the SOA infrastructure based on the detected event.   
     
     
         2 . The method of  claim 1  wherein the SOA infrastructure includes a service registry of available services and the automatic update includes a change in one or more of a state of one of the services, a listing of one of the services in a service registry, and a version of one of the services in the service registry. 
     
     
         3 . The method of  claim 1  wherein the SOA infrastructure includes a service registry of available services and the automatic updating includes a change to a name of one of the services in the service registry in response to a change in a version of the one of the services, wherein the version of the one of the services is representative of a portion of the respective name. 
     
     
         4 . The method of  claim 1 , wherein the step of the computer determining another component of the SOA infrastructure that requires update is based on the computer determining whether that the other component has been notified of the detected event. 
     
     
         5 . The method of  claim 1 , wherein:
 each component of the SOA infrastructure has an associated plug-in and storage queue.   
     
     
         6 . The method of  claim 5 , wherein:
 in response to the detected event at the component, the component routes a message providing the notice of the detected event to the associated storage queue of the component.   
     
     
         7 . The method of  claim 5 , further comprising the step of communicating with each component of the SOA infrastructure through the respective associated plug-in and storage queue. 
     
     
         8 . The method of  claim 5 , further comprising the step of sequentially querying the storage queue of each component of the SOA infrastructure, to detect messages contained therein that provide notice of the occurrences of events at respective components of the SOA infrastructure. 
     
     
         9 . The method of  claim 1 , wherein:
 in response to direction from a system event generator, directing the computer to perform an action of a specified SOA governance procedure.   
     
     
         10 . The method of  claim 9 , wherein:
 the specified SOA governance procedure corresponds to the detected event, and is selected from a set comprising multiple SOA governance procedures each corresponding to a different respective event.   
     
     
         11 . The method of  claim 1 , wherein:
 wherein the automatically updating further includes selecting tasks specific to one of only a vendor and only a user, for implementing an action selected from a group of actions, wherein the group includes at least the actions of sending an email to a repository administrator, and creating a human task for administration.   
     
     
         12 . The method of  claim 1 , wherein:
 the detected event is from a group of events including at least a service state change, and the addition of a new SOA governance component to a configuration of the SOA infrastructure.   
     
     
         13 . A computer program product for managing events in a service oriented architecture (SOA) infrastructure, the computer program product comprising:
 one or more computer readable data storage devices having computer executable program instructions stored thereon, the computer executable program instructions comprising:   computer executable program instructions for detecting a predetermined type of event resulting from an addition of a component to the SOA infrastructure;   computer executable program instructions responsive to the detected event for determining another component of the SOA infrastructure that requires update based on the detected event and for querying the other component of the SOA infrastructure, to determine whether the other component has been updated based on the detected event; and   computer executable program instructions responsive to determining that the other component has not been updated based on the detected event, for automatically updating the other component of the SOA infrastructure based on the detected event.   
     
     
         14 . The computer program product of  claim 13  wherein the computer executable program instructions for determining another component of the SOA infrastructure that requires update is based on:
 computer executable program instructions for determining that the other component has been notified of the detected event. 
 
     
     
         15 . The computer program product of  claim 13 , further comprising:
 computer executable program instructions in response to the detected event at the component, wherein each component of the SOA infrastructure has an associated plug-in and storage queue, for routing a message providing the notice of the detected event to the associated storage queue of the component.   
     
     
         16 . The computer program product of  claim 15 , further comprising:
 computer executable program instructions for sequentially querying the storage queue of each component, to detect messages contained therein that provide notice of the detected events at respective components.   
     
     
         17 . The computer program product of  claim 13 , wherein:
 computer executable program instructions for the system event generator for selecting computer executable program instructions of a specified SOA governance procedure that corresponds to the detected event, selected from a set comprising multiple SOA governance procedures each corresponding to a different event.   
     
     
         18 . A computer program product for managing events in a service oriented architecture (SOA) infrastructure, the computer program product comprising:
 one or more computer readable data storage devices having computer executable program instructions stored thereon, the computer executable program instructions comprising:   computer executable program instructions for detecting a predetermined type of event resulting from a change to an existing component to the SOA infrastructure;   computer executable program instructions responsive to the detected event for determining another component of the SOA infrastructure that requires update based on the detected event for querying the other component of the SOA infrastructure, to determine whether the other component has been updated based on the detected event; and   computer executable program instructions responsive to determining that the other component has not been updated based on the detected event, for automatically updating the other component of the SOA infrastructure based on the detected event.   
     
     
         19 . The computer program product of  claim 18  wherein the computer executable program instructions for determining another component of the SOA infrastructure that requires update is based on:
 computer executable program instructions for determining whether that the other component has been notified of the detected event. 
 
     
     
         20 . The computer program product of  claim 18 , further comprising:
 computer executable program instructions in response to the detected event at the component, wherein each component of the SOA infrastructure has an associated plug-in and storage queue, for routing a message providing the notice of the detected event to the associated storage queue of the component.   
     
     
         21 . The computer program product of  claim 20 , further comprising:
 computer executable program instructions for sequentially querying the storage queue of each component, to detect messages contained therein that provide notice of the detected events at respective components.   
     
     
         22 . The computer program product of  claim 18 , wherein:
 computer executable program instructions for the system event generator for selecting computer executable program instructions of a specified SOA governance procedure that corresponds to the detected event, selected from a set comprising multiple SOA governance procedures each corresponding to a different event.

Join the waitlist — get patent alerts

Track US2013152106A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.