# US 2009/0024561 A1 · System and method for synchronizing service metadata

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0024561 A1
- Document ID: US20090024561A1
- Status: Published application
- Kind: A1
- Application number: 12/032,546
- Filed: 2008-02-15
- Published: 2009-01-22
- Earliest claimed: 2007-07-17
- Assignees: BEA Systems, Inc.
- Inventors: Muthukumar S. Palanisamy
- Web page: https://patentgrep.com/patent/US20090024561A1

## CPC

- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F 16/178: Techniques for file synchronisation in file systems
- H04L 67/567: Integrating service provisioning from a plurality of service providers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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.

## Claims

### Claim 1

A method for synchronizing service metadata into a format for canonical representation of service metadata, comprising:
receiving service metadata at a connector 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.

### Claim 2 (depends on 1)

The method of claim 1, wherein the standard format for the canonical representation of service metadata is Service Component Architecture (SCA).

### Claim 3 (depends on 1)

The method of claim 1, wherein the standard protocol to search the metadata repository is Universal Description, Discovery, and Integration (UDDI).

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 1)

The method of claim 1, wherein a service consumer accesses the metadata repository to obtain the normalized service metadata.

### Claim 6

A system to synchronize service metadata into a format for canonical representation of service metadata, comprising:
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.

### Claim 7 (depends on 6)

The system of claim 6 wherein the service metadata is stored into a metadata repository that supports the format for canonical representation of service metadata.

### Claim 8 (depends on 6)

The system of claim 6, wherein the metadata repository supports UDDI.

### Claim 9 (depends on 6)

The system of claim 6, wherein the normalizer makes normalized service metadata available as Java objects.

### Claim 10 (depends on 6)

The system of claim 6, wherein the provider publishes the service metadata to a metadata repository.

### Claim 11 (depends on 10)

The system of claim 10, wherein a chain of providers is processed sequentially.

### Claim 12 (depends on 6)

The system of claim 6, wherein the format for canonical representation of service metadata is Service Component Architecture.

### Claim 13 (depends on 6)

The system of claim 6, wherein a service consumer accesses the metadata repository to obtain the normalized service metadata.

### Claim 14

A computer-readable medium containing instructions stored thereon, wherein the instructions comprise:
receiving service metadata from a service producer;
normalizing the service metadata into the format for canonical representation of service metadata; and
storing normalized service metadata into a metadata repository that supports the format for canonical representation of service metadata.

### Claim 15 (depends on 14)

The computer-readable medium of claim 14, wherein the standard format for the canonical representation of service metadata is Service Component Architecture (SCA).

### Claim 16 (depends on 14)

The computer-readable medium of claim 14, wherein the standard protocol to search the metadata repository is Universal Description, Discovery, and Integration (UDDI).

### Claim 17 (depends on 14)

The computer-readable medium of claim 14, 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.

### Claim 18 (depends on 14)

The computer-readable medium of claim 14, wherein a service consumer accesses the metadata repository to obtain the normalized service metadata.
