Abstract: Described herein is a system and method for automating asset workflows in a service metadata repository. A service metadata repository includes an event model for generating one or more events based on a change to one or more assets. A persistent message stores the one or more events. A subscription service provides the ability to subscribe to one or more events and register one or more subscribed web service endpoints where the one or more events will be delivered. A delivery service matches the one or more events to the one or more web service endpoint and delivers the one or more events to a notification service. A notification service notifies the one or more subscribed web service endpoints of the one or more events. One or more workflows automate asset registration based on rules configured in an XML file, wherein the one or more workflows are initiated upon receiving the one or more events at a subscribed web service endpoint.

Abstract: Business Process Execution Language (BPEL) engines and Enterprise Service Buses (ESBs) often connect to adapters to integrate backend packaged applications with a process flow by invoking web services using Java Connector Architecture (JCA) and Simple Object Access Protocol (SOAP) bindings. The Web Service Description Language (WSDL) files for the web services that interact with the adapters can be introspected to harvest adapter integration and transformation information into a service metadata repository. This permits dependency and impact analysis to extend from services to adapters and transformations.

Abstract: A method is provided for creating a Universally Unique Identifier (UUID) for a web service. The UUID is stored in service metadata associated with the web service. The UUID can then be used to track services and correlate service information between multiple systems. In accordance with an embodiment, a method is provided for publishing Universal Description Discovery and Integration (UDDI) service information from a metadata repository to a service registry. In accordance with an embodiment, a method is provided for receiving Universal Description Discovery and Integration (UDDI) service information from a service registry into a metadata repository.

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.

Abstract: A method is provided for creating a Universally Unique Identifier (UUID) for a web service. The UUID is stored in service metadata associated with the web service. The UUID can then be used to track services and correlate service information between multiple systems. In accordance with an embodiment, a method is provided for publishing Universal Description Discovery and Integration (UDDI) service information from a metadata repository to a service registry. In accordance with an embodiment, a method is provided for receiving Universal Description Discovery and Integration (UDDI) service information from a service registry into a metadata repository.

Abstract: Business Process Execution Language (BPEL) engines and Enterprise Service Buses (ESBs) often connect to adapters to integrate backend packaged applications with a process flow by invoking web services using Java Connector Architecture (JCA) and Simple Object Access Protocol (SOAP) bindings. The Web Service Description Language (WSDL) files for the web services that interact with the adapters can be introspected to harvest adapter integration and transformation information into a service metadata repository. This permits dependency and impact analysis to extend from services to adapters and transformations.

Abstract: Described herein is a system and method for automating asset workflows in a service metadata repository. A service metadata repository includes an event model for generating one or more events based on a change to one or more assets. A persistent message stores the one or more events. A subscription service provides the ability to subscribe to one or more events and register one or more subscribed web service endpoints where the one or more events will be delivered. A delivery service matches the one or more events to the one or more web service endpoint and delivers the one or more events to a notification service. A notification service notifies the one or more subscribed web service endpoints of the one or more events. One or more workflows automate asset registration based on rules configured in an XML file, wherein the one or more workflows are initiated upon receiving the one or more events at a subscribed web service endpoint.

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.