System and method for orchestrating composite web services in constrained data flow environments

• US 20060106748A1
• Filed: 11/12/2004
• Published: 05/18/2006
• Est. Priority Date: 11/12/2004
• Status: Active Grant

• Current Assignee: International Business Machines Corporation, ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Mann, Vijay, Chandra, Sunil, Chafle, Girish B., Ghosal, Sugata, Nanda, Mangala G.
• Granted Patent: US 7,606,832 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A technique for orchestrating composite web services in a constrained data flow environment. Data flow constraints represent the restrictions which the domains involved in composition might want to impose on access to the data they provide or the source from which they can accept data. The data flow constraints are overcome by breaking down an input composite web service specification into topologies (a topology is a set of partitions communicatively connected with one another at runtime). The system applies a rule-based filtering mechanism to choose a topology that does not violate any data flow constraints. Each of the partitions belonging to the chosen topology is executed within the same domain as the corresponding web service it invokes, thus having the same access rights as the corresponding web service. The composite web service is orchestrated in a decentralized fashion using these partitions, thereby ensuring that no data flow constraints are violated.

Claims

1. A system for orchestrating composite web services in a constrained data flow environment, said system comprising:

a build time module comprising logic circuitry adapted to;

receive a composite web service specification;

partition said composite web service specification into multiple topologies, wherein each topology comprises a set of composite web service partitions that are communicatively connected with each other at runtime, and wherein each composite web service partition comprises a functionally complete composite web service; and

select a topology for deployment;

at least one runtime module comprising logic circuitry adapted to verify and deploy partitions of the selected topology within a corresponding component web service domain.

2. The system of claim 1, wherein said build time module comprises a topology filter comprising a rule-based filtering mechanism adapted to select said topology that adheres to all data flow constraints provided by component web service domains.

3. The system of claim 2, wherein said data flow constraints are expressed as rules specified in terms of a 3-tuple group of a source of said data, a destination of said data, and a message type and are represented by an eXtensible Markup Language (XML) representation.

4. The system of claim 2, wherein said build time module comprises a constraint reinforcer adapted to ensure that said data flow constraints are applied to any new message type generated as a result of data transformations being applied to a message type that is part of an original data flow constraint.

5. The system of claim 1, wherein said build time module comprises a deployment manager adapted to send said web service partitions to multiple runtime modules residing at said component web service domains.

6. The system of claim 2, wherein said runtime module comprises a runtime constraint reinforcer adapted to generate an additional set of constraints based on said composite web service partitions received in said runtime modules and data flow constraints of a corresponding component web service domain.

7. The system of claim 2, wherein said runtime module comprises a partition deployer adapted to verify that said composite web service partitions adhere to said data flow constraints of a receiving component web service domain.

8. A method of orchestrating composite web services in a constrained data flow environment, said method comprising:

inputting a composite web service specification into a build time module;

partitioning said composite web service specification into multiple topologies, wherein each topology comprises a set of composite web service partitions that are communicatively connected with each other at runtime, and wherein each composite web service partition comprises a functionally complete composite web service;

selecting a topology for deployment using a rule-based filtering mechanism; and

deploying partitions of the selected topology within a corresponding component web service domain.

9. The method of claim 8, wherein said rule-based filtering mechanism selects a topology that adheres to all data flow constraints provided by component web service domains.

10. The method of claim 9, wherein said data flow constraints are expressed as rules specified in terms of a 3-tuple group of a source of said data, a destination of said data, and a message type and are represented by an eXtensible Markup Language (XML) representation.

11. The method of claim 9, further comprising that said data flow constraints are applied to any new message type generated as a result of data transformations being applied to a message type that is part of an original data flow constraint.

12. The method of claim 9, further comprising sending said composite web service partitions to multiple runtime modules residing at said component web service domain.

13. The method of claim 12, further comprising generating an additional set of constraints based on said composite web service partitions received in said runtime modules and the data flow constraints provided by a receiving component web service domain.

14. The method of claim 9, further comprising verifying that said composite web service partitions adhere to said data flow constraints of a receiving component web service domain.

15. A program storage device readable by computer, tangibly embodying a program of instructions executable by said computer to perform a method of orchestrating composite web services in a constrained data flow environment, said method comprising:

inputting a composite web service specification into a build time module;

partitioning said composite web service specification into multiple topologies, wherein each topology comprises a set of composite web service partitions that are communicatively connected with each other at runtime, and wherein each composite web service partition comprises a functionally complete composite web service;

selecting a topology for deployment using a rule-based filtering mechanism; and

deploying partitions of the selected topology within a corresponding component web service domain.

16. The program storage device of claim 15, wherein said rule-based filtering mechanism selects a topology that adheres to all data flow constraints provided by component web service domains.

17. The program storage device of claim 16, wherein said data flow constraints are expressed as rules specified in terms of a 3-tuple group of a source of said data, a destination of said data, and a message type and are represented by an extensible Markup Language (XML) representation.

18. The program storage device of claim 16, wherein said method further comprises assuring that said data flow constraints are applied to any new message type generated as a result of data transformations being applied to a message type that is part of an original data flow constraint.

19. The program storage device of claim 16, wherein said method further comprises sending said composite web service partitions to multiple runtime modules residing at said component web service domain.

20. The program storage device of claim 19, wherein said method further comprises generating an additional set of constraints based on said composite web service partitions received in said runtime modules and the data flow constraints provided by a receiving component web service domain.

21. The program storage device of claim 16, wherein said method further comprises verifying that said composite web service partitions adhere to said data flow constraints of a receiving component web service domain.

22. A service for orchestrating composite web services in a constrained data flow environment, said service:

inputting a composite web service specification into a build time module;

partitioning said composite web service specification into multiple topologies, wherein each topology comprises a set of composite web service partitions that are communicatively connected with each other at runtime, and wherein each composite web service partition comprises a functionally complete composite web service;

selecting a topology for deployment using a rule-based filtering mechanism; and

deploying partitions of the selected topology within a corresponding component web service domain.

23. The service of claim 22, wherein said rule-based filtering mechanism selects a topology that adheres to all data flow constraints provided by component web service domains.

24. The service of claim 23, wherein said data flow constraints are expressed as rules specified in terms of a 3-tuple group of a source of said data, a destination of said data, and a message type and are represented by an eXtensible Markup Language (XML) representation.

25. The service of claim 23, further comprising ensuring that said data flow constraints are applied to any new message type generated as a result of data transformations being applied to a message type that is part of an original data flow constraint.

26. The service of claim 23, further comprising sending said composite web service partitions to multiple runtime modules residing at said component web service domain.

27. The service of claim 26, further comprising generating an additional set of constraints based on said composite web service partitions received in said runtime modules and the data flow constraints provided by a receiving component web service domain.

28. The service of claim 23, further comprising verifying that said composite web service partitions adhere to said data flow constraints of a receiving component web service domain.

29. A system for orchestrating composite web services in a constrained data flow environment, said system comprising:

means for inputting a composite web service specification into a build time module;

means for partitioning said composite web service specification into multiple topologies, wherein each topology comprises a set of composite web service partitions that are communicatively connected with each other at runtime, and wherein each composite web service partition comprises a functionally complete composite web service;

means for selecting a topology for deployment using a rule-based filtering mechanism; and

means for deploying partitions of the selected topology within a corresponding component web service domain.