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

• US 9,864,788 B2
• Filed: 08/08/2012
• Issued: 01/09/2018
• Est. Priority Date: 08/26/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Lock, Hendrik C. R., Lamba, Vikas, Pattewar, Pravin Prakash, Kothandaraman, Ramprasadh
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Khoshnoodi, Fariborz
• Application Number:
  US13/569,483
• Publication Number:
  US 20120303580A1
• Time in Patent Office: 1,980 Days
• Field of Search: 707620, 707621
• 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 computer-implemented method for providing access to data and maintaining data integrity, the method comprising:

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

assigning keys to documents containing the changed data at a first middleware associated with the first computer application in a key mapping operation, wherein the documents containing the changed data include new documents that are assigned new keys and revised documents, which have previously assigned keys;

calling, by the first middleware, a service operating on a second middleware, wherein the service call includes new keys and keys of documents with new data, and wherein push and pull functionality of data in the first server is not available directly to the second middleware;

after the new keys match the previously assigned keys maintained by the first middleware, replicating the 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 a second server;

replicating the changed data at the second middleware; and

uploading the replicated data to a client.

2. The computer-implemented method of claim 1, wherein the second middleware responds to remote function calls and remote process calls.

3. The computer-implemented method of claim 1, wherein the new keys are stored in a consolidated data store.

7. The computer-implemented method of claim 1, wherein the second middleware communicates with the first middleware according to a first communication functionality and the second middleware communicates with the second server according to a second communication functionality.

8. The computer-implemented method of claim 1, further comprising receiving at the first middleware a second set of data changes from the second middleware, wherein the second set of data changes were pulled by the second middleware from the second server.

9. The computer-implemented method of claim 8, wherein the second set of data changes are not available directly to the first middleware.

4. A computer-implemented method for providing access to data and maintaining data integrity, the method comprising:

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

retrieving data from a database maintained by the first server;

analyzing the retrieved data at the first middleware;

assigning keys to documents generated by the 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, by the first middleware, a service operating on a second middleware, wherein the service call includes new keys and keys of documents with new data, and wherein push and pull functionalities of data in the first server is not available directly to the second middleware;

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

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

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

forwarding the replicated data to a client.

5. The computer-implemented method of claim 4, wherein the second middleware responds to remote function calls and remote process calls.

6. The computer-implemented method of claim 4, wherein the new keys are stored in a consolidated data store.

10. The computer-implemented method of claim 4, wherein the second middleware communicates with the first middleware according to a first communication functionality and the second middleware communicates with the second server according to a second communication functionality.

11. The computer-implemented method of claim 4, further comprising receiving at the first middleware a second set of data changes from the second middleware, wherein the second set of data changes were pulled by the second middleware from the second server.

12. The computer-implemented method of claim 11, wherein the second set of data changes are not available directly to the first middleware.