Cloud-based mainframe integration system and method

• US 9,058,213 B2
• Filed: 09/28/2011
• Issued: 06/16/2015
• Est. Priority Date: 09/01/2011
• Status: Active Grant

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: Yaffe, Lior
• Primary Examiner(s): Gee, Jason K.
• Assistant Examiner(s): Ullah, Sharif E
• Application Number:
  US13/247,179
• Publication Number:
  US 20130060838A1
• Time in Patent Office: 1,357 Days
• Field of Search: 709/203, 380/255, 380/264, 380/276, 713/150, 713/163, 713/181, 726/2, 726/21, 726/36
• US Class Current: 1/1
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/53 using third party service providers

Abstract

The present technology concerns a cloud-based mainframe integration system for providing at least one client access to at least one mainframe, the at least one mainframe being accessible over a persistent communication connection. The cloud-based mainframe integration system comprises, at least one mainframe integration server, adapted for routing communications between the at least one client and the at least one mainframe. The at least one MIS is located within a cloud computing environment separate from a computer network in which the at least one mainframe is located. The at least one MIS also is adapted for communicating with the separate network over a non-persistent communication connection.

Claims

1. A cloud-based mainframe integration system for providing at least one client access to at least one mainframe, the at least one mainframe being accessible over a persistent communication connection, wherein the cloud-based mainframe integration system comprises:

at least one mainframe integration server (MIS), implemented using at least one information processing apparatus having at least one processor, and configured to route communications, via a cloud computing environment, between the at least one client and the at least one mainframe; and

a load balancer configured to communicate with each MIS instance,

wherein the at least one MIS is located within the cloud computing environment separate from a computer network in which the at least one mainframe is located,

wherein the cloud computing environment provides a dynamically allocated pool of virtual machines and a single domain URI entry point, each MIS instance publishing a unique URI enabling communication between MIS instances and enabling communication between each MIS instance and the single domain URI entry point,

wherein the at least one MIS is configured to communicate over the separate computer network, with the at least one mainframe, over a non-persistent communication connection, and

wherein the load balancer represented by the single domain URI entry point and routing requests to target MIS instances.

2. The cloud-based mainframe integration system of claim 1, further comprising at least one mainframe communication bridge located within the network of the at least one mainframe, the at least one MCB being configured to maintain a persistent communication connection with the at least one mainframe and further configured to communicate with the cloud computing environment over the non-persistent communication connection.

3. The cloud-based mainframe integration system of claim 1, wherein the at least one MIS is adapted for storing a session state relating to a request/response cycle of the communication between the at least one client and the at least one mainframe, the session state being usable for subsequent request/response cycles between the at least one client and the at least one mainframe.

4. The cloud-based mainframe integration system of claim 3, wherein the at least one MIS is configured to send the session state to the at least one MCB for storage at the at least one MCB.

5. The cloud-based mainframe integration system of claim 1, wherein the load balancer is configured to dispatch a communication coming from the network of the at least one mainframe to one of a plurality of MIS inside the cloud computing environment.

6. The cloud-based mainframe integration system of claim 5, wherein the MIS selected by the load balancer is configured to obtain a current session state relating to the communication from another MIS, if the selected MIS does not possess the current session state.

7. The cloud-based mainframe integration system of claim 5, wherein the MIS selected by the load balancer is configured to obtain a current session state relating to the communication from at least one MCB, if none of the other MIS possesses the current session state.

8. The cloud-based mainframe integration system of claim 1, wherein the at least one MIS is configured to send a connection identifier to the at least one client, the connection identifier identifying the MCB which handled the communication between the at least one client and the at least one mainframe.

9. The cloud-based mainframe integration system of claim 8, wherein the at least one MIS is configured to receive a client request comprising the connection identifier and further configured to determine whether it already established a connection to the at least one MCB identified by the connection identifier, and if not, redirecting the client request to the load balancer.

10. The cloud-based mainframe integration system of claim 9, wherein the at least one MIS adds its own identifier to the client request when redirecting the client request to the load balancer.

11. The cloud-based mainframe integration system of claim 2, wherein the at least one MCB is configured to communicate with the at least one MIS only via the load balancer, and wherein the at least one MCB is configured to send a plurality of registration requests to the load balancer in order to register with substantially all MIS.

16. The cloud-based mainframe integration system of claim 1, wherein the at least one MIS is configured to communicate with the at least one mainframe using at least one mainframe communication bridge, and communications between the MIS and the at least one mainframe communication bridge are conducted using a standard internet protocol where communications between the at least one mainframe communication bridge and the at least one mainframe are conducted using a mainframe protocol.

17. The cloud-based mainframe integration system of claim 16, wherein using the standard protocol for communications between the at least one MCB and the MIS replaces standard telnet connections between the MIS and the at least one mainframe with a request/response mode over standard IP communication.

18. The cloud-based mainframe integration system of claim 16, wherein the MIS communicates both inbound and outbound requests using only the standard internet protocol.

19. The cloud-based mainframe integration system of claim 1, wherein the single domain URI entry point is used by all clients and MCB instances to communicate with one or more MIS instances.

20. The cloud-based mainframe integration system of claim 1, wherein a number of one or more MIS instances running inside the cloud computing environment is adjustable based on workload demand.

12. A method for providing at least one client access to at least one mainframe, the at least one mainframe being accessible over a persistent communication connection, the method comprising:

routing, by at least one mainframe integration server (MIS), via a cloud computing environment, communications between the at least one client and the at least one mainframe; and

communicating with each MIS instance via a load balancer,

wherein the at least one MIS is located within the cloud computing environment separate from a computer network in which the at least one mainframe is located,

wherein the cloud computing environment provides a dynamically allocated pool of virtual machines and a single domain URI entry point, each MIS instance publishing a unique URI enabling communication between MIS instances and enabling communication between each MIS instance and the single domain URI entry point,

wherein the at least one MIS is configured to communicate over the separate computer network, with the at least one mainframe, over a non-persistent communication connection, and

wherein the load balancer represented by the single domain URI entry point and routing requests to target MIS instances.

13. The method of claim 12, further comprising:

storing, by the at least one MIS, a session state relating to a request/response cycle of the communication between the at least one client and the at least one mainframe, the session state being usable for subsequent request/response cycles between the at least one client and the at least one mainframe; and

/or

sending, by the at least one MIS, the session state to at least one mainframe communication bridge located within the network of the at least one mainframe for being stored at the at least one MCB.

14. The method of claim 12, further comprising:

sending, by the at least one MIS, a connection identifier to the at least one client, the connection identifier identifying the MCB which handled the communication between the at least one client and the at least one mainframe.

15. A non-transitory computer-readable storage medium tangibly storing a computer program comprising instructions for causing a computer of an information processing apparatus to perform functionality comprising:

routing, by at least one mainframe integration server (MIS), via cloud computing environment, communications between the at least one client and the at least one mainframe; and

communicating with each MIS instance via a load balancer,

wherein the at least one MIS is located within the cloud computing environment separate from a computer network in which the at least one mainframe is located,

wherein the cloud computing environment provides a dynamically allocated pool of virtual machines and a single domain URI entry point, each MIS instance publishing a unique URI enabling communication between MIS instances and enabling communication between each MIS instance and the single domain URI entry point,

wherein the at least one MIS is configured to communicate over the separate computer network, with the at least one mainframe, over a non-persistent communication connection, and

wherein the load balancer represented by the single domain URI entry point and routing requests to target MIS instances.