ON-PREMISES AND OFF-PREMISES COMMUNICATION

• US 20180124153A1
• Filed: 11/01/2016
• Published: 05/03/2018
• Est. Priority Date: 11/01/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DOLBY, Trevor C., GOLBY-KIRK, Matthew E., REEVE, John A.
• Granted Patent: US 10,594,770 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Proposed are concepts for managing communication between off-premises and on-premises servers. A file system event request from an application of a first server (such as an off-premises server or an on-premises server) is received and a requested file system is determined based on the received file system event request. Stored file system path data associated with the requested file system can then be identified. The file system event request is then communicated to a second server (such as an on-premises server or off-premises server) based on the identified file system path data.

Claims

1. A computer system comprising:

a memory; and

a processor in communications with the memory, wherein the computer system is configured to perform a method, the method comprising;

storing, in a file system path data store, file system path data associated with one or more file systems;

receiving a file system event request from an application of a first server;

determining a requested file system based on the received file system event request;

identifying stored file system path data associated with the requested file system; and

communicating the file system event request to a second server based on the identified file system path data.

2. The computer system of claim 1, wherein the first server comprises an off-premises server and the second server comprises an on-premises server, or the first server comprises an on-premises server and the second server comprises an off-premises server.

3. The computer system claim 1, wherein the first server comprises an off-premises cloud server, and wherein the application is provided as a service of the off-premises cloud server.

4. The computer system of claim 1, wherein the method further includes receiving file system path data from at least one selected from the group consisting of:

an application of an off-premises server, an application of an on-premises server, an off-premises server module, and an on-premises server module, and wherein a registration module is adapted to store received file system path data in the file system path data store.

5. The computer system of claim 4, wherein the registration module is adapted to remove file system path data from the file system path data store in response to at least one selected from the group consisting of:

an application, a server, and a file system becoming inaccessible.

6. The computer system of claim 4, wherein the file system path data comprises at least one selecting from the group consisting of:

a file system name, a server identification, a server address, a file system version identifier, supported file system events, permitted file system events, permission information, authentication information, and checksum information.

7. The computer system of claim 1, wherein the file system event request comprises at least one selected from the group comprising:

a file system name, file system event, a data payload, and entry point data.

8. The computer system of claim 1, wherein the first server comprises an off-premises server and the second server comprises an on-premises server, and wherein the receiving the file system event request receives the file system event request from the off-premises server, and the communicating the file system event request communicates the file system event request to the on-premises server based on the identified file system path data.

9. The computer system claim 1, wherein the first server comprises an on-premises server and the second server comprises an off-premises server, and wherein the receiving the file system event request receives the file system event request from the on-premises server, and the communicating the file system event request communicates the file system event request to the off-premises server based on the identified file system path data.

10. The computer system of claim 1, further comprising receiving a response to the communicated file system event request, and communicating the received response to the application.

11. A computer-implemented method of managing communication between off-premises and on-premises servers, the method comprising:

storing, in a file system path data store, file system path data associated with one or more file systems;

receiving a file system event request from an application of a first server;

determining a requested file system based on the received file system event request;

identifying stored file system path data associated with the requested file system; and

communicating the file system event request to a second server based on the identified file system path data.

12. The method of claim 11, wherein the first server comprises an off-premises server and the second server comprises an on-premises server, or the first server comprises an on-premises server and the second server comprises an off-premises server.

13. The method of claim 11, further comprising:

receiving end-point data from at least one selected from the group consisting of;

an application of an off-premises server, an application of an on-premises server, an off-premises server module, and an on-premises server module; and

storing received file system path data in the file system path data store.

14. The method of claim 13, further comprising removing file system path data from the file system path data store in response to at least one selected from the group consisting of:

an application, a server, and a file system becoming inaccessible.

15. The method of claim 11, wherein the first server comprises an off-premises server and the second server comprises an on-premises server, and wherein the receiving the file system event request comprises receiving the file system event request from the off-premises server, and wherein the communicating the file system event request comprises communicating the file system event request to the on-premises server based on the identified file system path data.

16. The method of claim 11, wherein the first server comprises an on-premises server and the second server comprises an off-premises server, and wherein the receiving the file system event request comprises receiving the file system event request from the on-premises server, and wherein the communicating the file system event request comprises communicating the file system event request to the off-premises server based on the identified file system path data.

17. The method of claim 11, further comprising:

receiving a response to the communicated file system event request; and

communicating the received response to the application.

18. A computer program product for managing communication between off-premises and on-premises servers, 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 a file system path data store, file system path data associated with one or more file systems;

receiving a file system event request from an application of a first server;

determining a requested file system based on the received file system event request

identifying stored file system path data associated with the requested file system; and

communicating the file system event request to a second server based on the identified file system path data.

19. The computer program product of claim 19, wherein the first server comprises an off-premises server and the second server comprises an on-premises server, or the first server comprises an on-premises server and the second server comprises an off-premises server.

20. The computer program product of claim 19, wherein the wherein the first server comprises an off-premises cloud server, and wherein the application is provided as a service of the off-premises cloud server.