Extensible remote data synchronization

• US 20050137895A1
• Filed: 12/19/2003
• Published: 06/23/2005
• Est. Priority Date: 12/19/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Dournov, Pavel, Whitlock, Donna, Yeates, Anthony J., La Blanc, Sylvester, Hawthorne, Eric
• Granted Patent: US 7,487,189 B2
• Time in Patent Office: Days
• US Class Current: 705/1.100
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

Data replication between a headquarters application and one or more client applications is provided. The client applications are generally located remote from the headquarters application and communicate therewith via known methods. A pair of classes is used to generically transfer data selected for replication. New entity types and/or data types can be synchronized without having to rewrite the synchronization application by simply deploying an appropriate data class and manager class for the new entity. Moreover, the prior art worksheet is abstracted, in some aspects, to a simpler form that is more user friendly.

Claims

1. A system for replicating information, the system comprising:

an HQ server application;

at least one remote application remote from the HQ server application;

a communication link between the HQ server application and at least one remote application; and

wherein data selected for replication between the HQ server application and at least one remote application is replicated over the communication link generically.

2. The system of claim 1, wherein the HQ server application is coupled to a service that periodically checks for modification to the data selected for replication.

3. The system of claim 1, and further comprising a change tracking table for recording changes to the data selected for replication.

4. The system of claim 3, wherein the HQ server application is coupled to a service that periodically checks the change tracking table.

5. The system of claim 3, wherein an entry is added to the change tracking table upon a modification to the data selected for replication.

6. The system of claim 5, wherein entries are added periodically based upon a query for modifications to the data selected for replication.

7. The system of claim 5, and further comprising a software trigger to automatically add the entry to the change tracking table.

8. The system of claim 1, and further comprising a data class and manager class corresponding to the data selected for replication, wherein the data class and manager class are implemented on the HQ application and at least one remote application.

9. The system of claim 8, wherein metadata describing the data class is consumed during replication to instantiate a manager class object relative to the data selected for replication.

10. The system of claim 9, wherein the manager class object includes information to instantiate a data object to encapsulate the data selected for replication.

11. The system of claim 10, wherein the data object is transmitted over the link.

12. The system of claim 1, wherein the link includes web services.

13. The system of claim 1, wherein the data selected for replication is compressed prior to transfer.

14. The system of claim 1, wherein the data selected for replication is encrypted prior to transfer.

15. The system of claim 1, wherein the HQ application is coupled to a user interface that provides data views relative to at least one remote application.

16. The system of claim 15, wherein the interface provides data views of all remote applications in an organization.

17. The system of claim 16, wherein the views allow data to be modified.

18. The system of claim 1, wherein the information is business information, and wherein at least one of the remote locations is located at a store.

19. A method of replicating data between a source and at least one target located remotely from the source, the method comprising:

selecting data for replication between the source and the target;

detecting a modification to the data at the source;

instantiating a manager object at the source relative to the modified data;

instantiating with the manager object a data object to encapsulate the data;

transferring the data object over a link from the source to the target;

instantiating a manager object at the target relative to the data object received over the link; and

using the manager object instantiated at the target to persist the data object.

20. The method of claim 19, wherein the target is an HQ application.

21. The method of claim 20, wherein the target is a store.

22. The method of claim 19, wherein detecting a modification to the data includes checking a tracking table.

23. The method of claim 22, wherein an entry is added to the tracking table when the data is modified.

24. The method of claim 23, wherein entries are added periodically based upon a query for modifications to the data selected for replication.

25. The method of claim 23, wherein the entry is automatically added.

26. The method of claim 25, wherein automatically adding entries includes employing a database trigger.

27. The method of claim 19, wherein transferring the data object includes employing web services to transfer the data object.

28. The method of claim 19, wherein the data object is compressed prior to the step of transferring.

29. The method of claim 19, wherein the data object is encrypted prior to the step of transferring.