Method and apparatus for synchronizing client transactions executed by an autonomous client

• US 20060010130A1
• Filed: 07/09/2004
• Published: 01/12/2006
• Est. Priority Date: 07/09/2004
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Leff, Avraham, Rayfield, James Thomas
• Application Number:
  US10/888,811
• Publication Number:
  US 20060010130A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

One embodiment of the present method and apparatus for synchronization of client transactions executed by an autonomous client enables a client operating on a limited connection to a server to log transactions executed against a locally stored server database state. Logged transactions are then synchronized with a current server database state by delivering the transaction log to the server, which re-executes each logged client transaction against the current server database state, thereby reducing synchronization-related transaction conflicts.

Claims

1. A method for synchronizing one or more transactional applications executed by a client against a transaction database of an associated server, the method comprising the steps of:

caching data representing at least a portion of a current state of said server transaction database;

recording one or more transactional business logic executions executed against the cached data in a client transaction log, where said client operates substantially autonomously when said transactions are executed; and

delivering said transaction log to said server when said client re-establishes a full connection with said server.

2. The method of claim 1, wherein said transaction log comprises at least one of the following for each recorded business logic execution:

a name for the business logic execution, input parameters for the business logic execution and the business logic execution'"'"'s result value.

3. The method of claim 1 wherein said caching step comprises:

requesting said data from said server; and

receiving said data from said server in response to said request.

4. The method of claim 1, wherein said data represents a subset of said server'"'"'s current state.

5. The method of claim 1, wherein said client comprises one or more transactional applications that are capable of execution when said client operates substantially autonomously.

6. The method of claim 1, further comprising the steps of:

receiving a status update from said server, wherein said status update represents an updated server transaction database state reflecting the extent to which said recorded business logic executions were synchronized with said server transaction database at said server; and

deleting the cached server transaction database state data.

7. The method of claim 6, further comprising the step of:

replacing the deleted server transaction database state data with data representing the updated server transaction database state.

8. The method of claim 1, wherein said client is not connected to said server when said business logic executions are executed and recorded.

9. The method of claim 1, wherein said substantially autonomous operation of said client is attributable to at least one of slow connection speed and high latency.

10. A computer readable medium containing an executable program for synchronizing transactional applications executed by a client against a transaction database of an associated server, where the program performs the steps of:

caching data representing at least a portion of a current state of said server transaction database;

recording one or more transactional business logic executions against the cached data in a client transaction log, where said client operates substantially autonomously when said transactions are executed; and

delivering said transaction log to said server when said client re-establishes a full connection to said server.

11. The computer readable medium of claim 10, wherein said transaction log comprises at least one of the following for each recorded business logic execution:

a name for the business logic execution, input parameters for the business logic execution and the business logic execution'"'"'s result value.

12. The computer readable medium of claim 10 wherein said caching step comprises:

requesting said data from said server; and

receiving said data from said server in response to said request.

13. The computer readable medium of claim 10, wherein said data represents a subset of said server'"'"'s current state.

14. The computer readable medium of claim 10, wherein said client comprises one or more transactional applications that are capable of execution when said client operates substantially autonomously.

15. The computer readable medium of claim 10, further comprising the steps of:

receiving a status update from said server, wherein said status update represents an updated server transaction database state reflecting the extent to which said recorded business logic executions were synchronized with said server transaction database at said server; and

deleting the cached server transaction database state data.

16. The computer readable medium of claim 15, further comprising the step of:

replacing the deleted server transaction database state data with data representing the updated server transaction database state.

17. The computer readable medium of claim 10, wherein said client is not connected to said server when said business logic executions are executed and recorded.

18. The computer readable medium of claim 10, wherein said substantially autonomous operation of said client is attributable to at least one of slow connection speed and high latency.

19. An apparatus for synchronizing transactional applications executed by a client against a transaction database of an associated server, comprising:

means for caching data representing at least a portion of a current state of said server transaction database;

means for recording one or more transactional business logic executions executed against the cached data in a client transaction log, where said client operates substantially autonomously when said business logic executions are executed; and

means for delivering said transaction log to said server when said client re-establishes a full connection to said server.

20. The apparatus of claim 19, wherein said apparatus is deployed within a framework for distributed enterprise components.

21. The apparatus of claim 20, wherein said apparatus is deployed within at least one of an Enterprise JavaBeans or Java 2 Platform, Enterprise Edition system.

22. A method for synchronizing one or more transactional business logic executions executed by a client with a current state of a transaction database residing at a server, the method comprising the steps of:

receiving a transaction log from said client, wherein said transaction log comprises one or more transactional business logic executions executed by said client while said client operates substantially autonomously; and

re-executing each recorded business logic execution against said transaction database.

23. The method of claim 22, wherein business logic executions recorded in said log are re-executed one-by-one.

24. The method of claim 22, further comprising the steps of:

receiving a request from said client to transmit data representing a current state of said transaction database, prior to receiving said transaction log; and

delivering, in response to said request, said data to said client.

25. The method of claim 22, further comprising the steps of:

delivering a status report to said client, wherein said status report represents an updated transaction database state reflecting the extent to which said business logic executions recorded by said client were synchronized with said transaction database at said server.

26. The method of claim 22, wherein said transaction log comprises at least one of the following for each business logic execution:

a name for the business logic execution, input parameters for the business logic execution and the business logic execution'"'"'s result value.

27. A computer readable medium containing an executable program for synchronizing one or more transactional business logic executions executed by a client with a current state of a transaction database residing at a server, where the program performs the steps of:

receiving a transaction log from said client, wherein said transaction log comprises one or more transactional business logic executions executed by said client while said client operates substantially autonomously; and

re-executing each business logic execution recorded in said log against said transaction database.

28. The computer readable medium of claim 27, wherein business logic executions recorded in said log are re-executed one-by-one.

29. The computer readable medium of claim 27, further comprising the steps of:

receiving a request from said client to transmit data representing a current state of said transaction database, prior to receiving said transaction log; and

delivering, in response to said request, said data to said client.

30. The computer readable medium of claim 27, further comprising the steps of:

delivering a status report to said client, wherein said status report represents an updated transaction database state reflecting the extent to which said business logic executions recorded by said client were synchronized with said transaction database at said server.

31. The computer readable medium of claim 27, wherein said transaction log comprises at least one of the following for each recorded business logic execution:

a name for the business logic execution, input parameters for the business logic execution and the business logic execution'"'"'s result value.

32. An apparatus for synchronizing one or more transactional business logic executions executed by a client with a current state of a transaction database residing at a server, comprising:

means for receiving a transaction log from said client, wherein said transaction log comprises one or more transactional business logic executions executed by said client while said client operates substantially autonomously; and

means for re-executing each business logic execution recorded in said log against said transaction database.

33. The apparatus of claim 32, wherein said apparatus is deployed within a framework for distributed enterprise components.

34. The apparatus of claim 33, wherein said apparatus is deployed within at least one of an Enterprise JavaBeans or Java 2 Platform, Enterprise Edition system.