Direct transmission of data between applications in a multi-tenant environment

• US 9,742,724 B2
• Filed: 09/09/2014
• Issued: 08/22/2017
• Est. Priority Date: 09/09/2014
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bailey, Christopher N.
• Primary Examiner(s): Taylor, Nicholas
• Assistant Examiner(s): Robinson, Christopher B
• Application Number:
  US14/480,831
• Publication Number:
  US 20160072919A1
• Time in Patent Office: 1,078 Days
• Field of Search: None
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Overhead of sending data from one application to another by doing input and output processing can be costly. The present invention provides a method of transmitting data with a low overhead between applications in a multi-tenant runtime environment. The multi-tenant runtime detects a connection between tenants, and then performs low-overhead data transmission mechanisms by cloning data from one tenant space to another tenant space, while keeping the data isolated for two tenants.

Claims

1. A computer program product for direct transmission of data between applications in a multi-tenant environment, the computer program product comprising a computer readable storage medium having stored thereon:

first program instructions programmed to determine if a first tenant and a second tenant exist within a same runtime;

second program instructions programmed to, responsive to the first tenant and the second tenant not existing within the same runtime, open a server socket of a first tenant;

third program instructions programmed to place an entry in a registry, the entry including an IP number and a port number associated with the first tenant;

fourth program instructions programmed to receive a request for a connection by a second tenant;

fifth program instructions programmed to store a pairing entry that associates the first tenant with the second tenant;

sixth program instructions programmed to, responsive to determining the first tenant and the second tenant exist within the same runtime, establish a mechanism for transmitting data between the first tenant and the second tenant, wherein the mechanism for transmitting data between the first tenant and the second tenant has a low overhead for transmitting data; and

seventh program instructions programmed to, responsive to a connection being made between the first tenant and the second tenant and the opening of the server socket of the first tenant, establish the mechanism for transmitting data between the first tenant and the second tenant,

wherein;

the mechanism includes, at least, one of the following;

     1) copying a byte array of the server socket from a first space assigned to the first tenant to a second space assigned to the second tenant; and

     2) intercepting an object prior to the forming of a byte array level and deep copying of the object and corresponding references from the first space assigned to the first tenant to the second space assigned to the second tenant.

2. The computer program product of claim 1, wherein when the mechanism includes copying a byte array, finalizing the data at the point of transmission.

3. The computer program product of claim 2, wherein:

the byte array for the server socket is used for a paired call; and

the paired call includes a write method and a read method.

4. The computer program product of claim 1, wherein when the mechanism includes deep copying the deep copying of the object and corresponding references is carried out by a write object method.

5. The computer program product of claim 1, wherein the mechanism for transmitting data includes maintaining any transmitted data isolated from the first tenant with respect to the second tenant after transmission is completed, in such ways as by directly cloning the transmitted data.

6. The computer program product of claim 1, further comprising:

sixth program instructions programmed to detect the connection being made between the first tenant and the second tenant.

7. The computer program product of claim 1, further comprising:

seventh program instructions programmed to responsive to receiving a request for a connection via the server socket, look up the IP number and the port number used by the server socket in the registry.

8. A computer system for direct transmission of data between applications in a multi-tenant environment, the computer system comprising:

a processor(s) set; and

a computer readable storage medium;

wherein;

the processor set is structured, located, connected and/or programmed to run program instructions stored on the computer readable storage medium; and

the program instructions include;

first program instructions to determine if a first tenant and a second tenant exist within a same runtime;

second program instructions programmed to, responsive to the first tenant and the second tenant not existing within the same runtime, open a server socket of a first tenant;

third program instructions programmed to place an entry in a registry, the entry including an IP number and a port number associated with the first tenant;

fourth program instructions programmed to receive a request for a connection by a second tenant;

fifth program instructions programmed to store a pairing entry that associates the first tenant with the second tenant; and

sixth program instructions programmed to, responsive to determining the first tenant and the second tenant exist within the same runtime, establish a mechanism for transmitting data between the first tenant and the second tenant, wherein the mechanism for transmitting data between the first tenant and the second tenant has a low overhead for transmitting data; and

seventh program instructions programmed to responsive to a connection being made between the first tenant and the second tenant and the opening of the server socket of the first tenant, establish the mechanism for transmitting data between the first tenant and the second tenant,

wherein;

the mechanism includes, at least, one of the following;

     1) copying a byte array of the server socket from a first space assigned to the first tenant to a second space assigned to the second tenant; and

     2) intercepting an object prior to the forming of a byte array level and deep copying of the object and corresponding references from the first space assigned to the first tenant to the second space assigned to the second tenant.

9. The computer system of claim 8, wherein when the mechanism includes copying a byte array, finalizing the data at the point of transmission.

10. The computer system of claim 9, wherein:

the byte array for the server socket is used for a paired call; and

the paired call includes a write method and a read method.

11. The computer system of claim 8, wherein when the mechanism includes deep copying the deep copying of the object and corresponding references is carried out by a write object method.

12. The computer system of claim 8, wherein the mechanism for transmitting data includes maintaining any transmitted data isolated from the first tenant with respect to the second tenant after transmission is completed, in such ways as by directly cloning the transmitted data.

13. The computer system of claim 8, further comprising:

sixth program instructions programmed to responsive to receiving a request for a connection via the server socket, look up the IP number and the port number used by the server socket in the registry.