Mapping Of Metadata Between A Web Service And A Line-Of-Business System

• US 20100332529A1
• Filed: 06/24/2009
• Published: 12/30/2010
• Est. Priority Date: 06/24/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Doctor, Mustansir, Prasad, Anil, Nayak, Tapas K., Sampathkumar, Jayanthi
• Application Number:
  US12/490,518
• Publication Number:
  US 20100332529A1
• Time in Patent Office: Days
• US Class Current: 707/770
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Techniques are provided for interfacing clients with line of business (LOB) systems through a web service. An operation of the LOB system that the LOB system is configured to perform is selected. The selected operation is indicated in a metadata map. A first mapping is included in the metadata map of one or more LOB-side parameters of the operation to corresponding service-side parameters. A second mapping is included in the metadata map of one or more LOB-side types associated with the LOB-side parameters to corresponding service-side types. The metadata map may be serialized into a service contract. The service contract may be used by the web service to expose the LOB system to clients. The metadata map may be deserialized and used by the web service to map messages between the web service and LOB system.

Claims

1. A method for interfacing a web service with a line of business (LOB) system, comprising:

selecting an operation of the LOB system that the LOB system is configured to perform;

indicating the selected operation in a metadata map;

determining a plurality of LOB-side parameters associated with the selected operation;

including a first mapping of the plurality of LOB-side parameters to a plurality of service-side parameters in the metadata map;

determining a plurality of LOB-side types associated with the plurality of LOB-side parameters;

including a second mapping of the plurality of LOB-side types to a plurality of service-side types in the metadata map; and

serializing the metadata map.

2. The method of claim 1, wherein said indicating the selected operation in a metadata map comprises:

including a mapping in the metadata map of a first name referenced at the LOB system for the selected operation to a second name configured to be referenced at the web service for the selected operation.

3. The method of claim 1, wherein said including a first mapping of the plurality of LOB-side parameters to a plurality of service-side parameters in the metadata map comprises:

selecting a LOB-side parameter of the plurality of LOB-side parameters that is not to be exposed by the web service; and

removing a mapping of the selected LOB-side parameter to a service-side parameter from the first mapping.

4. The method of claim 1, wherein said including a first mapping of the plurality of LOB-side parameters to a plurality of service-side parameters in the metadata map comprises:

including in the first mapping a mapping of a first name referenced at the LOB system for a LOB-side parameter to a second name configured to be referenced at the web service for a service-side parameter that corresponds to the LOB-side parameter.

5. The method of claim 1, wherein said including a second mapping of the plurality of LOB-side types to a plurality of service-side types in the metadata map comprises:

including in the second mapping a mapping of a first name referenced at the LOB system for a LOB-side type to a second name configured to be referenced at the web service for a service-side type that corresponds to the LOB-side type.

6. The method of claim 1, wherein said including a second mapping of the plurality of LOB-side types to a plurality of service-side types in the metadata map comprises:

including in the second mapping a mapping of a first name referenced at the LOB system for a LOB-side type member to a second name configured to be referenced at the web service for a service-side type member that corresponds to the LOB-side type member.

7. The method of claim 1, wherein said serializing comprises:

serializing the metadata map into a service contract.

8. The method of claim 7, wherein said serializing comprises:

serializing an operation metadata, an operation parameter, a type metadata, and a type member into the service contract.

9. The method of claim 1, further comprising:

initializing the web service by at least deserializing the metadata map from a service contract.

10. The method of claim 9, wherein said initializing comprises:

deserializing an operation metadata, an operation parameter, a type metadata, and a type member from the service contract.

11. The method of claim 1, further comprising:

receiving a SOAP request message from a client regarding the operation;

mapping the SOAP request message to a LOB request message according to the generated metadata map;

transmitting the LOB request message to the LOB system;

receiving a LOB response message from the LOB system;

mapping the LOB response message to a SOAP response message according to the generated metadata map;

transmitting the SOAP response message to the client in response to the SOAP request message.

12. The method of claim 11, wherein said mapping the SOAP request message to a LOB request message according to the generated metadata map comprises:

mapping the SOAP request message to a LOB request message according to a deserialized version of the generated metadata map; and

wherein said mapping the LOB response message to a SOAP response message according to the generated metadata map comprises;

mapping the LOB response message to a SOAP response message according to the deserialized version of the generated metadata map.

13. A metadata map generator tool, comprising:

a metadata service configured to receive a request from a user to retrieve metadata for an operation from a line of business (LOB) system;

a metadata handler configured to provide an operation metadata request to the LOB system based on the request received from the user, and to receive operation metadata associated with the operation from the LOB system; and

a metadata analyzer configured to generate a metadata map based at least on the operation metadata, and to serialize the metadata map into a service contract.

14. The metadata map generator tool of claim 13, wherein the metadata service is configured to determine whether the operation metadata includes one or more parameters that reference a complex type;

the metadata handler being configured to provide a type metadata request associated with the complex type to the LOB system, and to receive type metadata associated with the complex type from the LOB system, if the complex type is determined to referenced; and

the metadata analyzer being configured to generate the metadata map based at least on the operation metadata and the type metadata.

15. The metadata map generator tool of claim 13, further comprising:

an interface module configured to generate an interface to enable the user to select the operation of the LOB system to generate a metadata map for the selected operation.

16. The metadata map generator tool of claim 13, further comprising:

an interface module configured to generate an interface to enable the user to modify the generated metadata map.

17. The metadata map generator tool of claim 16, wherein the interface is configured to enable the user to perform at least one of changing a service-side name of the operation, a service-side name of a parameter of the operation, a service-side name of a type associated with the parameter, or a service-side name of a type member associated with the type.

18. The metadata map generator tool of claim 16, wherein the interface is configured to enable the user to configure at least one of a parameter of the operation or a type member of a type associated with the parameter to not be exposed on the service-side.

20. A web service, comprising:

a web service module configured to expose an operation of a line of business (LOB) system at the web service according to a service contract, the service contract including a serialized metadata map that maps metadata associated with the operation between the web service and the LOB system;

a contract analyzer configured to deserialize the metadata map into an intermediate data structure form; and

an LOB adaptor configured to map metadata messages between the web service and the LOB system according to the deserialized metadata map.