Simplifying synchronization of copies of same data used by multiple applications

• US 8,572,161 B2
• Filed: 03/12/2008
• Issued: 10/29/2013
• Est. Priority Date: 03/12/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gill, Bikram Singh
• Primary Examiner(s): Bengzon, Greg C
• Application Number:
  US12/046,504
• Publication Number:
  US 20090235185A1
• Time in Patent Office: 2,057 Days
• Field of Search: 709201-203, 709208-209, 709218-220, 709/248, 707614-615, 707626-633, 707/634, 707/637, 707662-665, 707690-692, 707702-703, 707806-811, 715/230, 715/234, 715/700, 715735-739, 715/748, 715/760, 715/866
• US Class Current: 709/203
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Simplifying synchronization of copies of same data used by multiple applications, in particular, between a source application and multiple target applications. In one embodiment, a synchronization tool (provided external to the source application and the multiple target applications) pulls information of interest from a data store associated with the source application using a web service and then pushes the retrieved information of interest to corresponding data stores associated with the multiple target applications using respective web services.

Claims

1. A method of simplifying synchronization of information between a source application and a plurality of target applications, said method being performed by a sync tool provided external to said source application and said plurality of target applications, said method comprising:

maintaining a configuration data specifying a plurality of mappings, each mapping indicating that information is to be synchronized between said source application and one of said plurality of target applications;

selecting, by said sync tool, a first mapping indicating that information is to be synchronized between said source application and said first target application, wherein said first mapping is contained in said plurality of mappings,

said first mapping further indicating a criteria qualifying said information to be synchronized, wherein said criteria qualifies a plurality of data items of said source application are to be synchronized with said first target application;

pulling from said sync tool, said plurality of data items using a first web service designed to retrieve said plurality of data items from a first data store associated with said source application,

wherein said pulling comprises sending a request to said first web service for invoking a first operation provided by said first web service and receiving a response from said first web service containing said plurality of data items, whereby said pulling causes said plurality of data items to be received by said sync tool,

wherein said request and said response are according to respective formats specified by a first web service definition according to Web Service Definition Language (WSDL),

wherein said first web service definition is capable of being retrieved as a corresponding WSDL file from said first web service,

wherein said first web service definition further specifies an identifier of said first operation, wherein said first operation is invoked by including said identifier in said request to said first web service; and

pushing, from said sync tool, said plurality of data items using a second web service designed to store said plurality of data items in a second data store associated with a first target application contained in said plurality of target applications, wherein said pushing comprises invoking a second operation provided by said second service designed to store data in said second data store, wherein said pushing causes said plurality of data items, retrieved by said sync tool, to be stored in said second data store,

wherein said invoking of said second operation is according to a format specified by a second web service definition according to WSDL,

wherein said second web service definition is capable of being retrieved as a corresponding WSDL file from said second web service,

wherein said second web service definition further specifies an identifier of said second operation, wherein said second operation is invoked by including said identifier of said second operation in a request to said second web service,

wherein said pulling and said pushing are performed from said sync tool for each of said plurality of data items in response to said selecting of said first mapping from said configuration data,

wherein said sync tool is implemented based on at least one processor executing a set of instructions retrieved from a memory.

2. The method of claim 1, wherein each web service is designed to provide a corresponding set of operations, which on invocation performs the actions of said pulling and said pushing of information,

wherein each of said plurality of mappings further indicates the specific operations to be invoked in corresponding web services for performing synchronization of information between said source application and said plurality of target applications,

wherein said first mapping further indicates that said first operation provided by said first web service is to be invoked for said pulling of said plurality of data items and that said second operation provided by said second web service is to be invoked for said pushing of said plurality of data items,

wherein said pulling pulls said plurality of data items by invoking said first operation in said first web service and said pushing pushes said plurality of data items by invoking said second operation in said second web service based on examination of said first mapping,

wherein invoking of said first operation comprises sending a first location/URL of the first web service and said identifier of said first operation provided by the first web service.

3. The method of claim 2, wherein said selecting selects a second mapping indicating that information is to be synchronized between said source application and a second target application contained in said plurality of target applications, wherein said second mapping is contained in said plurality of mappings,

wherein said second mapping further indicates that a third operation provided by said first web service is to be invoked for said pulling of said plurality of data items and that a fourth operation provided by a third web service is to be invoked for said pushing of said plurality of data items, wherein said third web service is designed to store said plurality of data items in a third data store associated with said second target application,

wherein said pulling pulls said plurality of data items by invoking said third operation and said pushing pushes said plurality of data items by invoking said fourth operation after said selecting said second mapping,

wherein said first mapping and said second mapping are provided in the form of configuration data external to said sync tool.

4. The method of claim 3, wherein said first mapping further specifies a first schedule according to which information is to be synchronized between said source application and said first target application,

wherein said second mapping further specifies a second schedule according to which information is to be synchronized between said source application and said second target application,

wherein said sync tool performs said pulling and said pushing for said first mapping according to said first schedule,

wherein said sync tool performs said pulling and said pushing for said second mapping according to said second schedule.

5. The method of claim 2, wherein said pulling comprises:

sending said request to said first web service for invoking said first operation, wherein said request is according to an input format specified by said first web service definition; and

receiving said response to said request from said first web service, wherein said response contains said plurality of data items according to an output format specified by said first web service definition,

wherein said plurality of data items is retrieved from said first data store by a software code corresponding to said first operation executing in a first system.

6. The method of claim 5, further comprising:

converting said plurality of data items from said output format to another input format specified by said second web service definition,

wherein said pushing comprises;

sending another request to said second web service for invoking said second operation, wherein said another request contains said plurality of data items according to said another input format,

wherein said plurality of data items is stored in said second data store by a software code corresponding to said second operation executing in a second system.

7. The method of claim 6, wherein said request, said response and said another request are encoded in the form of Simple Object Access Protocol (SOAP) packets.

8. The method of claim 7, wherein said configuration data specifies a resource at which said first web service is provided, said method further comprising:

retrieving said first web service definition from said resource by sending a request to said resource,

wherein said pulling from said first web service is performed according to the retrieved first web service definition.

9. The method of claim 3, wherein said first mapping further indicates that one of a second set of operations provided by said second web service is to be invoked for said pushing of said plurality of data items, said second operation being contained in said second set of operations, said method further comprising:

maintaining a historical data indicating the information synchronized between said source application and each of said plurality of target applications; and

determining the specific one of said second set of operations to be invoked based on said historical data and said plurality of data items,

wherein said pushing pushes said plurality of data items using the determined specific one of said second set of operations.

10. The method of claim 9, wherein said second set of operations contains an insert operation and an update operation designed respectively for inserting and updating a first information packet in said second data store, said first information packet being contained in said plurality of data items,

wherein said determining determines that said insert operation is to be invoked if said historical data indicates that said first information packet is not previously synchronized between said source application and said first target application, and that said update operation is to be invoked otherwise.

11. The method of claim 10, wherein said second set of operations contains a delete operation designed for deleting a second information packet contained in said second data store,

wherein said determining determines that said delete operation is to be invoked if said second information packet is not contained in said plurality of data items and said historical data indicates that said second information packet is previously synchronized between said source application and said first target application.

12. The method of claim 11, wherein said determining determines that said delete operation is to be invoked if said second information packet is indicated to be deleted by said plurality of data items.

13. The method of claim 1, further comprising receiving an indication indicating that synchronization between said source application and said first target application is to be performed, wherein said pulling and said pushing are performed in response to said receiving said indication.

14. The method of claim 13, wherein said receiving receives said indication from one of said source application and said first target application as a request to a fourth web service provided by said sync tool.

15. The method of claim 3, further comprising:

providing a user interface to indicate the specific operations to be invoked in corresponding web services for performing synchronization of information between said source application and said plurality of target applications,

wherein a user uses said user interface to indicate that said first operation provided by said first web service is to be invoked for said pulling of said plurality of data items and that said second operation provided by said second web service is to be invoked for said pushing of said plurality of data items.

16. A non-transitory machine readable medium storing one or more sequences of instructions for causing a system to simplify synchronization of information between a source application and a plurality of target applications, wherein execution of said one or more sequences of instructions by one or more processors contained in said system causes said system to perform the actions of:

determining a first set of operations provided by a first web service and a second set of operations provided by a second web service, wherein a first subset of said first set of operations is designed to retrieve information from a first data store associated with said source application, wherein a second subset of said second set of operation is designed to store information in a second data store associated with a first target application of said plurality of target applications,

wherein said determining determines said first set of operations based on a first web service definition capable of being retrieved from said first web service, and said second set of operations based on a second web service definition capable of being retrieved from said second web service; and

enabling a user to specify a first pair of operations, wherein a first operation of said first pair is contained in said first subset, and a second operation of said first pair is contained in said second subset,

wherein a sync tool, based on said user having specified said first pair of operations, is operable to pull an information of interest by invoking said first operation of said first web service, and push said information of interest by invoking said second operation of second web service to store said information of interest in said second data store.

17. The non-transitory machine readable medium of claim 16, wherein said first web service definition and said second web service definition are according to Web Service Definition Language (WSDL),

wherein said first web service definition and said second web service definition are capable of being retrieved as corresponding WSDL files from said first web service and said second web service respectively.

18. The non-transitory machine readable medium of claim 17, wherein said enabling comprises:

providing a user interface to indicate the specific operations to be invoked in corresponding web services for performing synchronization of information between said source application and said plurality of target applications, wherein said user interface displays said first set of operations and said second set of operations,

wherein a user uses said user interface to specify said first pair of operations based on said display.

19. The non-transitory machine readable medium of claim 18, further comprising one or more instructions for:

maintaining a configuration data specifying a plurality of mappings, each mapping indicating that information is to be synchronized between said source application and one of said plurality of target applications, wherein a first mapping of said plurality of mappings indicates that information is to be synchronized between said source application and said first target application,

said maintaining further including along with said first mapping in said configuration data said first pair of operations, in response to said enabling; and

selecting initially said first mapping indicating that information is to be synchronized between said source application and said first target application,

wherein said sync tool is operable to perform said pulling and said pushing after said selecting said first mapping.

20. The non-transitory machine readable medium of claim 19, wherein said first mapping further indicates that said second subset of said second set of operations provided by said second web service can be invoked for said pushing of said information of interest to said first target application, further comprising one or more instructions for:

maintaining a historical data indicating the information synchronized between said source application and each of said plurality of target applications including said first target application; and

determining the specific one of said second subset of said second set of operations to be invoked based on said historical data for said first target application and said information of interest,

wherein said sync tool pushes said information of interest to said first target application by invoking the determined specific one of said second subset of said second set of operations.

21. The non-transitory machine readable medium of claim 20, wherein said second subset of said second set of operations contains an insert operation and an update operation designed respectively for inserting and updating a first information packet in said second data store, said first information packet being contained in said information of interest,

wherein said determining determines that said insert operation is to be invoked if said historical data indicates that said first information packet is not previously synchronized between said source application and said first target application, and that said update operation is to be invoked otherwise.

22. The non-transitory machine readable medium of claim 21, wherein said second subset of said second set of operations contains a delete operation designed for deleting a second information packet contained in said second data store,

wherein said determining determines that said delete operation is to be invoked if said second information packet is not contained in said information of interest and said historical data indicates that said second information packet is previously synchronized between said source application and said first target application.

23. A computing system comprising:

a plurality of data stores comprising corresponding non-volatile storage to store respective copies of a data, said plurality of data stores including a first data store and a second data store;

a plurality of systems to execute a plurality of applications, wherein each of said plurality of applications is designed to operate with the copy of said data maintained in one of said plurality of data stores, wherein a first application and a second application of said plurality of applications is designed to operate with respective copies of data maintained in said first data store and said second data store; and

a sync tool provided external to said plurality of applications to synchronize the copies of said data, said sync tool being operable to;

determine a first set of operations provided by a first web service and a second set of operations provided by a second web service, wherein a first subset of said first set of operations is designed to retrieve information from said first data store, wherein a second subset of said second set of operation is designed to store information in said second data store,

wherein said sync tool determines said first set of operations based on a first web service definition capable of being retrieved from said first web service, and said second set of operations based on a second web service definition capable of being retrieved from said second web service;

enable a user to specify a first pair of operations, wherein a first operation of said first pair is contained in said first subset, and a second operation of said first pair is contained in said second subset;

pull an information of interest contained in said data by invoking said first operation of said first web service; and

push said information of interest by invoking said second operation of said second web service to store said information of interest in said second data store,

wherein at least one of said sync tool and said plurality of systems contains a processor and a memory, said processor to retrieve instructions from said memory and to execute the retrieved instructions.

24. The computing system of claim 23, further comprising:

a local database associated with said sync tool to maintain a configuration data specifying a plurality of mappings, each mapping indicating that information is to be synchronized between said plurality of applications, wherein a first mapping of said plurality of mappings indicates that information is to be synchronized between said first application and said second application,

said sync tool further including along with said first mapping in said configuration data said first pair of operations, in response to said enabling,

wherein said sync tool initially selects said first mapping indicating that information is to be synchronized between said first application and said second application

wherein said sync tool then pulls and pushes said information of interest in response to selecting said first mapping.