CN116150268A - Cross-system data synchronization method and related equipment - Google Patents
Cross-system data synchronization method and related equipment Download PDFInfo
- Publication number
- CN116150268A CN116150268A CN202211715443.XA CN202211715443A CN116150268A CN 116150268 A CN116150268 A CN 116150268A CN 202211715443 A CN202211715443 A CN 202211715443A CN 116150268 A CN116150268 A CN 116150268A
- Authority
- CN
- China
- Prior art keywords
- target
- data
- field content
- dependency
- synchronized
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
- G06Q10/0875—Itemisation or classification of parts, supplies or services, e.g. bill of materials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Computing Systems (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a cross-system data synchronization method and related equipment, which are used for ensuring the normal operation of a service. The method comprises the following steps: responding to a dependency analysis instruction aiming at target field content, judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is any preset dependency; if the target dependency relationship corresponding to the target field content exists, determining target dependency data corresponding to the target field content in the target dependency relationship; and if the target dependent data is unsynchronized data, synchronizing the target dependent data to a target system, and synchronizing the target field content to the target system.
Description
Technical Field
The embodiment of the application relates to the field of data integration, in particular to a cross-system data synchronization method based on data association analysis and related equipment
Background
Multiple independent business systems are usually deployed simultaneously in a group enterprise, so that each business system can independently process different businesses, but in order to realize the whole-flow management of group enterprise data, cross-system data integration or cross-system data synchronization is usually required between the systems.
But the system integration process is generally faced with the following scenarios: there is a dependency between the different data to be synchronized. For example, cross-system synchronization of business documents generally requires that the underlying data or upstream documents related to the business document be synchronized to the target system first, so as to ensure that the business document can be successfully synchronized to the business system without data synchronization failure caused by business semantic loss.
However, the existing interface-based cross-system data synchronization scheme often cannot ensure that the corresponding dependent data is completed synchronously, so that the data synchronization fails and normal service development is affected.
Disclosure of Invention
The embodiment of the application provides a cross-system data synchronization method and related equipment, which are used for ensuring the normal operation of a service.
A first aspect of an embodiment of the present application provides a method for synchronizing cross-system data, including:
responding to a dependency analysis instruction aiming at target field content, judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is any preset dependency;
if the target dependency relationship corresponding to the target field content exists, determining target dependency data corresponding to the target field content in the target dependency relationship;
and if the target dependent data is unsynchronized data, synchronizing the target dependent data to a target system, and synchronizing the target field content to the target system.
In a specific implementation, the method further includes:
responding to the trigger of the target synchronous task to acquire a target bill;
and determining each field content in the target document as target field content in turn, wherein the target synchronization task is used for synchronizing the field content of the target document from the system to be synchronized to the target system.
In a specific implementation, the method further includes:
if the target dependency relationship corresponding to the target field content does not exist, synchronizing the target field content to the target system;
and if the target dependent data is synchronized data, synchronizing the target field content to the target system.
In a specific implementation, before the responding to the dependency analysis instruction for the target field content, the method further includes:
if synchronization failure information of a target document is received, determining the content of each field to be synchronized in the target document as target field content in turn;
and initiating a dependency analysis instruction for the target field content.
In a specific implementation, the method further includes:
calling an authorization interface of a system to be synchronized based on a system account of the system to be synchronized so as to obtain an authorization credential of the system to be synchronized;
and acquiring the target document from a data interface of the system to be synchronized based on the authorization credential of the system to be synchronized.
In a specific implementation manner, after the determining the target dependency data corresponding to the target field content in the target dependency relationship, the method further includes:
if the historical data table does not exist, the historical data abstract corresponding to the target dependent data is determined to be unsynchronized data.
In a specific implementation, before the determining that the target dependent data is unsynchronized data, the method further includes:
responding to the operation of synchronizing the historical data to the target system, and acquiring a historical data abstract corresponding to the historical data;
and recording the historical data abstract in the historical data abstract table.
A second aspect of the embodiments of the present application provides a data synchronization device, including:
the judging unit is used for responding to a dependency analysis instruction aiming at the target field content and judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is a preset arbitrary dependency;
a determining unit, configured to determine target dependency data corresponding to the target field content in the target dependency relationship if there is the target dependency relationship corresponding to the target field content;
and the synchronization unit is used for synchronizing the target dependent data to a target system and synchronizing the target field content to the target system if the target dependent data is unsynchronized data.
In a specific implementation, the apparatus further includes: an acquisition unit;
the acquisition unit is used for responding to the trigger of the target synchronous task and acquiring a target bill;
the determining unit is further configured to determine each field content in the target document as a target field content in turn, and the target synchronization task is configured to synchronize the field content of the target document from the system to be synchronized to the target system.
In a specific implementation manner, the synchronization unit is further configured to synchronize the target field content to the target system if there is no target dependency relationship corresponding to the target field content;
the synchronization unit is further configured to synchronize the target field content to the target system if the target dependent data is synchronized data.
In a specific implementation, before the responding to the dependency analysis instruction for the target field content, the apparatus further includes: an initiating unit:
the determining unit is further configured to determine, in turn, each field content to be synchronized in the target document as a target field content if synchronization failure information of the target document is received;
the initiating unit is further configured to initiate a dependency analysis instruction for the target field content.
In a specific implementation, the apparatus further includes: calling unit:
the calling unit is used for calling an authorization interface of the system to be synchronized based on a system account of the system to be synchronized so as to obtain an authorization credential of the system to be synchronized;
the acquisition unit is further used for acquiring the target document from a data interface of the system to be synchronized based on the authorization credential of the system to be synchronized.
In a specific implementation manner, after the determining that the target field content corresponds to the target dependency data in the target dependency relationship, the determining unit is further configured to determine that the target dependency data is unsynchronized data if the historical data summary corresponding to the target dependency data does not exist in the historical data table.
In a specific implementation, before the determining that the target dependent data is unsynchronized data, the apparatus further includes: a recording unit:
the acquisition unit is further used for responding to the operation of synchronizing the historical data to the target system and acquiring a historical data abstract corresponding to the historical data;
the recording unit is used for recording the historical data abstract in the historical data abstract table.
A third aspect of the embodiments of the present application provides a data processing apparatus, including:
a central processing unit, a memory and an input/output interface;
the memory is a short-term memory or a persistent memory;
the central processor is configured to communicate with the memory and to execute instruction operations in the memory to perform the method of the first aspect.
A fourth aspect of the embodiments provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method according to the first aspect.
A fifth aspect of the embodiments of the present application provides a computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method according to the first aspect.
From the above technical solutions, the embodiments of the present application have the following advantages: and a dependency analysis instruction aiming at any target field content in the business bill can be initiated, and whether the target dependency corresponding to the target field content exists or not is judged, namely whether corresponding target dependency data needing prior synchronization exists or not is determined. When it is determined that there is target dependent data that needs to be synchronized before and the target dependent data is unsynchronized data, the target dependent data should be synchronized to the target system before the target field content is synchronized to the target system. And determining the dependency relationship of each target field content to be synchronized in real time through the preset dependency relationship so as to ensure the accurate synchronization of the target field content and further ensure the normal service.
Drawings
FIG. 1 is a system architecture diagram of a data synchronization method disclosed in an embodiment of the present application;
FIG. 2 is an exemplary graph of dependencies disclosed in embodiments of the present application;
FIG. 3 is a schematic flow chart of a data synchronization method disclosed in an embodiment of the present application;
FIG. 4 is another flow chart of a data synchronization method disclosed in an embodiment of the present application;
FIG. 5 is a schematic diagram of a data synchronization device according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of another structure of a data synchronization device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The embodiment of the application provides a cross-system data synchronization method based on data association analysis and related equipment, which are used for improving the success rate of data synchronization.
In order to better implement the technical solution of the embodiments of the present application, the embodiments of the present application provide a data synchronization system, which may be used to perform cross-system data synchronization, and synchronize service data to be synchronized from the system to be synchronized to a target system at regular time or as needed. Meanwhile, the data synchronization system may be deployed at any server or terminal, which is not particularly limited herein. The system to be synchronized and the target system are different service systems, the system to be synchronized can be an (SRM, supplier relationship management) system, a manufacturing execution system (MES, manufacturing execution system) or a customer relationship management (CRM, customer relationship management) system, and the target system can be an SRM system, an MES system or a CRM system.
In some embodiments, referring to fig. 1, a processing framework of a data synchronization system in an embodiment of the present application includes: the system comprises a service call layer, a dependency configuration module, a synchronized data storage module, a correlation data analysis and calculation module, a task suspension module, a data pulling task scheduling module and a service execution module.
The document dependency relationship configuration module is used for configuring document dependency relationships, namely, through means of configuring pages or configuration files, the association between any two documents is designated through which field. Referring to fig. 2, fig. 2 is an example of a table dependency relationship. In the example, [ order table. FdeptId ] → [ department table. FId ] is a dependency assignment, and [ order table. FdeptId ] is downstream of [ department table. FId ], that is, if the department table does not include a department record of fId to 001 in the actual data, and the fdeptId in the order table stores a department Id of 001, the field content 001 corresponding to the field fdeptId of the order table cannot be synchronized into the target system due to the loss of service semantics. The service semantic deletion specifically means that the data synchronization system does not know that the fdeptId field of the order table corresponds to the fId field of the department table, and also does not know that the field content of the fdeptId field in the order table of the system to be synchronized should be synchronized as the field content of which field of a plurality of forms in the target system.
The synchronized data storage module is used for storing the service data (such as field contents of different forms) extracted from the system to be synchronized and recording the service data synchronized from the system to be synchronized to the target system, namely the synchronized service data. In practical applications, the recorded synchronized service data may be each service data synchronized from the system to be synchronized to the target system, or a summary of service data synchronized from the system to be synchronized to the target system, which is not limited herein. For example, if the synchronized department table includes a department identifier, a department name, and/or department information of each department, the synchronized business data may include only the department identifier of each department that needs to participate in the dependency analysis, without recording the department name and/or department information of each department, so as to save storage resources.
The service call module is responsible for initiating (or event type passive call) a call to a system to be synchronized at regular time, wherein the call comprises a system interface call or a call of a system database.
The association data analysis and calculation module is used for determining whether the target field content has a corresponding dependency relationship according to the pre-configured dependency relationship, and determining whether a target table pointed to by the target dependency relationship corresponding to the target field content (or the target field content in the corresponding target dependency relationship depends on) has a record of the target field content. For example, the data synchronization system extracts a newly entered document from a purchase table of the system to be synchronized, the field content of the field fdeptId of the document is 001, searches a corresponding target dependency relationship according to the target field content, determines a department table with the target dependency data of the target field content of the target dependency relationship being 001 of the field fId, determines whether the department table with the field content of the field fId being 001 is already synchronized, and if so, indicates that the data dependency relationship is normal; if the new input bill is not synchronized, the written target system is likely to fail due to the fact that the business semantics are lost.
The task suspending module is configured to suspend (suspend to a proxy queue and a corresponding stack) a target synchronization task of a target document to which the target field content belongs if the associated data analysis module finds that the associated data is not synchronized in advance (i.e., the target dependent data corresponding to the target field content is unsynchronized data) in the calculation process. For example, if the department table with field content of 001 in field fId is not synchronized, the target synchronization task needs to be suspended first, a synchronization task for the department table with field content of 001 in field fId is initiated and executed first, and after the synchronization task for the department table with field content of 001 in field fId is completed, the target synchronization task for the target document is continuously executed.
The data pulling task scheduling module is applied to two business scenes: firstly, after the currently executed synchronous task is suspended, initiating an automatic complement dependent data task for a bill corresponding to the currently executed synchronous task. The automatic completion dependent data task can automatically perform recursive scheduling, and complete the dependent data corresponding to each field content in the document corresponding to the currently executed synchronous task (namely, synchronizing the dependent data corresponding to each field content in the corresponding dependent relation to the target system). Wherein the corresponding dependent data comprises direct or indirect dependent data. For example, if the target dependency data (i.e., dependency data) corresponding to the target field content a is document B and the target dependency data corresponding to one field content in document B is document C, the dependency data of the target field content a is document B (direct dependency) and document C (indirect dependency). And secondly, timing scheduling or timing synchronization of the normal scene. For example, the method is pre-configured, and each newly added purchase order in a period of time in the system to be synchronized is written into a sales order corresponding to the target system (one purchase order corresponds to one sales order).
The task execution module is used for executing tasks of pulling data from the system to be synchronized and writing data into the target system.
On the basis of the foregoing data synchronization system, referring to fig. 3, an embodiment of the present application provides a cross-system data synchronization method, which is executed by a server and/or a terminal loading the foregoing data synchronization system, and includes the following steps:
301. and responding to a dependency analysis instruction aiming at the target field content, judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is any preset dependency.
When a dependency analysis instruction for the target field content is received, it should first be determined whether there is a target dependency corresponding to the target field content, that is, whether other data (i.e., target dependency data) needs to be synchronized before determining to synchronize the target field content, to ensure that the target field content can be successfully and accurately synchronized. Specifically, whether other data needs to be synchronized before synchronizing the contents of the target field may be determined by a pre-configured dependency relationship. The target dependency relationship corresponding to the target field content refers to at least one preset dependency relationship, which includes the dependency relationship of the target field content, that is, if one dependency relationship is a dependency relationship a depends on B, it is indicated that the dependency relationship is a dependency relationship corresponding to a, but not a dependency relationship corresponding to B.
In practical application, before performing cross-system synchronization or performing dependency analysis operation, an operator may configure a dependency for a portion of target dependency data that needs to be synchronized before corresponding field content, so that the data synchronization system may perform the dependency analysis operation.
It should be noted that, the data synchronization system may initiate a dependency analysis instruction for each field content in a document after synchronization of the document fails; or after the document synchronization fails, the data synchronization system can acquire the content of each field of the document synchronization failure, and then the data synchronization system can initiate a dependency relationship analysis instruction for the content of each field of the document synchronization failure.
In addition, the target field content can be any basic material. Basic data generally refers to business objects such as people/organizations (departments, users, banks, etc.) or objects (production materials, warehouses, equipment, etc.).
302. And if the target dependency relationship corresponding to the target field content exists, determining target dependency data corresponding to the target field content in the target dependency relationship.
If there is a target dependency relationship corresponding to the target field content, it may be necessary to synchronize the target dependency data corresponding to the target field content in the target dependency relationship before synchronizing the target field content.
Specifically, if the target field content in the target dependency relationship corresponding to the target field content is downstream data, that is, it is stated that the target dependency data corresponding to the target field content in the target dependency relationship is completed in advance, the target field content can be successfully synchronized to the target system. Therefore, it is necessary to determine the target dependency data corresponding to the target field content in the target dependency relationship. Wherein the target dependent data may be any underlying material or any upstream document.
In addition, if the target field content in the target dependency relationship corresponding to the target field content is downstream data, that is, synchronization of the target field content can be completed without synchronizing other data in advance.
It should be noted that, if there are multiple corresponding target dependencies, the flow of this step is executed for each target dependency.
303. If the target dependent data is unsynchronized data, synchronizing the target dependent data to the target system and synchronizing the target field content to the target system.
Further, whether the target dependent data is synchronized needs to be determined, and if so, the content of the target field can be directly synchronized to the target system; if the target dependent data is not synchronized, the corresponding target dependent data is synchronized to the target system, and then the target field content is synchronized, so that the successful and accurate synchronization of the target field content can be completed.
It should be noted that, if there are a plurality of corresponding target dependent data, the flow of this step is executed for each target dependent data.
In the embodiment of the application, a dependency analysis instruction for any target field content in the business document can be initiated, and whether the target dependency corresponding to the target field content exists or not is judged, namely whether corresponding target dependency data needing to be synchronized in advance exists or not is determined. When it is determined that there is target dependent data that needs to be synchronized before and the target dependent data is unsynchronized data, the target dependent data should be synchronized to the target system before the target field content is synchronized to the target system. And determining the dependency relationship of each target field content to be synchronized in real time through the preset dependency relationship so as to ensure the accurate synchronization of the target field content and further ensure the normal service.
In some embodiments, the dependency analysis for a document or underlying material may be initiated before it is synchronized, as follows: mode one: responding to the trigger of the target synchronous task to acquire a target bill; determining each field content in the target document as target field content in turn, wherein a target synchronization task is used for synchronizing the field content of the target document from a system to be synchronized to a target system; if the target dependency relationship corresponding to the target field content does not exist, synchronizing the target field content to a target system; and if the target dependent data is synchronized data, synchronizing the target field content to the target system. Mode two: if the synchronization failure information of the target document is received, determining the content of each field to be synchronized in the target document as target field content in turn; a dependency analysis instruction is initiated for the target field content.
Specifically, in the first mode, when the target document needs to be synchronized to the target system, each field content to be synchronized in the target document is processed in turn, the steps 301 to 303 are executed sequentially for each target field content, and according to the steps, the target field content for which no corresponding dependency relationship exists or for which the corresponding dependency data is synchronized to the target system. In the second mode, the steps and processes described in the first mode are executed only for the target document that fails to synchronize. In addition, when the target dependent data is unsynchronized data, the target dependent data needs to be synchronized to the target system and then the target field content needs to be synchronized to the target system; for the case that no corresponding target dependency relationship exists and the corresponding target dependency data bit has synchronized data, the army can directly synchronize the target field content to the target system.
Further, considering the efficiency and reliability of the dependency analysis, the embodiment of the application further includes the following steps: responding to the operation of synchronizing the historical data to a target system, and acquiring a historical data abstract corresponding to the historical data; the historical data summary is recorded in a historical data summary table. Further, if the historical data summary table does not exist, the historical data summary corresponding to the target dependent data determines that the target dependent data is unsynchronized data.
Specifically, whether the target dependent data is unsynchronized data may be determined based on the history data digest in which the synchronized history data is recorded in the history data digest table. Wherein the history data digest is any information describing each synchronized history data. For example, the department data of the department 101 is synchronized, and then the department 101 need only be recorded in the history data summary table.
The following describes the data synchronization method according to the embodiment of the present application in a specific scenario. A practical scenario between a manufacturing enterprise and its clients is described here as an example. The customer places an order for a production enterprise to purchase a certain product, the customer places a purchase order through the own business system, the business system of the production enterprise corresponds to the transaction and places a sales order, the integration of the two systems can enable the rapid and efficient collaboration among enterprises, the purchase order in the customer system is synchronized to the business system of the production enterprise, and the corresponding sales order is automatically generated. Further, the data synchronization further includes, but is not limited to, the production enterprise having to purchase production materials from suppliers when producing according to sales orders, at which time the purchase orders of the production enterprise may be automatically synchronized to the corresponding suppliers' business systems, where sales orders of the suppliers are generated; the integration can create an efficient collaborative information system of an upstream and downstream industrial chain of the enterprise, and the business processing period is greatly shortened compared with the traditional paper ordering process; the 2 service systems can be target systems, and according to different service scenarios, the data synchronization directions of the two parties can be interchanged (for example, the synchronization from the A system to the B system is changed into the synchronization from the B system to the A system).
First, the dependency relationship between the document and the underlying material (as in fig. 2) and/or the dependency relationship between the underlying material and the underlying material are configured in the data synchronization system. For example, the department ID field points to the department base and the material ID points to the material table.
It should be noted that, the bill and the basic data are concepts describing the service scene; general basic data refers to business objects such as people/organizations (departments, users, banks, etc.), things (production materials, warehouse, equipment, etc.); documents are descriptions of business process states, such as purchase orders, sales orders, and the like, and are process documents; the two concepts are introduced in this embodiment to facilitate description of a business scenario, and the implementation process of the technical scheme of this embodiment only focuses on the dependency relationship between objects, and treats documents and basic materials equally (the basic materials may depend on other basic materials, such as production materials associated with a storage warehouse).
The embodiment is implemented as follows, and first, initialization of the data synchronization system is performed. 1. The method comprises the steps that documents, basic data form objects and dependency relations related to business scenes of a business system (a system to be synchronized and a target system) of both sides are configured in a data synchronization system; 2. completing the creation of an intermediate storage table of the data synchronization system; 3. and completing the relevant system to be synchronized and the target system access parameter configuration, including but not limited to necessary account numbers, passwords, ip addresses, interface addresses and/or the like.
And then, the timing scheduling (or the active calling of the business system) of the data synchronization system initiates a synchronization task, the task execution module initiates service calling according to an integration scene, and the service calling module actually executes specific business system interface calling.
Then, after the data synchronization system retrieves the data to be synchronized from the interface of the system to be synchronized, the associated data analysis and calculation module carries out associated analysis on the data according to the configured dependence relationship (between the system to be synchronized and the target system), if the unsynchronized dependence data is found, the current task is suspended to a suspension queue (the node type is a stack), and if the associated data has the dependence data which is not uploaded, the task suspended before is found in the suspension queue, and a new suspension task is pressed in the stack; when the last-stage dependent data synchronization is successful, the suspended task is popped from the stack, the suspended task is sequentially re-executed until the stack is empty, and finally the suspended task is cleaned.
Then, the service execution module of the data synchronization system writes the data to be synchronized (which can be the field content in the basic material or the document) into the target system by calling the service calling module;
finally, the data of the system to be synchronized is read and written into the target system, and the data is actually executed by the service calling module; the basic reading process is that a configured system account number is obtained, an authorization interface of a service system is called to obtain an authorization certificate of the service system, which is generally a token (namely, an authorization certificate), and then the token is utilized to access an interface of a specified service (namely, an interface of a system to be synchronized); or under the condition of directly reading the service system database, the information such as the configured database access account number, access address port and the like is utilized to directly read the corresponding service table, and service data (such as service documents, basic materials and the like newly built/updated in the latest period) meeting the conditions are returned; the authorization portion of the write is the same, except that a data write operation is performed.
In other implementations, considering that dependent data, especially basic data, is usually already synchronized to a target system in advance, in order to reduce the problem of reduced synchronization performance caused by performing dependency analysis before each synchronization, the required computation power for data synchronization is greatly reduced by immediately writing the data to be synchronized into the target system after the data to be synchronized is extracted from the system to be synchronized, and performing related processes (determining the target dependency and the corresponding target dependency data) such as the dependency analysis only on the data to be synchronized that fails to be synchronized.
The basic data updating frequency is lower, the service bill updating frequency is higher, the system integration based on non-event cannot ensure that the dependent data is synchronous to the target system before the dependent data is synchronous to the target system, the data synchronization failure is caused when the dependent data is not synchronous to the target system in advance, the general processing method is to increase the basic data synchronization frequency, but the method can not put an end to the problem, and meanwhile, because the system service is frequently called, extra pressure is added to the service system (such as a system to be synchronized and/or the target system), and the target service system is possibly crashed. In this embodiment, through the independent analysis process of the dependent data of the data synchronization system, the target dependent data corresponding to the target field content can be synchronized to the target system first, and under the condition that no additional pressure is added, the successful and accurate synchronization of the target field content is effectively ensured. Meanwhile, the method can accurately identify that the linkage data synchronization failure is caused by the failure of which data (which target field content) and provide accurate problem analysis for the problem investigation personnel.
Referring to fig. 5, an embodiment of the present application provides a data synchronization device, including:
a judging unit 501, configured to judge whether a target dependency relationship corresponding to the target field content exists in response to a dependency relationship analysis instruction for the target field content, where the target dependency relationship is a preconfigured arbitrary dependency relationship;
a determining unit 502, configured to determine target dependency data corresponding to the target field content in the target dependency relationship if there is the target dependency relationship corresponding to the target field content;
and the synchronization unit 503 is configured to synchronize the target dependent data to the target system and synchronize the target field content to the target system if the target dependent data is unsynchronized data.
In a specific implementation, the apparatus further includes: an acquisition unit;
the acquisition unit is used for responding to the trigger of the target synchronous task and acquiring a target bill;
the determining unit 502 is further configured to determine each field content in the target document as a target field content in turn, and the target synchronization task is configured to synchronize the field content of the target document from the system to be synchronized to the target system.
In a specific implementation manner, the synchronization unit 503 is further configured to synchronize the target field content to the target system if there is no target dependency relationship corresponding to the target field content;
the synchronization unit 503 is further configured to synchronize the target field content to the target system if the target dependent data is synchronized data.
In one particular implementation, before responding to the dependency analysis instruction for the target field content, the apparatus further comprises: an initiating unit:
the determining unit 502 is further configured to determine, in turn, each field content to be synchronized in the target document as a target field content if synchronization failure information of the target document is received;
and the initiating unit is also used for initiating a dependency analysis instruction aiming at the content of the target field.
In a specific implementation, the apparatus further includes: calling unit:
the calling unit is used for calling an authorization interface of the system to be synchronized based on the system account number of the system to be synchronized so as to obtain an authorization credential of the system to be synchronized;
the acquisition unit is also used for acquiring the target document from the data interface of the system to be synchronized based on the authorization credential of the system to be synchronized.
In a specific implementation manner, after determining the target dependency data corresponding to the target field content in the target dependency relationship, the determining unit 502 is further configured to determine that the target dependency data is unsynchronized data if the historical data summary corresponding to the target dependency data does not exist in the historical data table.
In one specific implementation, before determining that the target dependent data is unsynchronized data, the apparatus further comprises: a recording unit:
the acquisition unit is also used for responding to the operation of synchronizing the historical data to the target system and acquiring a historical data abstract corresponding to the historical data;
and the recording unit is used for recording the historical data abstract in the historical data abstract table.
Fig. 6 is a schematic structural diagram of a data synchronization device according to an embodiment of the present application, where the data synchronization device 600 may include one or more central processing units (central processing units, CPU) 601 and a memory 605, and one or more application programs or data are stored in the memory 605.
Wherein the memory 605 may be volatile storage or persistent storage. The program stored in the memory 605 may include one or more modules, each of which may include a series of instruction operations in the data synchronization device. Still further, the central processor 601 may be configured to communicate with the memory 605 to execute a series of instruction operations in the memory 605 on the data synchronizer 600.
The data synchronization device 600 may also include one or more power supplies 602, one or more wired or wireless network interfaces 603, one or more input/output interfaces 604, and/or one or more operating systems, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.
The cpu 601 may perform the operations performed by the data synchronization device in the embodiments shown in fig. 1 to 5, and detailed descriptions thereof are omitted herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform a cross-system data synchronization method as described above.
Claims (10)
1. A method for synchronizing data across systems, comprising:
responding to a dependency analysis instruction aiming at target field content, judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is any preset dependency;
if the target dependency relationship corresponding to the target field content exists, determining target dependency data corresponding to the target field content in the target dependency relationship;
and if the target dependent data is unsynchronized data, synchronizing the target dependent data to a target system, and synchronizing the target field content to the target system.
2. The method according to claim 1, wherein the method further comprises:
responding to the trigger of the target synchronous task to acquire a target bill;
and determining each field content in the target document as target field content in turn, wherein the target synchronization task is used for synchronizing the field content of the target document from the system to be synchronized to the target system.
3. The method according to claim 1, wherein the method further comprises:
if the target dependency relationship corresponding to the target field content does not exist, synchronizing the target field content to the target system;
and if the target dependent data is synchronized data, synchronizing the target field content to the target system.
4. The method of claim 1, wherein prior to said responding to the dependency analysis instruction for the target field content, the method further comprises:
if synchronization failure information of a target document is received, determining the content of each field to be synchronized in the target document as target field content in turn;
and initiating a dependency analysis instruction for the target field content.
5. The method according to any one of claims 1 to 4, further comprising:
calling an authorization interface of a system to be synchronized based on a system account of the system to be synchronized so as to obtain an authorization credential of the system to be synchronized;
and acquiring the target document from a data interface of the system to be synchronized based on the authorization credential of the system to be synchronized.
6. The method of claim 1, wherein after said determining the target dependency data corresponding to the target field content in the target dependency relationship, the method further comprises:
if the historical data summary table does not exist, determining that the target dependent data is unsynchronized data according to the historical data summary corresponding to the target dependent data.
7. The method of claim 6, wherein prior to said determining that the target-dependent data is unsynchronized data, the method further comprises:
responding to the operation of synchronizing the historical data to the target system, and acquiring a historical data abstract corresponding to the historical data;
and recording the historical data abstract in the historical data abstract table.
8. A data synchronization device, comprising:
the judging unit is used for responding to a dependency analysis instruction aiming at the target field content and judging whether a target dependency corresponding to the target field content exists or not, wherein the target dependency is a preset arbitrary dependency;
a determining unit, configured to determine target dependency data corresponding to the target field content in the target dependency relationship if there is the target dependency relationship corresponding to the target field content;
and the synchronization unit is used for synchronizing the target dependent data to a target system and synchronizing the target field content to the target system if the target dependent data is unsynchronized data.
9. A data synchronization device, comprising:
a central processing unit, a memory and an input/output interface;
the memory is a short-term memory or a persistent memory;
the central processor is configured to communicate with the memory and to execute instruction operations in the memory to perform the method of any of claims 1 to 7.
10. A computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211715443.XA CN116150268A (en) | 2022-12-29 | 2022-12-29 | Cross-system data synchronization method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211715443.XA CN116150268A (en) | 2022-12-29 | 2022-12-29 | Cross-system data synchronization method and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116150268A true CN116150268A (en) | 2023-05-23 |
Family
ID=86361197
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211715443.XA Pending CN116150268A (en) | 2022-12-29 | 2022-12-29 | Cross-system data synchronization method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116150268A (en) |
-
2022
- 2022-12-29 CN CN202211715443.XA patent/CN116150268A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11422853B2 (en) | Dynamic tree determination for data processing | |
| US11243928B2 (en) | Method and system for cloning enterprise content management systems | |
| EP3049968B1 (en) | Master schema shared across multiple tenants with dynamic update | |
| US9996593B1 (en) | Parallel processing framework | |
| US7328213B2 (en) | Transaction processing method, transaction control apparatus and program thereof | |
| JP2016541056A (en) | Computer apparatus, method and apparatus for scheduling business flows | |
| JP4141875B2 (en) | Recovery processing method, its execution system, and its processing program | |
| RU2501069C2 (en) | Asynchronous multi-level undo support in javascript grid | |
| US10956278B2 (en) | Intelligent captain selection for disaster recovery of search head cluster | |
| WO2021082925A1 (en) | Transaction processing method and apparatus | |
| US11294917B2 (en) | Data attribution using frequent pattern analysis | |
| US20060031194A1 (en) | Decision support implementation for workflow applications | |
| CN116150268A (en) | Cross-system data synchronization method and related equipment | |
| US10728323B2 (en) | Method and apparatus for operating infrastructure layer in cloud computing architecture | |
| CN115905151A (en) | Method, system and device for querying circulation information based on backup log | |
| WO2018200167A1 (en) | Managing asynchronous analytics operation based on communication exchange | |
| CN109635040B (en) | Real-time data migration method and device and storage medium | |
| US11836125B1 (en) | Scalable database dependency monitoring and visualization system | |
| CN113296847A (en) | Workflow engine implementation method based on self-analysis node | |
| CN115269161B (en) | Abnormal process reverse rollback method and system | |
| CN109005059A (en) | A kind of system and method for realizing Redis automated back-up | |
| CN113704254B (en) | Method and device for processing database business, electronic equipment and storage medium | |
| CN112732415B (en) | Transaction processing method, device and equipment based on resource exchange proxy system | |
| CN111464580B (en) | Method and device for selecting main server | |
| CN115168487A (en) | Data synchronization method, assembly, equipment and medium based on button |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |