Declarative Service Domain Federation

• US 20160323155A1
• Filed: 07/08/2016
• Published: 11/03/2016
• Est. Priority Date: 03/11/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bauer, Daniel, Butler, Nicholas D., Chen, Han, Dragicevic, Kristijan, Garces-Erice, Luis, Gershinsky, Gidon, Kim, Minkyong, Lei, Hui, Rushall, David, Schmidt, Marc-Thomas H., Shagin, Konstantin, Yang, Hao, Zeng, Liangzhao
• Granted Patent: US 10,581,701 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

A mechanism for declarative service domain federation uses a declarative approach to both the visibility aspect and the management aspect of service domain federation. Instead of manually exporting services, that is, selecting individual services from source domains to be visible in the target domain, using the present system, a federation architect uses a federation console to specify federation intent. The federation intent may include federation rule, query-based service group, and quality-of-service (QoS) policy. Based on the declared federation intent, a planning engine resolves the individual services based on the group query, generates the service visibility configuration, and creates the necessary service proxies and/or mediation objects to satisfy the goal. At runtime, a service monitor collects the performance metrics of federated services and dynamically adjusts the mediation/proxy configurations to maintain the QoS objectives specified by the federation architect.

Claims

1. A method, in a distributed service-oriented data processing system, for declarative service domain federation, the method comprising:

receiving, in a planning engine executing on a processor of a federation server within the service-oriented data processing system, a federation intent declaration comprising a federation rule, a quality-of-service policy, and a service group definition;

automatically identifying, by the planning engine, a set of services based on the service group definition;

automatically generating, by the planning engine, a service visibility configuration and one or more service proxies based on the federation rule arid the quality-of-service policy, wherein the visibility configuration enables service consumers to interact with service providers residing in different service domains and wherein the one or more service proxies enable a service consumer in a first service domain within a plurality of service domains to access a service in a second service domain within the plurality of service domains;

automatically deploying, by the planning engine, the visibility configuration to the plurality of service domains comprising the identified set of services; and

automatically deploying, by the planning engine, the one or more service proxies to execute within connectivity middleware of executing on at least one processor the plurality of service domains within the service-oriented data processing system.

2. The method of claim 1, wherein identifying the set of services comprises:

querying service registries of the plurality of domains based on the service group definition.

3. The method of claim 1, wherein the service group definition is stored in a service group definition language.

4. The method of claim 1, wherein the service group definition specifies a service group by at feast one of explicit enumeration, a query against a set of service properties, or a union or intersection of a plurality of other service groups.

5. The method of claim 4, wherein the set of service properties includes at least one of syntactic properties, semantic properties, or quality-of-service attributes.

6. The method of claim 1, wherein deploying the visibility configuration comprises generating entries in service registries of the plurality of service domains based on the service group definition.

7. The method of claim 1, wherein the federation rule is stored in a connectivity federation description language.

8. The method of claim 1, wherein the federation rule specifies a verb, a subject, an object, and an adverb, wherein the verb specifies an action, wherein the subject specifies a set of services, wherein the object specifies a set of service domains, and wherein the adverb specifies how the federation is to be carried out.

9. The method of claim 1, wherein the quality-of-service policy is stored in a Web services performance language that is compatible with an existing Web services policy framework.

10. The method of claim 1, wherein the quality-of-service policy describes quality-of-services capabilities by specifying service performance measurements collected by a runtime service monitoring engine and populated in a service registry of at least one service domain.

11. The method of claim 1, wherein the quality-of-service policy describes quality-of-service requirements that specify a set of service level assurance or optimization objectives.

24. The method of claim 1, further comprising:

collecting, by a service monitor, performance metrics of federated services at runtime; and

dynamically adjusting the one or more service proxies to maintain quality-of-service objectives specified in the quality-of-service policy.

12. A computer program product comprising a non-transitory computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a processor of a federation server within a service-oriented data processing system, causes the federation server to:

receive, in a planning engine executing on the processor of the federation server within a service-oriented data processing system, a federation intent declaration comprising a federation rule, a quality-of-service policy, and a service group definition;

automatically identify, by the planning engine, a set of services based on the service group definition;

automatically generate, by the planning engine, a service visibility configuration and one or more service proxies based on the federation rule and the quality-of-service policy, wherein the visibility configuration enables service consumers to interact with service providers residing in different service domains and wherein the one or more service proxies enable a service consumer in a first service domain within a plurality of service domains to access a service in a second service domain within the plurality of service domains;

automatically deploy, by the planning engine, the visibility configuration to the plurality of service domains comprising the identified set of services; and

automatically deploy, by the planning engine, the one or more service proxies to execute within connectivity middleware executing on at least one processor of the plurality of service domains within the service-oriented data processing system.

13. The computer program product of claim 12, wherein the service group definition specifies a service group by at least one of explicit enumeration, a query against a set of service properties, or a union or intersection of a plurality of other service groups.

14. The computer program product of claim 12, wherein the federation rule specifies a verb, a subject, an object, and an adverb, wherein the verb specifies an action, wherein the subject specifies a set of services, wherein the object specifies a set of service domains, and wherein the adverb specifies how the federation is to be carried out.

15. The computer program product of claim 12, wherein the quality-of-service policy describes quality-of-services capabilities by specifying service performance measurements collected by a runtime service monitoring engine and populated in a service registry of at least one service domain.

16. The compute program product of claim 12, wherein the quality-of-service policy describes quality-of-service requirements that specify a set of service level assurance or optimization objectives.

25. The computer program product of claim 12, wherein the computer readable program further causes the computing device to:

collect, by a service monitor, performance metrics of federated services at runtime; and

dynamically adjust the one or more service proxies to maintain quality-of-service objectives specified in the quality-of-service policy.

26. The computer program product of claim 12, wherein identifying the set of services comprises:

querying service registries of the plurality of domains based on the service group definition.

27. The computer program product of claim 12, wherein the service group definition is stored in a service group description language, wherein the federation rule is stored in a connectivity federation description language, and wherein the quality-of-service policy is stored in a Web services performance language that is compatible with an existing Web services policy framework.

17. (canceled)

18. (canceled)

19. A federation server within a service-oriented data processing system, comprising:

a processor; and

a memory coupled to the processors wherein the memory comprises a planning engine comprising instructions which, when executed by the processor, cause the processor to;

receive, in a planning engine executing on the processor of the federation server within a service-oriented data processing system, a federation intent declaration comprising a federation rule, a quality-of-service policy, and a service group definition;

automatically, identify, by planning engine, a set of services based on the service group definition;

automatically generate, by the planning engine, a service visibility configuration and one or more service proxies based on the federation rule and the quality-of-service policy, wherein the visibility configuration enables service consumers to interact with service providers residing in different service domains and wherein the one or more service proxies enable a service consumer in a first service domain within a plurality of service domains to access a service in a second service domain within the plurality of service domains;

automatically deploy, by the planning engine, the visibility configuration to the plurality of service domains comprising the identified set of services; and

automatically deploy, by the planning engine, the one or more service proxies to execute within, connectivity middleware executing on at least one processor of the plurality of service domains within the service-oriented data processing system.

20. The federation server of claim 19, wherein the service group definition specifies a service group by at least one of explicit enumeration, a query against, a set of service properties, or a union or intersection of a plurality of other service groups.

21. The federation server of claim 19, wherein the federation rule specifies a verb, a subject, an object, and an adverb, wherein the verb specifies an action, wherein the subject specifies a set of services, wherein the object specifies a set of service domains, and wherein, the adverb specifies how the federation is to be carried out.

22. The federation server of claim 19, wherein the quality-of-service policy describes quality-of-services capabilities by specifying service performance measurements collected by a runtime service monitoring engine and populated in a service registry of at least one service domain.

23. The federation server of claim 19, wherein the quality-of-service policy describes quality-of-service requirements that specify a set of service level assurance or optimization objectives.

28. The federation server of claim 19, wherein the instructions further cause the processor to:

collect, by a service monitor, performance metrics of federated services at runtime; and

dynamically adjust the one or more service proxies to maintain quality-of-service objectives specified in the quality-of-service policy.

29. The federation server of claim 19, wherein identifying the set of services comprises:

querying service registries of the plurality of domains based on the service group definition.

30. The federation server of claim 19, wherein the service group definition is stored in a service group description language, wherein the federation rule is stored in a connectivity federation description language, and wherein the quality-of-service policy is stored in a Web services performance language that is compatible with an existing Web services policy framework.