Socket-like communication API for Java

• US 20060129981A1
• Filed: 12/14/2004
• Published: 06/15/2006
• Est. Priority Date: 12/14/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Dostert, Jan, Fleischer, Christian
• Granted Patent: US 7,600,217 B2
• Time in Patent Office: Days
• US Class Current: 717/114
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A system and method are described for performing data processing using shared memory and socket-like application programming interface. In one embodiment, a plurality of handles is employed and associated with a plurality of processes. The plurality of handles may serve as communication end-points for communication of data. Further, an application programming interface is employed to present the plurality of handles as the application programming interface for sockets for facilitating the communication of data compatible with a programming language. The data is communicated between the plurality of processes via the socket-like plurality of handles.

Claims

1. A method, comprising:

employing a plurality of handles associated with a plurality of processes, wherein the plurality of handles serve as communication end-points for communication of data;

employing an application programming interface (API) to present the plurality of handles as the API for sockets for facilitating the communication of data compatible with a programming language; and

communicating the data between the plurality of processes via the plurality of handles.

2. The method of claim 1, wherein the programming language includes one or more of the following:

C, C++, C#, Visual Basic, and Java.

3. The method of claim 1, wherein the API comprises a programming language-based API including one or more of the following:

a C-based API, a C++-based API, a C#-based API, a Visual Basic-based API, and a Java-based API.

4. The method of claim 1, wherein the communicating of the data comprises receiving requests and providing responses in response to the requests, the requests including on or more of the following:

Advanced Business Application Programming (ABAP)-related requests and Java-related requests.

5. The method of claim 1, wherein the plurality of processes comprises a plurality of ABAP-based work processes for processing the ABAB-related requests, wherein the plurality of ABAP-based work processes resides at an ABAP engine.

6. The method of claim 1, wherein the plurality of processes comprises a plurality of Java 2 Enterprise Engine (J2EE)-based worker nodes for processing the Java-related requests, wherein the plurality of J2EE-based work processes resides at a J2EE engine.

7. The method of claim 1, wherein the communicating of the data further comprises using a shared memory to provide a common access to the ABAP and J2EE engines, wherein the using of the shared memory to provide the common access includes integrating the ABAP and J2EE engines.

8. The method of claim 7, wherein the providing of the common access comprises facilitating bi-directional communication between the plurality of components, wherein the plurality of components further include one or more of the following:

an internet communication manager (ICM), the ABAP engine having the plurality of work processes, and the J2EE engine having the plurality of worker nodes.

9. The method of claim 7, wherein the shared memory includes a plurality of memory pipes to work bi-directionally to facilitate the bi-directional communication between each of the plurality of components.

10. A system, comprising:

a request-creation tool at a client capable of creating requests to perform transactions, wherein the requests are sent to a server having a request-handling service; and

the request-handling service at the server coupled with the client, the request-handling service to receive the requests, wherein the request-handling services is further to

employ a plurality of handles associated with a plurality of processes, wherein the plurality of handles serve as communication end-points for communication of data;

employ an API to present the plurality of handles as the API for sockets for facilitating the communication of data compatible with a programming language; and

communicate the data between the plurality of processes via the plurality of handles.

11. The system of claim 10, wherein the programming language includes one or more of the following:

C, C++, C#, Visual Basic, and Java.

12. The system of claim 10, wherein the API comprises a programming language-based API including one or more of the following:

a C-based API, a C++-based API, a C#-based API, a Visual Basic-based API, and a Java-based API a C-based API and a Java-based API.

13. The system of claim 10, wherein the communicating of the data comprises receiving requests and providing responses in response to the requests, the requests including on or more of the following:

ABAP-related requests and Java-related requests.

14. The system of claim 10, wherein the plurality of processes comprises a plurality of ABAP-based work processes for processing the ABAB-related requests, wherein the plurality of ABAP-based work processes resides at an ABAP engine.

15. The system of claim 10, wherein the plurality of processes comprises a plurality of J2EE-based worker nodes for processing the Java-related requests, wherein the plurality of J2EE-based work processes resides at a J2EE engine.

16. A machine-readable medium having stored thereon data representing sets of instructions which, when executed by a machine, cause the machine to:

employ a plurality of handles associated with a plurality of processes, wherein the plurality of handles serve as communication end-points for communication of data;

employ an API to present the plurality of handles as the API for sockets for facilitating the communication of data compatible with a programming language; and

communicate the data between the plurality of processes via the plurality of handles.

17. The machine-readable medium of claim 16, wherein the programming language includes one or more of the following:

C, C++, C#, Visual Basic, and Java.

18. The machine-readable medium of claim 16, wherein the API comprises a programming language-based API including one or more of the following:

a C-based API, a C++-based API, a C#-based API, a Visual Basic-based API, and a Java-based API.

19. The machine-readable medium of claim 16, wherein the communicating of the data comprises receiving requests and providing responses in response to the requests, the requests including on or more of the following:

ABAP-related requests and Java-related requests.

20. The machine-readable medium of claim 16, wherein the plurality of processes comprises a plurality of ABAP-based work processes for processing the ABAB-related requests, wherein the plurality of ABAP-based work processes resides at an ABAP engine.