Automatic failover of nodes of a middle-tier layer

• US 9,246,754 B2
• Filed: 12/03/2013
• Issued: 01/26/2016
• Est. Priority Date: 12/06/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jones, Robert C., Mandelli, Manuela, Wilson, Russell
• Primary Examiner(s): Iqbal, Nadeem
• Application Number:
  US14/094,824
• Publication Number:
  US 20140164818A1
• Time in Patent Office: 784 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2458 Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Method and system are provided for automatic failover between multiple nodes in a middle-tier layer between client applications and a back-end service. The method at a first node includes: receiving a request from a client application; determining that the first node cannot service the request successfully; forwarding the request from the first node to a second peer node; receiving a response at the first node on completion of the request by the second peer node; and forwarding the response from the first node to the client application. An original path of communication between the client application and the first node is maintained. The failover of the request from the first node to the second peer node is transparent to the client application. Nodes may be registered in a group, wherein a node in a group has awareness of other nodes in the group.

Claims

1. A method for automatic failover between multiple nodes in a middle-tier layer between client applications and a back-end service, comprising:

registering a middle-tier node operating as a first node in a group, wherein the first node has awareness of other nodes in the group;

receiving, at the first node, a request from a client application;

determining that the first node cannot service the request successfully;

forwarding the request from the first node to a second peer node registered in a same group as the first node;

receiving a response at the first node on completion of the request by the second peer node;

forwarding the response from the first node to the client application;

the first node requesting a peer node from a group registry of available peer nodes; and

the group registry selecting a peer node from available peer nodes based on a selection criteria;

wherein an original path of communication between the client application and the first node is maintained;

wherein failover of the request from the first node to the second peer node is transparent to the client application; and

wherein registering the node in the group includes;

registering the node'"'"'s availability and access details.

2. The method as claimed in claim 1, further comprising:

establishing dedicated connections between peer nodes in the group utilizing optimized links where available.

3. The method as claimed in claim 2, wherein establishing a connection is carried out on a lazy basis when first needed.

4. The method as claimed in claim 1, further comprising:

the first node obtaining details of a peer node from a group registry of available peer nodes.

5. The method as claimed in claim 4, wherein the first node selects a peer node based upon an availability of dedicated connections.

6. The method as claimed in claim 1, wherein forwarding the request from the first node to the second peer node includes forwarding information in a correct form required to call the back-end service.

7. The method as claimed in claim 1, further comprising:

receiving, by a second peer node, a forwarded response from the first node;

carrying out a service request at a back-end service; and

responding to the first node with an outcome of the request.

8. The method as claimed in claim 7, wherein the second peer node carries out the service request at a different back-end service resource than a back-end service resource that the first node attempted to use.

9. The method as claimed in claim 1, wherein the middle-tier layer is a transaction gateway between client applications and multiple transaction servers.

18. A computer program product for automatic failover between multiple nodes in a middle-tier layer between client applications and a back-end service, the computer program product comprising:

a non-transitory computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method according to claim 1.

19. A computer program stored on a non-transitory computer readable medium and loadable into an internal memory of a digital computer, comprising software code portions, when said program is run on a computer, for performing the method of claim 1.

10. A system for automatic failover between multiple nodes in a middle-tier layer between client applications and a back-end service, comprising:

a middle-tier layer having multiple nodes registered in groups; and

a registry mechanism configured to register a node in a group, wherein the node has awareness of other nodes in the group and for registering the node'"'"'s availability and access details;

wherein a failover mechanism is provided to forward a request received at a first node from a client application to a second peer node registered in a same group as the first node;

wherein an original path of communication between the client application and the first node is maintained;

wherein failover of the request from the first node to the second peer node is transparent to the client application;

wherein a middle-tier node operating as the first node comprises;

a client request receiving component configured to;

receive the request from the client application;

a request servicing failure component configured to;

determine that the first node cannot service the request successfully; and

a first peer node forwarding component configured to;

forward the request from the first node to the second peer node;

receive a response at the first node on completion of the request by the second peer node; and

forward the response from the first node to the client application; and

wherein the registry mechanism is configured to receive a request for a peer node from a first node and for selecting another peer node from available peer nodes based on a selection criteria.

11. The system as claimed in claim 10, wherein the middle-tier node can perform a role of the first node or the second peer node.

12. The system as claimed in claim 10, wherein the registry mechanism includes a peer connection establishing component configured to establish dedicated connections between peer nodes in the group utilizing optimized links where available.

13. The system as claimed in claim 10, wherein the first node is configured to obtain details of a peer node from the registry mechanism.

14. The system as claimed in claim 12, wherein the peer connection establishing component selects a peer node based upon an availability of dedicated connections.

15. The system as claimed in claim 10, wherein a middle-tier node includes a peer node request receiving component that is configured to:

receive a forwarded response from the first node;

carry out a service request at a back-end service; and

respond to the first node with an outcome of the request.

16. The system as claimed in claim 15, wherein the second peer node carries out the service request at a different back-end service resource than a back-end service resource that the first node attempted to use.

17. The system as claimed in claim 10, wherein the middle-tier layer is a transaction gateway between client applications and multiple transaction servers.