System and method for synchronizing service metadata

Abstract

A system and method for synchronizing service metadata into a format for canonical representation of service metadata and publishing the synchronized service metadata into a metadata repository. The method comprises: receiving service metadata from a service producer; normalizing the service metadata into the format for canonical representation of service metadata; and publishing normalized service metadata into a metadata repository that supports the format for canonical representation of service metadata. The system comprises: at least one connector for each service producer, wherein the connector permits a synchronization system to communicate bi-directionally with the service producer; one normalizer for each service producer, wherein the normalizer transforms the service metadata into a format for the canonical representation of service metadata; and at least one provider for each service producer, wherein the provider publishes the canonical representation of service metadata into a metadata repository.

1. A method for synchronizing service metadata into a format for canonical representation of service metadata, comprising:
 inspecting a plurality of applications, each application providing at least one service having service metadata associated therewith, wherein said each application generates the service metadata in a native format, and wherein the service metadata includes at least a set of service interfaces and a set of service dependencies between said service interfaces; 
 providing a plurality of connectors for said plurality of applications, wherein each type of said application is associated with a different connector depending on said type of the application; 
 obtaining the service metadata from each of said plurality of applications by the set of connectors, wherein each connector populates a node object with the service metadata in said native format; 
 providing said node object from the connector to a normalizer; 
 normalizing the service metadata of said each application by the normalizer, wherein the normalizer converts the node object from the native format into the format for canonical representation of service metadata and creates an artifact to contain the canonical representation, and wherein the format for the canonical representation of the service metadata is Service Component Architecture (SCA); 
 storing the artifact into a repository; 
 constructing a synchronized dependency graph based on the service dependencies between the service interfaces, wherein the service dependencies are normalized; and 
 exposing, by said repository, an interface to retrieve the artifact associated with an application, wherein once the artifact is retrieved, a set of all dependent artifacts related to said artifact as indicated by the dependency graph are also retrieved, and wherein the interface exposed by the repository is Universal Description, Discovery, and Integration (UDDI). 
 
     
     
       2. The method of  claim 1 , wherein the service metadata includes: design-time metadata, deployment metadata, service interfaces, service dependencies, schemas, properties, relationships between services, service bindings, policies, and exposable implementation details. 
     
     
       3. The method of  claim 1 , wherein a service consumer accesses the backend system to obtain the normalized service metadata. 
     
     
       4. A system to synchronize service metadata into a format for canonical representation of service metadata, said system comprising:
 a plurality of applications executing on one or more computing devices, each application providing at least one service having service metadata associated therewith, wherein said each application generates the service metadata in a native format, and wherein the service metadata includes at least a set of service interfaces and a set of service dependencies between said service interfaces; 
 at least one connector associated with each of said plurality of applications, said connector executed by the one or more computing devices, wherein each type of said application is associated with a different connector depending on said type of the application, wherein the connector permits a synchronization system to communicate bi-directionally with the each application, and wherein the connector obtains the service metadata from the application associated with the connector, and populates a node object with the service metadata in said native format; 
 one normalizer for each said application, wherein the normalizer transforms the node object containing the service metadata from the native format into a format for the canonical representation of service metadata and creates an artifact to contain the canonical representation, and wherein the format for the canonical representation of the service metadata is Service Component Architecture (SCA); and 
 a repository that stores the artifact; 
 wherein a synchronized dependency graph is constructed based on the service dependencies between the service interfaces; and 
 wherein the repository exposes an interface to retrieve the artifact associated with an application, wherein once the artifact is retrieved, a set of all dependent artifacts related to said artifact as indicated by the dependency graph are also retrieved, and wherein the interface exposed by the repository is Universal Description, Discovery, and Integration (UDDI). 
 
     
     
       5. The system of  claim 4 , wherein the normalizer makes normalized service metadata available as Java objects. 
     
     
       6. The system of  claim 4 , wherein the provider publishes the service metadata to a metadata repository. 
     
     
       7. The system of  claim 6 , wherein a chain of providers is processed sequentially. 
     
     
       8. The system of  claim 4 , wherein the format for canonical representation of service metadata is Service Component Architecture. 
     
     
       9. The system of  claim 4 , wherein a service consumer accesses the one or more backend systems to obtain the normalized service metadata. 
     
     
       10. A computer-readable storage medium containing instructions stored thereon, wherein the instructions, when executed by one or more processors, cause the one or more processors to perform the steps of:
 inspecting a plurality of applications, each application providing at least one service having service metadata associated therewith, wherein said each application generates the service metadata in a native format, and wherein the service metadata includes at least a set of service interfaces and a set of service dependencies between said service interfaces; 
 providing a plurality of connectors for said plurality of applications, wherein each type of said application is associated with a different connector depending on said type of the application; 
 obtaining the service metadata from each of said plurality of applications by the set of connectors, wherein each connector populates a node object with the service metadata in said native format; 
 providing said node object from the connector to a normalizer; 
 normalizing the service metadata of said each application by the normalizer, wherein the normalizer converts the node object from the native format into the format for canonical representation of service metadata and creates an artifact to contain the canonical representation, and wherein the format for the canonical representation of the service metadata is Service Component Architecture (SCA); 
 storing the artifact into a repository; 
 constructing a synchronized dependency graph based on the service dependencies between the service interfaces, wherein the service dependencies are normalized; and 
 exposing, by said repository, an interface to retrieve the artifact associated with an application, wherein once the artifact is retrieved, a set of all dependent artifacts related to said artifact as indicated by the dependency graph are also retrieved, and wherein the interface exposed by the repository is Universal Description, Discovery, and Integration (UDDI). 
 
     
     
       11. The computer-readable storage medium of  claim 10 , wherein the service metadata includes: design-time metadata, deployment metadata, service interfaces, service dependencies, schemas, properties, relationships between services, service bindings, policies, and exposable implementation details. 
     
     
       12. The computer-readable storage medium of  claim 10 , wherein a service consumer accesses the one or more backend systems to obtain the normalized service metadata.