METHOD AND A SYSTEM FOR POLLING AND PROCESSING DATA

• US 20130117482A1
• Filed: 04/27/2012
• Published: 05/09/2013
• Est. Priority Date: 04/28/2011
• Status: Active Grant

• Current Assignee: Opshub, Inc.
• Original Assignee: Prakash Chandra Tiwary, Sandeep Jain
• Inventors: Jain, Sandeep, Tiwary, Prakash Chandra
• Granted Patent: US 9,489,325 B2
• Time in Patent Office: Days
• US Class Current: 710/109
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 13/22 using successive scanning, e.g. polling G06F13/24 takes precedence
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2322 using timestamps
• 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

Abstract

The embodiments herein provide a method and system for polling and processing data. The method comprises computing a maximum time from a source after a last update time, waiting for a preset time to ensure that all transactions with respect to a change in a data is completed, querying for a plurality of changes after an elapse of the preset waiting time since the last update time and up to the maximum time, generating a time window, collecting a list of changes occurred within the generated time window, sending the collected list of changes for processing; and updating the processed data at the destination. The time window comprises a time interval between the last update time and the maximum time.

Claims

1. A method for polling and processing data from a source to a destination comprises:

computing a maximum time from a source after a last update time;

waiting for a preset time to ensure that all transactions with respect to a change in a data is completed , and wherein the preset time is set such that all transactions that are in flight at a time of lust query are completed;

querying for a plurality of changes after an elapse of the preset waiting time since the last update time and up to the maximum time;

generating a time window and wherein the time window comprises a time interval between the last update time and the maximum time collecting a list of changes occurred within the generated time window;

sending the collected list of changes for processing; and

updating the processed data at the destination.

2. A system for polling and processing a data from a source to a destination comprises:

a connector framework and wherein the connector framework comprises two connector modules, a polling module and an adopter module;

a processing manager and wherein the processing manager processes a poll event using a processing engine;

a mapping manager and wherein the mapping manager maps a plurality of fields of the source to a corresponding fields of a destination;

a recovery manager and wherein the recovery manager automatically recovers a data in case of an unexpected failure;

a conflict manager and wherein the conflict manager solves one or more conflicts occurring during a synchronization process and wherein a conflict is occurred, when a current value of any field of the destination doesn'"'"'t match with a last value of a field of the source;

a failure manager and wherein the failure manager controls a failed event during a synchronization process and wherein the failed event is the one in which a change in a data is not written to the destination;

wherein the polling module reads the plurality of changes from the source and the adapter module writes the plurality of changes at the destination.

3. The system of claim 2, wherein the processing engine is any one of a Java Process Definition Language (JBOSS JPDL), Drools and an Apache Orchestration Director Engine (ODE).

4. The system of claim 2, wherein the processing manager reports a successful synchronization process back to the source after a completion of a successful synchronization process.

5. The system of claim 2, wherein the processing manager passes a control to a failure manager after an unsuccessful synchronization process.

6. The system of claim 2, wherein the recovery manager controls the adapter module and the polling module.

7. The system of claim 2, wherein the conflict manager detects a conflict to activate an integration model to resolve the conflict automatically.

8. The conflict manager of claim 7, wherein the integration model is at least one of a master/slave model, a partitioned ownership model, a dynamic ownership model, a peer to peer model and a custom configuration model, and wherein the entity is created at the master and wherein one or more read only copies of the entity are created in a slave system in the master slave model, and wherein one or more fields of the entity are created at one or more systems in the partitioned ownership model, and wherein an ownership of the entity changes dynamically in the dynamic ownership model, and wherein changes are made to the entities from a plurality of sites to carry out a conflict detection process and a conflict resolving process in the peer to peer model, and wherein a replication model is customized using the custom configuration model.

9. The system of claim 2, further comprises an event based trigger and a scheduler based trigger to synchronize a data from a source to a destination.