Configuration data synchronization method

Abstract

The invention provides a configuration data synchronization method, which comprises the following steps of S1, according to a timing starting rule set in a synchronization configuration file, after a data synchronization task is triggered in a timing manner, reading system information tables, issuing data interface URL (Uniform Resource Locator) information tables, table field mapping tables and field conversion tables of all upstream applications; and the data synchronization task can be automatically and regularly triggered through a timing starting rule set in the synchronization configuration file. Through intelligent configuration, flexibility and reliability of data synchronization are achieved, configuration efficiency improvement, expandability, user friendliness and centralized management are achieved, the requirement for manual intervention is reduced through the mode, it is ensured that a data synchronization task is executed on time, and the automation level and efficiency of the system are further improved.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and more specifically, to a method for synchronizing configured data.

[0002] With the in-depth development of digital transformation, the IT architectures of modern enterprises are becoming increasingly complex. There are many legacy systems and emerging modern cloud services existing simultaneously within many enterprises. Although this hybrid architecture can meet the business requirements at different stages, it also brings severe data management challenges. Especially in terms of data synchronization, due to the large number of systems and the diverse characteristics of data sources and targets, enterprises often need to migrate or synchronize data from one system to another, which requires the ability to adapt to different types of databases, communication protocols, and diverse data formats, including common relational databases such as MySQL and Oracle, non-relational databases such as MongoDB, and different data formats such as JSON and XML.

[0003] In the traditional mode, enterprises rely on professional developers to write code to achieve data synchronization, and a dedicated tool needs to be independently developed for the data synchronization of each set of systems. Taking SQL statements as an example, they are usually fixedly written in the code and it is difficult to flexibly respond to changes in different data sources. Similarly, the data conversion logic between systems is also hard-coded in the program. If a system needs to synchronize data with multiple systems of different database types, developers have to develop multiple independent synchronization tools, which undoubtedly greatly increases the development cost and time cost.

[0004] By deeply analyzing the current situation of enterprise system synchronization tools, it is not difficult to find a series of significant problems. First of all, poor usability is a major pain point. Whenever a synchronization task for adding a table or field is required, developers have to repeatedly write the relevant update code, which is not only cumbersome but also error-prone. Secondly, in terms of data format conversion, there is a lack of a standardized processing mechanism. Most of the existing systems write the data conversion logic in the code in a fixed manner, making it difficult to quickly and flexibly adapt and convert when facing different formats of data. Moreover, poor scalability is also a prominent problem. The existing data synchronization tools are not flexible enough. When facing complex scenarios with multiple data sources, adapters need to be repeatedly developed to meet the data synchronization requirements between different systems, which greatly limits the scope of application and scalability of the tools. At the same time, the phenomenon of tool fragmentation is serious. Each data synchronization scenario may require the independent development of a set of tools, which not only increases the development workload but also makes the subsequent operation and maintenance work extremely complex, greatly increasing the operation cost of enterprises. In addition, the monitoring and error recovery capabilities of synchronization tasks are insufficient. When an error occurs during the data synchronization process, the system often cannot monitor, warn, and automatically recover in a timely and effective manner, which may lead to data loss or inconsistency, thereby affecting the normal operation and decision-making of enterprises.

[0005] In summary, current enterprises face many challenges in data synchronization and urgently need a new data synchronization solution that is more efficient, flexible, intelligent and has strong monitoring and error recovery capabilities to cope with the increasingly complex enterprise IT architecture and diverse data synchronization requirements.

[0006] Therefore, developing a synchronization method for configured data has become an important technical requirement today. Summary of the Invention

[0007] The technical problem to be solved by the present invention is to provide a synchronization method for configured data that supports multiple data sources and targets and automatically processes data conversion in view of the deficiencies in the above technical solutions.

[0008] The present invention provides a synchronization method for configured data, and the method includes the following steps:

[0009] S1. According to the scheduled start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals, and then read the system information tables of all upstream applications, the issued data interface URL information tables, the table field mapping tables, and the field conversion tables.

[0010] S2. Based on the information in the application information table, create threads for each downstream application that needs to be synchronized in turn, import the system information tables of each upstream application, the issued data interface URL information tables, the table field mapping tables, and the field conversion tables into the corresponding application threads, and loop to process the data synchronization tasks of each application thread.

[0011] S3. Traverse the upstream application issued data interfaces corresponding to the configured applications, call the issued data interfaces in turn to obtain the issued data. If there is no issued data, continue to call the next issued data interface. If there is issued data, when the issued data is obtained, write the obtained issued data into the receiving log table, generate SQL statements according to the configured table field mapping and field conversion data, and execute the data synchronization task to the downstream application database and then continue to call the next interface.

[0012] In the synchronization method for configured data of the present invention; in the step S1, according to the scheduled start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of table field mapping data through the graphical interface or directly in the system information table.

[0013] In the synchronization method for configured data of the present invention; in the step S1, according to the scheduled start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of issued data interfaces through the graphical interface or directly in the issued data interface URL information table.

[0014] In the method for synchronizing configured data according to the present invention; in step S1, according to the scheduled start rule set in the synchronization configuration file, a data synchronization task is triggered at regular intervals. For each additional synchronization of an upstream application, one or more lines of table field mapping data are added through a graphical interface or directly in the field mapping table.

[0015] In the method for synchronizing configured data according to the present invention; in step S1, according to the scheduled start rule set in the synchronization configuration file, a data synchronization task is triggered at regular intervals. For each additional synchronization of an upstream application, one or more lines of data are added through a graphical interface or directly in the field conversion table.

[0016] In the method for synchronizing configured data according to the present invention; step S2 includes the following steps:

[0017] S21, traverse the downstream data interfaces issued by the upstream applications corresponding to the configured applications, and determine whether there are any unsynchronized downstream data interfaces. If so, call the downstream data interfaces in sequence to obtain the downstream data, and determine whether there is any obtained downstream data; if there is no obtained downstream data, continue to call the next downstream data interface. If there is obtained downstream data, write the obtained downstream data into the receiving log table when the data is obtained.

[0018] In the method for synchronizing configured data according to the present invention; step S3 includes the following steps:

[0019] S31, receive the unprocessed downstream data in the receiving log table, and determine whether the received downstream data has a deletion flag. When a deletion flag is detected, obtain the values of the associated fields according to the received downstream data based on the configured system information table and table field mapping, and generate a query SQL statement and a deletion SQL statement.

[0020] In the method for synchronizing configured data according to the present invention; step S3 further includes the following steps:

[0021] S32, perform operations on the query SQL statement and the deletion SQL statement in the downstream application database, and write the obtained downstream data and the deletion SQL statement in the query into the SQL log table. If the deletion is successful, write the SQL statement into the log table recording the success of the SQL. If the deletion fails, record the error information and the executed SQL statement.

[0022] In the method for synchronizing configured data according to the present invention; step S3 further includes the following steps:

[0023] S33. Receive the unprocessed downstream data in the log table and determine whether the received downstream data has a deletion flag. When no deletion flag is detected, configure the corresponding system information table and table field mapping according to the received downstream data, obtain the values of the associated fields, and generate a query SQL statement.

[0024] In the method for synchronizing configuration data according to the present invention; the step S3 further includes the following steps:

[0025] S34. Execute the operation of finding the SQL statement in the downstream application database. If the data does not exist, obtain the values of the fields to be inserted according to the configured system information table, table field mapping, and field conversion table information, generate an insert SQL statement and execute the insert. If the insert is successful, write the SQL statement into the log table recording the success of SQL. If the insert fails, record the error information and the executed SQL statement. If the data exists, obtain the values of the associated fields and the values of the fields to be updated according to the configured system information table, table field mapping, associated fields, and field conversion table information, generate an update SQL and execute it. If the update is successful, write the SQL into the log table recording the success of SQL. If the update fails, record the error information and the executed SQL statement.

[0026] The method for synchronizing configuration data of the present invention can automatically trigger the data synchronization task regularly by synchronizing the scheduled start rule set in the synchronization configuration file. Through intelligent configuration, the flexibility and reliability of data synchronization are achieved. It has improved configuration efficiency, scalability, user-friendliness, and centralized management. This method reduces the need for manual intervention, ensures that the data synchronization task is executed on time, and also improves the automation level and efficiency of the system. Brief Description of the Drawings

[0027] Figure 1 is a schematic flowchart of the method for synchronizing configuration data of the present invention. Detailed Embodiment

[0028] In order to make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification, claims and above-mentioned drawings of the present invention are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present invention described here can be implemented in an order other than those illustrated or described here. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, application, product or device that includes a series of steps or units does not necessarily limit to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0030] As Figure 1 shown, Figure 1 is a schematic flowchart of an embodiment of the method for synchronizing configuration data of the present invention. A method for synchronizing configuration data is provided, including the following steps:

[0031] In step S1, according to the timing start rule set in the synchronization configuration file, after triggering the data synchronization task at a fixed time, read the system information tables of all upstream applications, the issued data interface URL information tables, the table field mapping tables and the field conversion tables;

[0032] In step S2, based on the information in the application information table, create threads for each downstream application that needs to be synchronized in turn, import the system information tables of each upstream application, the issued data interface URL information tables, the table field mapping tables and the field conversion tables into the corresponding application threads, and loop to process the data synchronization tasks of each application thread;

[0033] In step S3, traverse the upstream application issued data interfaces corresponding to the configured applications, call the issued data interfaces in turn to obtain the issued data. If there is no issued data, continue to call the next issued data interface. If there is issued data, when the issued data is obtained, write the obtained issued data into the receiving log table, generate SQL statements according to the configured table field mapping and field conversion data, and execute the data synchronization task to the downstream application database and then continue to call the next interface. The purpose of writing into the receiving log table is for tracking in case of problems.

[0034] In this embodiment, in step S1, according to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at a fixed time. For each additional synchronization of an upstream application, add one or more rows of table field mapping data through the graphical interface or directly in the system information table.

[0035] In this embodiment, in step S1, according to the timing start rule set in the synchronization configuration file, the data synchronization task is triggered at regular intervals. For each additional upstream application synchronization, one or more rows of downstream data interface are added through the graphical interface or directly in the downstream data interface URL information table.

[0036] In this embodiment, in step S1, according to the timing start rule set in the synchronization configuration file, the data synchronization task is triggered at regular intervals. For each additional upstream application synchronization, one or more rows of table field mapping data are added through the graphical interface or directly in the field mapping table.

[0037] In this embodiment, in step S1, according to the timing start rule set in the synchronization configuration file, the data synchronization task is triggered at regular intervals. For each additional upstream application synchronization, one or more rows of data are added through the graphical interface or directly in the field conversion table.

[0038] In this embodiment, step S2 includes the following steps:

[0039] In step S21, traverse the downstream data interfaces of the configured applications corresponding to the upstream applications, and determine whether there are unsynchronized downstream data interfaces. If so, call the downstream data interfaces in sequence to obtain the downstream data, and determine whether there is any obtained downstream data; if there is no obtained downstream data, continue to call the next downstream data interface. If there is obtained downstream data, write the obtained downstream data into the receiving log table when the data is obtained.

[0040] In this embodiment, step S3 includes the following steps:

[0041] In step S31, receive the unprocessed downstream data in the receiving log table, and determine whether the received downstream data has a deletion flag. When a deletion flag is detected, obtain the values of the associated fields according to the received downstream data based on the configured system information table and table field mapping, and generate a query SQL statement and a deletion SQL statement.

[0042] In this embodiment, step S3 further includes the following steps:

[0043] In step S32, perform operations on the query SQL statement and the deletion SQL statement in the downstream application database, and write the obtained downstream data and the deletion SQL statement into the SQL log table. If the deletion is successful, write the SQL statement into the log table recording the SQL success. If the deletion fails, record the error information and the executed SQL statement. The purpose of writing into the SQL log table is to facilitate tracking after problems occur.

[0044] In this embodiment, step S3 further includes the following steps:

[0045] In step S33, receive the unprocessed downstream data in the log table, and determine whether the received downstream data has a deletion flag. When no deletion flag is detected, configure the corresponding system information table and table field mapping according to the received downstream data, obtain the values of the associated fields, and generate a query SQL statement.

[0046] In this embodiment, step S3 further includes the following steps:

[0047] In step S34, perform an operation to find the SQL statement in the downstream application database. If the data does not exist, obtain the values of the fields to be inserted according to the configured corresponding system information table, table field mapping, and field conversion table information, generate an insert SQL statement and execute the insertion. If the insertion is successful, write the SQL statement to the log table recording SQL success. If the insertion fails, record the error information and the executed SQL statement. If the data exists, obtain the values of the associated fields and the fields to be updated according to the configured corresponding system information table, table field mapping, associated fields, and field conversion table information, generate an update SQL and execute it. If the update is successful, write the SQL to the log table recording SQL success. If the update fails, record the error information and the executed SQL statement.

[0048] In step S1, according to the timing start rule set in the synchronization configuration file YML, trigger the data synchronization task regularly, as follows: execute once every 3 minutes from 8 am to 23 pm. Each time of regular synchronization, for example, when synchronizing and starting every 5 minutes, read all application information and the field configuration information of the application again. The purpose of this setting is to add a new application information and the field configuration of this application. For each additional synchronization configuration of an application, there is no need to restart the service. Then, when the next timing task starts, the synchronization configuration of this application will also be automatically read to perform data synchronization for this application.

[0049] Among them, the fields of the application system information table are as follows:

[0050]

[0051]

[0052] For each additional synchronization of an application, add a row of data through the graphical interface or directly in this table.

[0053] After the system starts, start the data synchronization task regularly according to the service configuration time. According to the number of records in this table, create an application synchronization thread and add it to the thread pool. And according to the database driver configuration, create a database connection through JDBC. Prepare for synchronizing the databases of each downstream system.

[0054] Upstream application downstream data interface information table.

[0055] The fields are as follows:

[0056] ID Globally unique identifier

[0057] URL Upstream application API address (data distribution interface)

[0058] appCode Application code of the upstream application

[0059] For each additional synchronization of the upstream application, the upstream application involves one or more data distribution interface urls. Add one or more rows of data distribution interfaces in the table through the graphical interface or directly in this table.

[0060] According to the appCode, client_id, client_secret of the upstream application configured in the system information table and the URL upstream application data distribution interface of Configuration 2, obtain the distributed data. For multiple URLs, loop to obtain the distributed data of each interface. Store the read distributed data in the receiving data table for convenient problem tracking

[0061] Table field mapping table

[0062] The fields are as follows:

[0063] ID, APP_ID, URL, TABLENAME, INSERT, UPDATE, RELATION

[0064]

[0065]

[0066] As follows:

[0067] id: ROLE_ID, code: ROLE_CODE, name: ROLE_NAME, xx: tenant_id, remark: ROLE_DESC, status: role_enabled, creator: creator, createTime: ctime, updater: editor, updateTime: utime

[0068] Before the colon is the field of the upstream application distribution interface, and after the colon is the field of the downstream application distribution interface. Multiple are separated by commas

[0069] UPDATE Update operation field mapping

[0070] As follows:

[0071] id: ROLE_ID, code: ROLE_CODE, name: ROLE_NAME, xx: tenant_id, remark: ROLE_DESC, status: role_enabled, updater: editor, updateTime: utime

[0072] The fields before the colon are the interface fields sent by the upstream application, and the fields after the colon are the interface fields sent by the downstream application. Multiple fields are separated by commas

[0073] The RELATION field is used to perform updates or deletes on associated fields

[0074] id: ROLE_ID

[0075] The fields before the colon are the interface fields sent by the upstream application, and the fields after the colon are the interface fields sent by the downstream application. Multiple fields are separated by commas

[0076] For each additional downstream application synchronization, where the downstream application involves the synchronization of one or more tables, and the table or tables to be synchronized come from one data interface URL sent by the upstream application, add one or more rows of table field mapping data through the graphical interface or directly in the table

[0077] The fields of the field conversion table are as follows

[0078] ID, APP_ID, TABLENAME, FIELD_NAME, Source_Value, Target_Value

[0079]

[0080] For each additional field data conversion, add one row of data through the graphical interface or directly in the table

[0081] If the Source_Value value s is configured as empty and the Target_Value is configured as non-empty, it means that the field will be updated to the configured value of the default Target_Value

[0082] For the downstream application app1, in the sys_menu table, for the field menu_type, when receiving data 1 from the upstream application

[0083] Convert it to M and synchronize and save it to the field menu_type in the sys_menu table

[0084] It is also possible to configure a certain field with Source_Value as empty and Target_Value as a specified value

[0085] It means that the default value of this field is the value specified by Target_Value. If the value of this field in the data sent by the upstream application is empty, the value specified by Target_Value is used to update the corresponding field in the downstream application database.

[0086] Based on the received data, the configured tables, fields, and the sent values, find the converted values and convert them to the corresponding values when generating SQL.

[0087] Specifically, by synchronizing the scheduled start rules set in the configuration file, this application can automatically trigger data synchronization tasks regularly. This method reduces the need for manual intervention, ensures that the data synchronization tasks are executed on time, and improves the automation level and efficiency of the system. It supports adding and modifying information through a graphical interface or directly in the table to add new upstream application synchronization configurations, sent data interfaces, field mappings, and field conversion rules. This flexibility enables the system to be quickly adjusted according to business requirements, enhancing the adaptability and scalability of the system. Create independent application threads for each downstream application that needs to be synchronized, and import the relevant configuration information into the corresponding application threads to achieve parallel processing of multiple tasks. This not only improves the speed of data synchronization but also effectively utilizes system resources and improves the overall performance. By traversing the data interfaces sent by the upstream application, call to obtain data in sequence, and decide whether to continue calling the next interface according to the actual situation (whether there is data). If there is data, write it immediately into the receiving log table and generate the corresponding SQL statements for data synchronization. This process ensures the efficiency and accuracy of data processing, and is also convenient for problem tracking and auditing. Whether it is an insert, update, or delete operation, the system will record in detail whether the SQL execution is successful and any error information. This comprehensive logging mechanism helps to quickly locate the problem, ensuring data integrity and system stability. It can dynamically generate SQL statements suitable for the target database according to the preset field mappings and field conversion rules, thus supporting complex data structure conversion requirements and improving the accuracy and reliability of data synchronization.

[0088] Through intelligent configuration, this solution achieves a high degree of flexibility and reliability in data synchronization. With an intuitive graphical interface and direct table operation functions, users can easily add or modify upstream application synchronization configurations, issue data interface information, field mapping, and conversion rules. This design significantly simplifies the configuration process, reduces setup time, and improves work efficiency. This application supports dynamically adding new synchronization tasks without restarting the service and can automatically adapt to new configurations to take effect when the next scheduled task starts. This enables the system to flexibly respond to the growing business needs and ensure long-term stable operation. Using a user-friendly graphical interface for configuration management reduces the technical threshold, enabling non-technical personnel to efficiently complete complex configuration tasks and greatly enhancing the user operation experience. All synchronization-related configuration information (including system information tables, issued data interface URL information tables, table field mapping tables, and field conversion tables) is centrally managed for easy unified maintenance and monitoring. This feature not only simplifies daily management work but also enhances the controllability and security of the system.

[0089] This application provides a highly configurable system that allows users to easily set up synchronization tasks, supports multiple data sources and targets, and automatically processes data conversion. It can conveniently and dynamically expand the data synchronization of multiple subsystems according to the growing business needs.

[0090] In summary, this application provides a highly flexible and reliable automated data synchronization solution that optimizes the entire data synchronization process through intelligent configuration, is applicable to various application scenarios that require cross-system and cross-database data synchronization, and meets the high requirements of modern enterprises for data processing efficiency and accuracy.

[0091] The beneficial effects of a method for synchronizing configured data provided by an embodiment of the present invention are at least as follows:

[0092] 1. Compared with the traditional development mode, this application can significantly shorten the task creation time by more than 85%, significantly improving the development efficiency.

[0093] 2. This application has excellent scalability. It not only supports the synchronization expansion of multiple tables within a single application but also enables the expansion of multiple fields in a certain table, flexibly meeting diverse data synchronization requirements.

[0094] 3. This application has strong adaptability, can be compatible with multiple data sources, and supports the synchronization expansion of multiple applications, easily coping with complex business scenarios.

[0095] 4. By establishing a unified data synchronization task configuration center, this application has a centralized synchronization task monitoring function, and at the same time has a convenient problem query and tracking processing ability, greatly optimizing the system management and maintenance experience.

[0096] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should be aware that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0097] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0098] Therefore, as described above, the above are only the preferred specific embodiments of the present invention, and the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present invention should be covered by the protection scope of the present invention. The protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for synchronizing configured data, characterized in that The method includes the following steps: S1. According to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals, and then read the system information tables of all upstream applications, the URL information tables of the issued data interfaces, the table field mapping tables, and the field conversion tables. S2. Based on the information in the application information table, create threads for each downstream application that needs to be synchronized in sequence, import the system information tables of each upstream application, the URL information tables of the issued data interfaces, the table field mapping tables, and the field conversion tables into the corresponding application threads, and loop to process the data synchronization tasks of each application thread. S3. Traverse the upstream application issued data interfaces corresponding to the configured applications, and call the issued data interfaces in sequence to obtain the issued data. If there is no issued data, continue to call the next issued data interface. If there is issued data, when the issued data is obtained, write the obtained issued data into the receiving log table, generate SQL statements according to the configured table field mapping and field conversion data, and execute the data synchronization task to the downstream application database and then continue to call the next interface.

2. The method for synchronizing configured data according to claim 1, wherein In step S1, according to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of table field mapping data through the graphical interface or directly in the system information table.

3. The method for synchronizing configured data according to claim 2, wherein In step S1, according to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of issued data interfaces through the graphical interface or directly in the URL information table of the issued data interface.

4. The method for synchronizing configured data according to claim 3, wherein In step S1, according to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of table field mapping data through the graphical interface or directly in the field mapping table.

5. The method for synchronizing configured data according to claim 4, wherein In step S1, according to the timing start rule set in the synchronization configuration file, trigger the data synchronization task at regular intervals. For each additional synchronization of an upstream application, add one or more rows of data through the graphical interface or directly in the field conversion table.

6. The method for synchronizing configured data according to claim 5, wherein Step S2 includes the following steps: S21. Traverse the upstream application issued data interfaces corresponding to the configured applications, and determine whether there are un-synchronized issued data interfaces. If there are, call the issued data interfaces in sequence to obtain the issued data, and determine whether there is obtained issued data. If there is no obtained issued data, continue to call the next issued data interface. If there is obtained issued data, write the obtained issued data into the receiving log table when the data is obtained.

7. The method for synchronizing configured data according to claim 6, wherein Step S3 includes the following steps: S31. Receive the unprocessed issued data in the receiving log table, and determine whether the received issued data has a deletion flag. When it is detected that there is a deletion flag, obtain the values of the associated fields according to the received issued data, the corresponding system information table, and the table field mapping, and generate a query SQL statement and a deletion SQL statement.

8. The method for synchronizing configured data according to claim 7, wherein Step S3 also includes the following steps: S32. Execute the query SQL statement and the delete SQL statement operation in the downstream application database, and write the downloaded data retrieved by the query and the delete SQL statement into the SQL log table. If the deletion is successful, write the SQL statement into the log table recording the success of SQL. If the deletion fails, record the error information and the executed SQL statement.

9. The method for synchronizing configured data according to claim 8, wherein The step S3 further includes the following steps: S33. Receive the undistributed data in the log table and determine whether the received undistributed data has a deletion flag. When no deletion flag is detected, configure the corresponding system information table and table field mapping according to the received undistributed data, obtain the value of the associated field, and generate a query SQL statement.

10. The method for synchronizing configured data according to claim 9, characterized in that, The step S3 further includes the following steps: S34. Execute the search SQL statement operation in the downstream application database. If the data does not exist, obtain the value of the field to be inserted according to the configured corresponding system information table, table field mapping, and field conversion table information, generate an insert SQL statement and execute the insertion. If the insertion is successful, write the SQL statement into the log table recording the success of SQL. If the insertion fails, record the error information and the executed SQL statement; if the data exists, obtain the value of the associated field and the value of the field to be updated according to the configured corresponding system information table, table field mapping, associated field, and field conversion table information, generate an update SQL and execute it. If the update is successful, write the SQL into the log table recording the success of SQL. If the update fails, record the error information and the executed SQL statement.

Images