PROTOCOL FOR ENABLING DYNAMIC AND SCALABLE FEDERATION OF ENTERPRISE SERVICE BUSES

• US 20090070456A1
• Filed: 09/11/2007
• Published: 03/12/2009
• Est. Priority Date: 09/11/2007
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Rodriguez, Adolfo F., Callaway, Robert D., Brown, Kyle G., Robinson, Richard A., Viniotis, Ioannis
• Granted Patent: US 8,095,670 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

In a method and system for creating a federation of a plurality of enterprise service buses (ESBs), a plurality of ESB nodes provide connectivity to one or more services. According to a protocol, at least a portion of the ESB nodes transmit policy-based service advertisement messages to other ESB nodes, wherein the policy-based service advertisement messages include service state information. In response to receiving the policy-based service advertisement messages, each of the ESB nodes stores the service state information received from other ESB nodes in respective distributed registries to create a local view of routable service endpoints in the federation. Each of the ESB nodes then uses its respective distributed registry to make routing decisions when routing service requests.

Claims

1. A computer-implemented method for creating a federation of a plurality of enterprise service buses (ESB) nodes, each one of the ESB nodes providing connectivity to one or more services, the method comprising:

transmitting policy-based service advertisement messages from at least a portion of ESB nodes to other ESB nodes, wherein the policy-based service advertisement messages include service state information;

in response to receiving the policy-based service advertisement messages, storing by each of the ESB nodes, the service state information received from other ESB nodes in respective distributed registries to create a local view of routable service endpoints in the federation; and

using by each of the ESB nodes, the respective distributed registries to make routing decisions when routing service requests.

2. The method of claim 1 wherein the service advertisement messages sent from each one of the ESB nodes share the ESB node'"'"'s service state data from each of the ESB node'"'"'s respective distributed registries.

3. The method of claim 2 wherein an amount of service state data from the respective distributed service registries that is shared with the ESB nodes of the federation is configurable via policy, thereby providing policy-based service advertisement.

4. The method of claim 3 wherein the policy-based service advertisement is configured such that a first set of services are only exposed to certain ESB nodes in the federation, and that advertisement of a second set of services are one of allowed and disallowed.

5. The method of claim 4 wherein configuration of the policy-based service advertisement messages determine an overall topology of the ESB federation and peer relationships of the ESB nodes therein.

6. The method of claim 1 further comprising providing the policy-based service advertisement messages with a first message type that is used to at least one of establish a connection between the ESB nodes in the ESB federation and to detect if a particular one of the ESB nodes is currently reachable or not so that the distributed registries can be updated.

7. The method of claim 6 further comprising providing the policy-based service advertisement messages with a second message type that is used as an acknowledgement of the first message type, and to share a sender'"'"'s current view of a topology of the ESB federation with a receiver.

8. The method of claim 7 further comprising providing the policy-based service advertisement messages with a third message type that is sent to a particular one of the ESB nodes if another one of the ESB nodes requests information about a particular one of the services.

9. The method of claim 8 further comprising providing the policy-based service advertisement messages with a fourth message type that is sent for at least one of as a response to the third message type with relevant information about the requested service, and to send updates to service metadata to the ESB nodes in the ESB federation.

10. An enterprise service bus federation system comprising:

a plurality of enterprise service bus (ESB) deployments, each of the ESB deployments comprising;

one or more ESB nodes, each providing connectivity to one or more services, including routing messages among the services; and

a respective distributed registry maintained by each of the ESB nodes; and

a protocol used by the ESB nodes, wherein according to the protocol, at least a portion of the ESB nodes function to;

transmit policy-based service advertisement messages to other ESB nodes, wherein the policy-based service advertisement messages include service state information;

in response to receiving the policy-based service advertisement messages, store the service state information received from other ESB nodes in the respective distributed registries to create a local view of routable service endpoints in the federation; and

use the respective distributed registries to make message routing decisions when routing service requests.

11. The system of claim 10 wherein the service advertisement messages sent from each one of the ESB nodes share the ESB node'"'"'s service state data from each of the ESB node'"'"'s respective distributed registries.

12. The system of claim 11 wherein an amount of service state data from the respective distributed service registries that is shared with each ESB node of the federation is configurable via policy, thereby providing policy-based service advertisement.

13. The system of claim 12 wherein the policy-based service advertisement is configured such that a first set of services are only exposed to certain ESB nodes in the federation, and that advertisement of a second set of services are one of allowed and disallowed.

14. The system of claim 13 wherein configuration of the policy-based service advertisement messages determine an overall topology of the ESB federation and peer relationships of the ESB nodes therein.

15. The system of claim 10 wherein the policy-based service advertisement messages include a first message type that is used to at least one of establish a connection between the ESB nodes in the ESB federation and to detect if a particular one of the ESB nodes is currently reachable or not so that the distributed registries can be updated.

16. The system of claim 15 wherein the policy-based service advertisement messages include a second message type that is used as an acknowledgement of the first message type, and to share a sender'"'"'s current view of a topology of the ESB federation with a receiver.

17. The system of claim 16 wherein the policy-based service advertisement messages include a third message type that is sent to a particular one of the ESB nodes if another one of the ESB nodes requests information about a particular one of the services.

18. The system of claim 17 wherein the policy-based service advertisement messages include a fourth message type that is sent for at least one of as a response to the third message type with relevant information about the requested service, and to send updates to service metadata to the ESB nodes in the ESB federation.

19. A method for using a distributed service registry for routing and forwarding service requests within an enterprise service buses (ESB) federation comprising at least two ESB deployments, wherein each of the ESB deployments further comprise one or more ESB nodes, the method comprising:

in response to a first ESB node in a first ESB deployment receiving a service request, passing the service request to a routing mediation procedure within the first ESB node;

performing by the routing mediation a table lookup of a distributed service registry to find matching services available in the first ESB federation and to determine a destination of where to send the service request;

determining by the routing mediation whether the destination for the service request exist within the ESB federation;

if it is determined that a destination for the service request does not exist within the ESB federation, then discarding the service request as not being serviceable within the federation;

determining by the routing mediation if the destination for the service request exists that is local to the first ESB deployment such that there is a second ESB node reachable in the first ESB deployment appropriate for handling the service request;

if the routing mediation determines that the destination for the service request is local to the first ESB deployment, then forwarding the service request to the second ESB node within the first ESB deployment, processing the service request by the second ESB node, and forwarding the service request onto the requested service;

if the routing mediation determines that the destination for the service request exists in the ESB federation, but that the destination is not local to the first ESB deployment, then forwarding the service request to a second ESB deployment, and then forwarding the service request onto an appropriate ESB node that provides connectivity for the particular service being requested.

20. An executable software product stored on a computer-readable medium containing program instructions for creating a federation of a plurality of enterprise service buses (ESB) nodes, each one of the ESB nodes providing connectivity to one or more services, the program instructions for:

transmitting policy-based service advertisement messages from at least a portion of ESB nodes to other ESB nodes, wherein the policy-based service advertisement messages include service state information;

in response to receiving the policy-based service advertisement messages, storing by each of the ESB nodes, the service state information received from other ESB nodes in respective distributed registries to create a local view of routable service endpoints in the federation; and

using by each of the ESB nodes, the respective distributed registries to make routing decisions when routing messages.