Method and system for cascading a middleware to a data orchestration engine

• US 8,266,104 B2
• Filed: 08/26/2008
• Issued: 09/11/2012
• Est. Priority Date: 08/26/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kothandaraman, Ramprasadh, Lock, Hendrik, Lamba, Vikas, Pattewar, Pravin Prakash
• Primary Examiner(s): Pulliam, Christyann
• Assistant Examiner(s): Khoshnoodi, Fariborz
• Application Number:
  US12/198,874
• Publication Number:
  US 20100057744A1
• Time in Patent Office: 1,477 Days
• Field of Search: 707/709, 707/730, 707/731, 707/749, 707/772, 707/826, 707/620, 707/621
• US Class Current: 707/620
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Methods, systems, and computer-readable medium storing instructions thereon for implementing methods are directed to facilitating data exchange, such as accessing and operating on data objects, between field applications, such as mobile clients, and dedicated servers by leveraging the features of middleware. An embodiment includes a first server providing a first set of services and data to a mobile client. A first communicating middleware is connected between the first server and the mobile client according to a first communication functionality. A second server provides a second set of services and data according to a second communication functionality that is different from the first communication functionality. A second middleware communicates with the second server according to the second communication functionality, and communicates with the first middleware according to the first communication functionality. The second middleware is connected to the second server and the first middleware.

Claims

1. A system for providing access to data, comprising:

a first server that provides a first set of services and data to a mobile client, the mobile client configured to exchange data with the first server;

a first middleware connected between the first server and the mobile client for communicating between the first server and the mobile client according to a first communication functionality to enable direct push-pull communication between the first server and the mobile client;

a second server that provides a second set of services and data according to a second communication functionality that is different from the first communication functionality, wherein the mobile client is incapable of directly accessing the second set of services and data from the second server;

a second middleware connected to the second server and the first middleware for providing the mobile client access to the second set of services and data provided by the second server by communicating with the second server according to the second communication functionality and communicating with the first middleware according to the first communication functionality, wherein the second middleware pulls the second set of data from the second server and pushes second set data changes to the first middleware, and wherein the push and pull of the second set of data are not available directly to the first middleware; and

a key mapping module for;

calling a service operating on a second middleware, the service call including new keys and keys of documents with new data,

when the new keys match previously assigned keys maintained by the first middleware, replicating changed data in the document and update data, maintained by the first middleware, related to the document,

mapping the changed data and a primary key related to the changed data provided by the first middleware to a database maintained by the second server,

replicating the changed data at second middleware, and

uploading the replicated data to the mobile client.

2. The system of claim 1, wherein the second middleware responds to remote function calls and remote process calls.

3. A computer-implemented method for providing access to data, comprising:

providing by a first server a first set of services and data to a mobile client, the mobile client configured to exchange data with the first server;

communicating by a first middleware connected between the first server and the mobile client according to a first communication functionality to enable direct push-pull communication between the first server and the mobile client;

providing by a second server, a second set of services and data according to a second communication functionality that is different from the first communication functionality;

communicating, by a second middleware, with the second server according to the second communication functionality and communicating with the first middleware according to the first communication functionality, wherein the second middleware is connected to the second server and the first middleware, wherein the second middleware pulls the second set of data from the second server and pushes second set data changes to the first middleware, and wherein the push and pull of the second set of data are not available directly to the first middleware;

calling a service operating on a second middleware, the service call including new keys and keys of documents with new data,

when the new keys match previously assigned keys maintained by the first middleware, replicating changed data in the document and update data, maintained by the first middleware, related to the document,

mapping the changed data and a primary key related to the changed data provided by the first middleware to a database maintained by the second server,

replicating the changed data at second middleware, and

uploading the replicated data to the mobile client.

4. The method of claim 3, further comprising:

delivering requested data to a mobile client that is incapable of accessing the data directly from the second server.

5. The method of claim 3, further comprising:

analyzing keys associated with data provided by the second server with keys maintained at the second middleware.

6. The method of claim 5, further comprising:

based on the analysis, downloading the requested data from the second server when the data associated with the keys have changed.

7. The method of claim 5, further comprising:

based on the analysis calling a service to provide new keys because the data has changed or created, wherein the new keys are stored in a consolidated data store.

13. The computer-implemented method of claim 3, further comprising:

changing data by either adding or revising data in a document by a first computer application; and

assigning keys to documents containing the changed data at the first middleware in a key mapping operation, wherein the document containing the changed data includes new documents that are assigned new keys and revised documents, which have previously assigned keys.

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

triggering a scheduled data retrieval operation at the first middleware to retrieve data maintained by the first server;

retrieving data from a database maintained by the first server;

analyzing the retrieved data at the first middleware.

15. The computer-implemented method of claim 3, comprising:

assigning keys to documents generated by data operations at the first middleware in a key mapping operation, wherein the documents generated include new documents that are assigned new keys and revised documents which have previously assigned keys;

calling a service operating on a second middleware, wherein the service call includes new keys and keys of documents with new data;

at the second middleware, comparing the keys included in the service call to keys maintained at the second middleware;

when the comparison of the keys indicates new data or revised data, data is stored in a database maintained by the second middleware;

replicating the data stored in the database maintained by the second middleware; and

forwarding the replicated data to the client.

8. A non-transitory computer readable storage medium embodied with instructions for a method for providing access to data, the instructions causing a computer to execute the method, comprising:

providing by a first server a first set of services and data to a mobile client, the mobile client configured to exchange data with the first server;

communicating by a first middleware connected between the first server and the mobile client according to a first communication functionality to enable direct push-pull communication between the first server and the mobile client;

providing by a second server, a second set of services and data according to a second communication functionality that is different from the first communication functionality;

communicating, by a second middleware, with the second server according to the second communication functionality and communicating with the first middleware according to the first communication functionality, wherein the second middleware is connected to the second server and the first middleware, wherein the second middleware pulls the second set of data from the second server and pushes second set data changes to the first middleware, and wherein the push and pull of the second set of data are not available directly to the first middleware;

calling a service operating on a second middleware, the service call including new keys and keys of documents with new data,

when the new keys match previously assigned keys maintained by the first middleware, replicating changed data in the document and update data, maintained by the first middleware, related to the document,

mapping the changed data and a primary key related to the changed data provided by the first middleware to a database maintained by the second server,

replicating the changed data at second middleware, and

uploading the replicated data to the mobile client.

9. The computer readable storage medium of claim 8, further comprises:

delivering requested data to a mobile client, wherein the mobile client is incapable of accessing the data directly from the second server.

10. The computer readable storage medium of claim 8, further comprising:

analyzing keys associated with data provided by the second server with keys maintained at the second middleware.

11. The computer readable storage medium of claim 10, further comprising:

based on the analysis, downloading the requested data from the second server when the data associated with the keys have changed.

12. The computer readable storage medium of claim 10, further comprising:

based on the analysis calling a service to provide new keys because the data has changed or created, wherein the new keys are stored in a consolidated data store.

16. The computer readable storage medium of claim 8, comprising:

changing data by either adding or revising data in a document by a first computer application; and

assigning keys to documents containing the changed data at the first middleware in a key mapping operation, wherein the document containing the changed data includes new documents that are assigned new keys and revised documents, which have previously assigned keys.

17. The computer readable storage medium of claim 8, comprising:

triggering a scheduled data retrieval operation at the first middleware to retrieve data maintained by the first server;

retrieving data from a database maintained by the first server;

analyzing the retrieved data at the first middleware.

18. The computer readable storage medium of claim 8, comprising:

assigning keys to documents generated by data operations at the first middleware in a key mapping operation, wherein the documents generated include new documents that are assigned new keys and revised documents which have previously assigned keys;

calling a service operating on a second middleware, wherein the service call includes new keys and keys of documents with new data;

at the second middleware, comparing the keys included in the service call to keys maintained at the second middleware;

when the comparison of the keys indicates new data or revised data, data is stored in a database maintained by the second middleware;

replicating the data stored in the database maintained by the second middleware; and

forwarding the replicated data to the client.