Co-execution of objects from divergent runtime environments

• US 20090025009A1
• Filed: 07/18/2007
• Published: 01/22/2009
• Est. Priority Date: 07/18/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Helm, Martin, Rosbach, Joerg, Nieswand, Wolfgang, Brunswig, Frank, Heiler, Jan
• Granted Patent: US 8,074,229 B2
• Time in Patent Office: Days
• US Class Current: 719/312
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

Systems and methods are described that permit objects from runtime environments that are incompatible with one another to be co-executed on a computing machine. Depending on which object can service the request, a generic proxy may send the request to the proxy of the particular runtime environment associated with that object. The proxy may call the appropriate methods of the object therein to service the request. Each runtime environment may be isolated from other runtime environments by a container such that catastrophic errors in one runtime environment do not disrupt the execution of objects in another runtime environment. A first object in a first runtime environment may execute methods in a second object in a second runtime environment by invoking a proxy of the second runtime environment to call the methods of the second object.

Claims

1. A system for co-execution of objects from divergent runtime environments, comprising:

a first runtime environment configured to execute a first object;

a second runtime environment configured to execute a second object, the first and second runtime environments further configured to be isolated from one another;

a first proxy associated with the first runtime environment;

a second proxy associated with the second runtime environment; and

a generic proxy configured to do one of;

call a method of the first object by invoking the first proxy, the first proxy configured to call the method of the first object, and

call a method of the second object by invoking the second proxy, the second proxy configured to call the method of the second object,

wherein the second runtime environment is incompatible with the first object and the first runtime environment is incompatible with the second object.

2. The system of claim 1, wherein the co-execution of the first and second objects occurs in a single transaction.

3. The system of claim 2, wherein each of the first and second objects is associated with a respective metadata, the metadata being stored in a shared repository, the shared repository being accessible to the first and second runtime environments.

4. The system of claim 1, wherein the first object is configured to call a method of the second object by invoking the first proxy, the first proxy is configured to invoke the second proxy, and the second proxy is configured to call the method of the second object.

5. The system of claim 1, further comprising:

a first container configured to execute the first runtime environment and to isolate the first runtime environment from catastrophic errors in the second runtime environment; and

a second container configured to execute the second runtime environment and to isolate the second runtime environment from catastrophic errors in the first runtime environment.

6. The system of claim 1, wherein the first and second proxies communicate via a shared memory.

7. The system of claim 1, wherein the first and second proxies communicate using remote function calls.

8. The system of claim 1, wherein the first runtime environment is configured to execute a third object and the second runtime environment is configured to execute a fourth object, and

wherein the third and fourth objects are configured to share data using a shared memory.

9. The system of claim 1, wherein the first runtime environment is an ABAP virtual machine and the second runtime environment is a Java virtual machine.

10. The system of claim 1, wherein the first runtime environment is configured to execute a third object, and

wherein the first object is configured to call a method of the third object by invoking the first proxy and the first proxy is configured to call the method of the third object.

11. The system of claim 4, wherein the second object is configured to call a method of the first object by invoking the second proxy, the second proxy is configured to invoke the first proxy, and the first proxy is configured to call the method of the first object.

12. The system of claim 11, further comprising:

a first container configured to execute the first runtime environment and to isolate the first runtime environment from catastrophic errors in the second runtime environment; and

a second container configured to execute the second runtime environment and to isolate the second runtime environment from catastrophic errors in the first runtime environment.

13. A method of executing objects from divergent runtime environments, comprising:

at a first runtime environment, receiving a request to execute a method of an object of a second runtime environment;

invoking a first proxy of the first runtime environment to call a second proxy of the second runtime environment;

transmitting the request from the first proxy to the second proxy; and

at the second proxy, calling the method of the second object,

wherein the first and second runtime environments are isolated from one another.

14. The method of claim 13, wherein the request is transmitted via shared memory.

15. The method of claim 14, wherein the request is transmitted via a remote function call.

16. The method of claim 13, wherein the first runtime environment is an ABAP virtual machine and the second runtime environment is a Java virtual machine.

17. The method of claim 13, further comprising:

sharing data between a third object of the first runtime environment and a fourth object of a second runtime environment using shared memory.

18. A system for co-execution of objects from divergent runtime environments, comprising:

a first runtime environment configured to execute a first object;

a second runtime environment configured to execute a second object, the first and second runtime environments further configured to be isolated from one another;

a first proxy associated with the first runtime environment;

a second proxy associated with the second runtime environment;

a first container configured to execute the first runtime environment and to isolate the first runtime environment from catastrophic errors in the second runtime environment;

a second container configured to execute the second runtime environment and to isolate the second runtime environment from catastrophic errors in the first runtime environment; and

a generic proxy configured to either

call a method of the first object by invoking the first proxy, the first proxy configured to call the method of the first object, or

call a method of the second object by invoking the second proxy, the second proxy configured to call the method of the second object,

wherein the second runtime environment is incompatible with the first object and the first runtime environment is incompatible with the second object.

19. The system of claim 18, further comprising a locking manager to lock down the first and second objects so that the first and second objects are each modifiable by a single entity at a time.