On-premise and off-premise communication

• US 10,348,516 B2
• Filed: 06/20/2016
• Issued: 07/09/2019
• Est. Priority Date: 03/09/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Coleman, Andrew, Golby-Kirk, Matthew E., Reeve, John A.
• Primary Examiner(s): Barot, Bharat
• Application Number:
  US15/186,968
• Publication Number:
  US 20170264460A1
• Time in Patent Office: 1,114 Days
• Field of Search: 709202-203, 709227-228
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment

Abstract

Proposed are concepts for managing communication between off-premise and on-premise servers. A flow execution request from an application of an off-premise server or an on-premise server is received and a requested flow is determined based on the received flow execution request. Stored endpoint data associated with the requested flow can then be identified. The flow execution request is then communicated to an on-premise server or off-premise server based on the identified endpoint data.

Claims

1. A connectivity component adapted to manage communication between an off-premise server at an off-premise location and an on-premise server at an on-premise location, the connectivity component residing at the off-premise location and comprising:

an endpoint data store of the connectivity component, the endpoint data store adapted to store endpoint data associated with one or more flows;

a first communication component of the connectivity component, the first communication component adapted to receive a flow execution request from an application of an off-premise server or an on-premise server;

a routing component of the connectivity component, the routing component adapted to determine a requested flow based on the received flow execution request and to identify stored endpoint data associated with the requested flow; and

a second communication component of the connectivity component, the second communication component adapted to communicate the flow execution request to an on-premise server or off-premise server based on the identified endpoint data.

2. The connectivity component of claim 1, wherein the first communication component is adapted to establish a first secure tunnel between the first communication component and a server hosting the application for receiving the flow execution request;

and wherein the second communication component is adapted to establish a second secure tunnel, different from the first secure tunnel, between the second communication component and an agent of the on-premise server or off-premise server for communicating the flow execution request.

3. The connectivity component of claim 1, wherein the off-premise server further comprises a cloud server;

and wherein the application is provided as a service of the cloud server.

4. The connectivity component of claim 1, further comprising:

a registration module of the connectivity component, the registration module adapted to receive end-point data from at least one selected from the group consisting of an application of an off-premise server, an application of an on-premise server, an off-premise server module, and an on-premise server module; and

wherein the registration module is adapted to store received endpoint data in the endpoint data store.

5. The connectivity component of claim 4, wherein the registration module is adapted to remove endpoint data from the endpoint data store in response to at least one selected from the group consisting of an application, a server, and a flow becoming inaccessible.

6. The connectivity component of claim 4, wherein the endpoint data further comprises at least one selected from the group consisting of a flow name, a server identification, a server address, a flow version identifier, and checksum information.

7. The connectivity component of claim 1, wherein the flow execution request further comprises at least one selected from the group consisting of a flow name, a data payload, and entry point data.

8. The connectivity component of claim 1, wherein the first communication component is adapted to receive the flow execution request from the off-premise server;

and wherein the second communication component is adapted to communicate the flow execution request to the on-premise server based on the identified endpoint data.

9. The connectivity component of claim 1, wherein the first communication component is adapted to receive the flow execution request from the on-premise server;

and wherein the second communication component is adapted to communicate the flow execution request to the off-premise server based on the identified endpoint data.

10. The connectivity component of claim 1, wherein the second communication component is adapted to receive a response to the communicated flow execution request;

and wherein the first communication component is adapted to communicate the received response to the application.

11. The connectivity component of claim 1, further comprising a switch module.

12. A computer-implemented method of managing communication between an off-premise server at an off-premise location and an on-premise server at an on-premise location, the method comprising:

storing, in an endpoint data store, by a connectivity component residing at the off-premise location, endpoint data associated with one or more flows;

receiving, by the connectivity component residing at the off-premise location, a flow execution request from an application of an off-premise server or an on-premise server;

determining, by the connectivity component residing at the off-premise location, a requested flow based on the received flow execution request;

identifying, by the connectivity component residing at the off-premise location, stored endpoint data associated with the requested flow; and

communicating, by the connectivity component residing at the off-premise location, the flow execution request to an on-premise server or off-premise server based on the identified endpoint data.

13. The computer-implemented method of claim 12, wherein the receiving the flow execution request further comprises:

establishing a first secure tunnel between a first communication component of the connectivity component and a server hosting the application, the first communication component performing the receiving the flow execution request, and the first secure tunnel for receiving the flow execution request; and

wherein the communicating the flow execution request further comprises establishing a second secure tunnel, different from the first secure tunnel, between a second communication component of the connectivity component and an agent of the on-premise or off-premise server, and the second secure tunnel for communicating the flow execution request.

14. The computer-implemented method of claim 12, further comprising:

receiving, by a registration module of the connectivity component, end-point data from at least one selected from the group consisting of an application of an off-premise server, an application of an on-premise server, an off-premise server module, and an on-premise server module; and

storing, by the registration module, received endpoint data in the endpoint data store.

15. The method of claim 14, further comprising removing, by the registration module, endpoint data from the endpoint data store in response to at least one selected from the group consisting of an application, a server, and a flow becoming inaccessible.

16. The computer-implemented method of claim 12, wherein the receiving the flow execution request further comprises:

receiving the flow execution request from the off-premise server; and

wherein the communicating the flow execution request further comprises communicating the flow execution request to the on-premise server based on the identified endpoint data.

17. The computer-implemented method of claim 12, wherein receiving the flow execution request further comprises:

receiving the flow execution request from the on-premise server; and

wherein the communicating the flow execution request further comprises communicating the flow execution request to the off-premise server based on the identified endpoint data.

18. The computer-implemented method of claim 12, further comprising:

receiving, by a second communication component of the connectivity component, a response to the communicated flow execution request; and

communicating, by the second communication component, the received response to the application.

19. A computer program product for managing communication between an off-premise server at an off-premise location and an on-premise server at an on-premise location, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processing unit to cause the processing unit to perform a method comprising:

storing, in an endpoint data store, by a connectivity component residing at the off-premise location, endpoint data associated with one or more flows;

receiving, by the connectivity component residing at the off-premise location, a flow execution request from an application of an off-premise server or an on-premise server;

determining, by the connectivity component residing at the off-premise location, a requested flow based on the received flow execution request;

identifying, by the connectivity component residing at the off-premise location, stored endpoint data associated with the requested flow; and

communicating, by the connectivity component residing at the off-premise location, the flow execution request to an on-premise server or off-premise server based on the identified endpoint data.

20. The computer program product of claim 19, wherein the receiving the flow execution request further comprises:

establishing a first secure tunnel between a first communication component of the connectivity component and a server hosting the application, the first communication component performing the receiving the flow execution request, and the first secure tunnel for receiving the flow execution request; and

wherein the communicating the flow execution request further comprises establishing a second secure tunnel, different from the first secure tunnel, between a second communication component of the connectivity component and an agent of the on-premise or off-premise server, and the second secure tunnel for communicating the flow execution request.