CN113239119A - Data synchronization method, device and storage medium - Google Patents

Data synchronization method, device and storage medium Download PDF

Info

Publication number
CN113239119A
CN113239119A CN202110611254.7A CN202110611254A CN113239119A CN 113239119 A CN113239119 A CN 113239119A CN 202110611254 A CN202110611254 A CN 202110611254A CN 113239119 A CN113239119 A CN 113239119A
Authority
CN
China
Prior art keywords
configuration
data synchronization
configuration template
service system
template
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
Application number
CN202110611254.7A
Other languages
Chinese (zh)
Inventor
刘颖麒
黄超洋
张占腾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Yeahka Technology Co ltd
Original Assignee
Shenzhen Yeahka Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Yeahka Technology Co ltd filed Critical Shenzhen Yeahka Technology Co ltd
Priority to CN202110611254.7A priority Critical patent/CN113239119A/en
Publication of CN113239119A publication Critical patent/CN113239119A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/252Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files
    • G06F9/4451User profiles; Roaming
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Computing Systems (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a data synchronization method, a device and a storage medium, wherein the method comprises the following steps: receiving interaction parameters of a service system to be docked; configuring a pre-stored configuration template according to the interaction parameters; and carrying out data synchronization between the first service system and the second service system according to the configured configuration template. The invention breaks the limit of the technology stack between the systems, realizes the rapid butt joint between the systems, has high efficiency and saves the investment of manpower and cost.

Description

Data synchronization method, device and storage medium
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a data synchronization method, device, and storage medium.
Background
At present, before data synchronization between two enterprise systems, an enterprise user needs to develop a corresponding docking interface for each system by self-behavior of the enterprise user, and then service docking between the systems is performed according to the developed docking interface, so that data synchronization between the systems is realized. Because the docking experience data of the enterprise system which has already implemented service docking at present belongs to private data of enterprise users and is not reproducible, when a new enterprise user also needs to implement data synchronization between systems through the same two enterprise systems, the operations still need to be executed again to implement data synchronization between systems, which results in long time spent on service docking between systems.
Disclosure of Invention
The embodiment of the application aims to solve the technical problem that the time spent by a new enterprise user for inter-system service docking through the same two enterprise systems is long due to the fact that docking experience data of the enterprise systems which have already realized service docking at present cannot be copied by providing a data synchronization method, data synchronization equipment and a storage medium.
The embodiment of the application provides a data synchronization method, which comprises the following steps:
receiving interaction parameters of a service system to be docked, wherein the service system to be docked comprises a first service system and a second service system;
configuring a pre-stored configuration template according to the interaction parameters;
and carrying out data synchronization between the first service system and the second service system according to the configured configuration template.
In an embodiment, the step of configuring the pre-stored configuration template according to the interaction parameter includes:
determining the system type of the service system to be docked according to the interaction parameters;
acquiring a configuration template according to the system type;
and outputting a configuration interface according to the configuration template so that a user can input the interaction parameters based on the configuration interface.
In an embodiment, the step of obtaining a configuration template according to the system type includes:
judging whether the pre-stored configuration templates comprise configuration templates related to the system types or not;
and when the pre-stored configuration templates comprise the configuration templates associated with the system types, acquiring the configuration templates associated with the system types.
In an embodiment, the step of determining whether the pre-stored configuration templates include a configuration template associated with the system type includes:
comparing the historical system type associated with each historical configuration template in the pre-stored configuration templates with the system type;
and when the historical system type associated with any one historical configuration template is the same as the system type, determining that the pre-stored configuration templates comprise the configuration template associated with the system type.
In an embodiment, after the step of determining whether the pre-stored configuration templates include the configuration template associated with the system type, the method further includes:
when the pre-stored configuration templates do not comprise the configuration template associated with the system type, creating a configuration template matched with the system type;
and acquiring the created configuration template.
In one embodiment, the step of creating a configuration template matching the system type includes:
acquiring a first parameter item in the created configuration template;
when the number of the first parameter items is different from that of the second parameter items of the interaction parameters, adjusting the number of the first parameter items to be the same as that of the second parameter items.
In an embodiment, after the step of creating a configuration template matching the system type when the configuration template associated with the system type is not included in the pre-stored configuration templates, the method further includes:
and updating the pre-stored configuration template by adopting the created configuration template.
In an embodiment, after the step of outputting a configuration interface according to the configuration template for a user to input the interaction parameter based on the configuration interface, the method further includes:
acquiring test data input into the configuration interface;
performing data synchronization test between the first service system and the second service system according to the test data to obtain a test result;
and acquiring test comparison data, wherein when the test result is the same as the test comparison data, the configuration of the configuration template is determined to be successful.
In addition, to achieve the above object, the present invention also provides a terminal device including: the data synchronization system comprises a memory, a processor and a data synchronization program which is stored on the memory and can run on the processor, wherein the data synchronization program realizes the steps of the data synchronization method when being executed by the processor.
In addition, to achieve the above object, the present invention also provides a storage medium having stored thereon a data synchronization program which, when executed by a processor, implements the steps of the above data synchronization method.
The technical scheme of the data synchronization method, the data synchronization device and the storage medium provided in the embodiments of the present application has at least the following technical effects or advantages:
the technical scheme that the pre-stored configuration template is configured according to the received interactive parameters of the service system to be docked, and data synchronization between the first service system and the second service system is carried out according to the configured configuration template is adopted, so that the technical problem that the time spent by a new enterprise user for carrying out service docking between the systems through the same two enterprise systems is long due to the fact that the docking experience data of the enterprise system which has already been subjected to service docking at present cannot be copied is solved.
Drawings
FIG. 1 is a schematic diagram of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a data synchronization method according to the present invention;
FIG. 3 is a flowchart illustrating a data synchronization method according to a second embodiment of the present invention;
fig. 4 is a flowchart illustrating a data synchronization method according to a third embodiment of the present invention.
Detailed Description
For a better understanding of the above technical solutions, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As shown in fig. 1, fig. 1 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present invention.
It should be noted that fig. 1 is a schematic structural diagram of a hardware operating environment of the terminal device.
As shown in fig. 1, the terminal device may include: a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the terminal device configuration shown in fig. 1 is not meant to be limiting for the terminal device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a storage medium, may include therein an operating system, a network communication module, a user interface module, and a data synchronization program. Among them, the operating system is a program that manages and controls hardware and software resources of the terminal device, a data synchronization program, and the operation of other software or programs.
In the terminal device shown in fig. 1, the user interface 1003 is mainly used for connecting a terminal, and performing data communication with the terminal; the network interface 1004 is mainly used for the background server and performs data communication with the background server; the processor 1001 may be used to invoke a data synchronization program stored in the memory 1005.
In this embodiment, the terminal device includes: a memory 1005, a processor 1001, and a data synchronization program stored on the memory 1005 and executable on the processor, wherein:
when the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are performed:
receiving interaction parameters of a service system to be docked, wherein the service system to be docked comprises a first service system and a second service system;
configuring a pre-stored configuration template according to the interaction parameters;
and carrying out data synchronization between the first service system and the second service system according to the configured configuration template.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
determining the system type of the service system to be docked according to the interaction parameters;
acquiring a configuration template according to the system type;
and outputting a configuration interface according to the configuration template so that a user can input the interaction parameters based on the configuration interface.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
judging whether the pre-stored configuration templates comprise configuration templates related to the system types or not;
and when the pre-stored configuration templates comprise the configuration templates associated with the system types, acquiring the configuration templates associated with the system types.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
comparing the historical system type associated with each historical configuration template in the pre-stored configuration templates with the system type;
and when the historical system type associated with any one historical configuration template is the same as the system type, determining that the pre-stored configuration templates comprise the configuration template associated with the system type.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
when the pre-stored configuration templates do not comprise the configuration template associated with the system type, creating a configuration template matched with the system type;
and acquiring the created configuration template.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
acquiring a first parameter item in the created configuration template;
when the number of the first parameter items is different from that of the second parameter items of the interaction parameters, adjusting the number of the first parameter items to be the same as that of the second parameter items.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
and updating the pre-stored configuration template by adopting the created configuration template.
When the processor 1001 calls the data synchronization program stored in the memory 1005, the following operations are also performed:
acquiring test data input into the configuration interface;
performing data synchronization test between the first service system and the second service system according to the test data to obtain a test result;
and acquiring test comparison data, wherein when the test result is the same as the test comparison data, the configuration of the configuration template is determined to be successful.
It should be noted that, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that shown, and the data synchronization method is applied to a data synchronization tool, which can implement data synchronization between two different office systems; two different office systems, for example, the BlueRad OA System and the golden butterfly System.
As shown in fig. 2, in a first embodiment of the present application, a data synchronization method of the present application includes the following steps:
step S210: and receiving the interactive parameters of the service system to be docked.
In this embodiment, the service system to be docked includes a first service system and a second service system, where the first service system and the second service system are two different systems, for example, the first service system is a blue-and-red-ice OA system, and the second service system is a golden-and-butterfly system, or the first service system is a golden-and-butterfly system and the second service system is a blue-and-red-ice OA system. If data synchronization between the first service system and the second service system needs to be realized, the first service system and the second service system need to be docked through a data synchronization tool. After the first service system and the second service system are connected in a butt joint mode, data to be processed, which are generated by the first service system and need to be processed by the second service system, are synchronously sent to the second service system, the second service system processes the data to be processed and returns processing results to the first service system, or the data to be processed, which are generated by the second service system and need to be processed by the first service system, are synchronously sent to the first service system, and the first service system processes the data to be processed and returns the processing results to the second service system. That is, the first service system and the second service system can process data generated by one of the parties and requiring the other party to process each other.
Specifically, before the first service system and the second service system are docked, the data synchronization tool needs to receive interaction parameters for docking the first service system and the second service system. The interactive parameters are obtained by arranging scattered data collected by a user from the first service system and the second service system in advance, and then are sent to the data synchronization tool, and the data synchronization tool receives the interactive parameters sent by the user. The interaction parameters comprise system information of the first service system and the second service system, wherein the system information of the first service system comprises attribute information, database information, a server address, account information, a data synchronization rule, a data processing rule, a data synchronization exception processing rule and the like. The attribute information comprises the name, type, identification and the like of the first service system; the database information comprises database addresses, database types and the like, wherein the database types are MySQL for example; the account information comprises an account number, a password and the like of the first service system; the synchronization rule of the data is a way of sending data to the second service system, for example, sending data to the second service system once every other time; the data processing rule refers to a data processing rule corresponding to different data, for example, the data sent by the second service system is employee annual leave asking data, and after the employee submits a leave asking form on the second service system, the first service system directly performs annual leave deduction according to the date of submitting the leave asking form, or performs annual leave deduction on the date of ending the leave asking period; the processing rule of the data synchronization exception refers to a data exception processing rule corresponding to different data, for example, after the first service system receives data from the second service system, the first service system sends a data reception error prompt to the second service system to notify the second service system to resend the data.
Accordingly, the system information of the second business system includes second attribute information, second database information, a second server address, second account information, a synchronization rule of the second data, a processing rule of a synchronization exception of the second data, and the like. The specific content corresponding to each piece of information in the system information of the second service system is similar to the specific content corresponding to each piece of information in the system information of the first service system, and is not described in detail in this embodiment.
Step S220: and configuring a pre-stored configuration template according to the interaction parameters.
In this embodiment, the configuration module is pre-stored in the database, the configuration template includes parameter items corresponding to the system information of the first service system and the second service system in the interaction parameters, after receiving the interaction parameters, the configuration template is obtained, and the specific content of the system information of the first service system and the second service system is written into the corresponding parameter items, so that the configuration of the configuration template can be completed. For example, the database address of the first service system is written into the database address parameter entry corresponding to the first service system, correspondingly, the database address of the second service system is written into the database address parameter entry corresponding to the second service system, and so on.
Step S230: and carrying out data synchronization between the first service system and the second service system according to the configured configuration template.
In this embodiment, after configuration of the configuration template is completed, the data synchronization tool monitors data generated by the first service system and the second service system simultaneously according to the configured configuration template, for example, to-be-processed data generated by the first service system is handed to the second service system for processing, the data synchronization tool sends the to-be-processed data generated by the first service system to the second service system for processing according to the configured configuration template, and after it is monitored that the to-be-processed data processing of the second service system is completed, the to-be-processed data is sent to the first service system according to the configured configuration template, thereby implementing data synchronization between the first service system and the second service system. Similarly, the data to be processed generated by the second service system is handed to the first service system for processing, and the data synchronization process is the same as the above process, which is not described herein again. For example, after monitoring that a first business system generates a leave requisition, a data synchronization tool reads the leave requisition from a database of the first business system, writes the leave requisition into a database of a second business system according to a configured configuration template, the second business system reads the leave requisition from the database and processes the leave requisition, after generating the leave requisition information by the second business system, the data synchronization tool reads the leave requisition information from the database of the second business system according to the configured configuration template and writes the leave requisition information into the database of the first business system, when an employee queries his own leave requisition through the first business system, the first business system reads the leave requisition from the database and feeds the leave requisition information back to the queried employee.
According to the technical scheme, the pre-stored configuration template is configured according to the received interaction parameters of the service system to be docked, and the data synchronization between the first service system and the second service system is carried out according to the configured configuration template, so that the limitation of a technical stack between the systems is broken, the rapid docking between the systems is realized, the efficiency is high, and the investment of manpower and cost is saved. In addition, the data synchronization tool can be independently packaged to be an independent data synchronization tool, the docking between corresponding systems is specially realized, for example, the data synchronization tool is packaged to be only docked with a Bluedong OA system and a golden butterfly system, so that the data synchronization between the Bluedong OA system and the golden butterfly system is realized, the data synchronization tool can be packaged to support various systems, the data synchronization between the Bluedong OA system and the golden butterfly system can be realized, and the data synchronization between other two systems can be realized.
As shown in fig. 3, in the second embodiment of the present application, step S220 includes the following steps based on the first embodiment:
step S221: and determining the system type of the service system to be docked according to the interaction parameters.
In this implementation, after receiving the interaction parameters, the data synchronization tool determines what the first service system is specifically based on the attribute information of the first service system in the interaction parameters, and determines what the second service system is specifically based on the attribute information of the second service system in the interaction parameters. For example, the first business system determined according to the interaction parameters is a blue-ray OA system, the second business system is a golden butterfly system, and then the system type of the business system to be docked is a blue-ray OA system-golden butterfly system type or a golden butterfly system-blue-ray OA system type.
Step S222: and acquiring a configuration template according to the system type.
In this embodiment, a configuration template is prestored in a database of the data synchronization tool, the prestored configuration template includes historical configuration templates associated with different historical system types, the historical system type is determined according to a first service system and a second service system which have been docked in the past and successfully implement data synchronization, and the historical configuration template is a configuration template corresponding to the first service system and the second service system which have been docked in the past and successfully implement data synchronization.
Specifically, after the system types of the first service system and the second service system are determined, the system type of the service system to be docked is also determined, and then the corresponding configuration template may be obtained from the database according to the determined system type of the service system to be docked.
Further, the step S222 of obtaining the configuration template according to the system type includes:
judging whether the pre-stored configuration templates comprise configuration templates related to the system types or not;
when the pre-stored configuration templates comprise configuration templates associated with the system types, acquiring the configuration templates associated with the system types;
when the pre-stored configuration templates do not comprise the configuration templates associated with the system types, creating the configuration templates matched with the system types;
and acquiring the created configuration template.
Specifically, the historical configuration templates associated with the historical system types included in the configuration templates stored in the database of the data synchronization tool are limited, when the configuration templates are obtained according to the system types of the system to be docked, it is necessary to determine whether the configuration templates associated with the system types are included in the pre-stored configuration templates, if so, it is indicated that a configuration template matched with the system type exists in the database, and then the configuration template matched with the system type is obtained from the database, and if not, it is indicated that no configuration template matched with the system type exists in the database, and then a configuration template matched with the system type is created.
Further, when judging whether the pre-stored configuration templates include configuration templates associated with the system type, comparing the historical system type associated with each historical configuration template in the pre-stored configuration templates with the system type of the system to be docked, namely comparing whether the historical system type associated with each historical configuration template in the pre-stored configuration templates is the same as the system type, determining that the pre-stored configuration templates include configuration templates associated with the system type when the historical system type associated with any historical configuration template is the same as the system type, and determining that the pre-stored configuration templates do not include configuration templates associated with the system type when the historical system types associated with all historical configuration templates are not the same as the system type. For example, historical configuration template 1 in the configuration templates is associated with historical system type 1, historical configuration template 2 is associated with historical system type 2, and historical configuration template 3 is associated with historical system type 3, where historical system type 3 is golden butterfly system-blue tooth OA system type, and the system type of the system to be docked is also golden butterfly system-blue tooth OA system type, then it is determined that the configuration template associated with the system type is included in the pre-stored configuration templates, and historical configuration template 3 is the configuration template associated with golden butterfly system-blue tooth OA system type, so that historical configuration template 3 is obtained as the configuration template associated with golden butterfly system-blue tooth OA system type.
If the historical system type 1-the historical system type 3 are not the golden butterfly system-the blue-ray OA system type, determining that the pre-stored configuration templates do not comprise the configuration template associated with the system type, and further needing to create the configuration template matched with the system type of the current system to be docked. The database also stores a first common template matching a first system and a second common template matching a second system item, wherein the first common template is different from the second common template, for example, the first common template is of a system type suitable for a first business system, for example, the first business system is of a tool type system, the first common template is suitable for the tool type system, the second common template is of a system type suitable for a second business system, for example, the second business system is of a financial type system, and the second common template is suitable for the financial type system. According to the system type of the current first service system and the system type of the second service system, a specific first universal template and a specific second universal template can be determined, then the first universal template and the second universal template are combined to obtain a configuration template matched with the system type of the current system to be docked, namely the configuration template matched with the system type of the current system to be docked is created, and then the created configuration template is obtained.
Further, a configuration template matched with the system type may be created in a preset manner, where the preset manner is:
acquiring a first parameter item in the created configuration template;
and when the number of the first parameter items is different from that of the second parameter items of the interaction parameters, adjusting the number of the first parameter items to be the same as that of the second parameter items.
Specifically, the created configuration template is obtained by combining a first general template and a second general template, the first general template is applicable to a first service system of the same type, the second general template is applicable to a second service system of the same type, and parameter information in each general template is fixed, that is, a parameter item in the created configuration template is fixed, where the parameter item in the created configuration template is referred to as a first parameter item; when the content in the received interaction parameters is more, the parameter items in the interaction parameters are more, and the parameter items in the interaction parameters are referred to as second parameter items; when the number of the second parameter items is greater than that of the first parameter items, the first parameter items and the second parameter items cannot form correspondence, the content in the interactive parameters cannot be completely written into the created configuration template, and then data synchronization between the first service system and the second service system cannot be realized according to the created configuration template after configuration. When the number of the first parameter item is different from the number of the second parameter item of the interaction parameter, the number of the first parameter item is required to be adjusted to be the same as the number of the second parameter item, so as to ensure that the interaction parameter is completely written into the created configuration template.
Further, after the created configuration template, the created configuration template is used to update a pre-stored configuration template, the pre-stored configuration template is updated to be the database, for example, the created configuration template is associated with the system type of the current system to be docked and then added to the database, so as to update the configuration template in the database, thereby improving the database.
Step S223: and outputting a configuration interface according to the configuration template so that a user can input the interaction parameters based on the configuration interface.
In this embodiment, after the configuration template is acquired, the data synchronization tool outputs a configuration interface corresponding to the configuration template, and the user inputs all contents in the interactive parameters into each parameter item in the configuration interface through other input methods such as a keyboard and voice, so that the configuration of the configuration template can be completed.
As shown in fig. 4, in the third embodiment of the present application, based on the first embodiment and the second embodiment, the following steps are further included after step S223:
step S2231: and acquiring test data input into the configuration interface.
In this embodiment, the test data is data for testing whether data synchronization between the first service system and the second service system can be normally achieved. The configuration interface is reserved with a write-in item of test data, after the configuration interface is output according to the configuration template, the configuration interface displays an input item capable of displaying the test data, a user inputs the test data into the configuration interface through input modes such as a keyboard or voice, and the data synchronization tool acquires the test data input into the configuration interface.
Step S2232: and performing data synchronization test between the first service system and the second service system according to the test data to obtain a test result.
Step S2233: and acquiring test comparison data, wherein when the test result is the same as the test comparison data, the configuration of the configuration template is determined to be successful.
Specifically, the data synchronization tool writes first test data into a database of a second service system according to a configuration template, the second service system reads the first test data from the database, processes the first test data, and after the processing is completed, the data synchronization tool reads a processing result from the database of the second service system, where the processing result is referred to as a first test result, and after the first test result is read, the data synchronization tool obtains first test comparison data which is previously imported into the data synchronization tool by a user, compares the first test comparison data with the first test result, and if the first test comparison data is the same as the first test result, determines that the configuration template is successfully configured, the data synchronization between the first service system and the second service system can be normally performed. Similarly, it is also necessary to test whether data synchronization can be performed between the second service system and the first service system, and accordingly, the data synchronization tool writes the second test data into the database of the first service system according to the configuration template, the first service system reads the second test data from the database, then processing the second test data, after the processing is finished, reading a processing result from the database of the first service system by the data synchronization tool, the processing result is called a second test result, after the second test result is read, the data synchronization tool obtains second test comparison data which is imported into the data synchronization tool in advance by a user, compares the second test comparison data with the second test result, if the two are the same, the configuration template is determined to be successfully configured, and then the data synchronization between the second service system and the first service system can be normally carried out.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (10)

1. A data synchronization method, characterized in that the data synchronization method comprises:
receiving interaction parameters of a service system to be docked, wherein the service system to be docked comprises a first service system and a second service system;
configuring a pre-stored configuration template according to the interaction parameters;
and carrying out data synchronization between the first service system and the second service system according to the configured configuration template.
2. The data synchronization method according to claim 1, wherein the step of configuring the pre-stored configuration template according to the interaction parameter comprises:
determining the system type of the service system to be docked according to the interaction parameters;
acquiring a configuration template according to the system type;
and outputting a configuration interface according to the configuration template so that a user can input the interaction parameters based on the configuration interface.
3. The data synchronization method of claim 2, wherein the step of obtaining a configuration template according to the system type comprises:
judging whether the pre-stored configuration templates comprise configuration templates related to the system types or not;
and when the pre-stored configuration templates comprise the configuration templates associated with the system types, acquiring the configuration templates associated with the system types.
4. The data synchronization method according to claim 3, wherein the step of determining whether the pre-stored configuration templates include a configuration template associated with the system type comprises:
comparing the historical system type associated with each historical configuration template in the pre-stored configuration templates with the system type;
and when the historical system type associated with any one historical configuration template is the same as the system type, determining that the pre-stored configuration templates comprise the configuration template associated with the system type.
5. The data synchronization method according to claim 3, wherein after the step of determining whether the pre-stored configuration templates include the configuration template associated with the system type, the method further comprises:
when the pre-stored configuration templates do not comprise the configuration template associated with the system type, creating a configuration template matched with the system type;
and acquiring the created configuration template.
6. The method of claim 5, wherein the step of creating a configuration template that matches the system type comprises:
acquiring a first parameter item in the created configuration template;
when the number of the first parameter items is different from that of the second parameter items of the interaction parameters, adjusting the number of the first parameter items to be the same as that of the second parameter items.
7. The data synchronization method according to claim 5, wherein after the step of creating a configuration template matching the system type when the configuration template associated with the system type is not included in the pre-stored configuration templates, further comprising:
and updating the pre-stored configuration template by adopting the created configuration template.
8. The method of claim 2, wherein after the step of outputting a configuration interface according to the configuration template for a user to input the interaction parameters based on the configuration interface, further comprising:
acquiring test data input into the configuration interface;
performing data synchronization test between the first service system and the second service system according to the test data to obtain a test result;
and acquiring test comparison data, wherein when the test result is the same as the test comparison data, the configuration of the configuration template is determined to be successful.
9. A terminal device, comprising: memory, a processor and a data synchronization program stored on the memory and executable on the processor, the data synchronization program when executed by the processor implementing the steps of the data synchronization method according to any one of claims 1-8.
10. A storage medium having stored thereon a data synchronization program which, when executed by a processor, implements the steps of the data synchronization method of any one of claims 1-8.
CN202110611254.7A 2021-06-01 2021-06-01 Data synchronization method, device and storage medium Pending CN113239119A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110611254.7A CN113239119A (en) 2021-06-01 2021-06-01 Data synchronization method, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110611254.7A CN113239119A (en) 2021-06-01 2021-06-01 Data synchronization method, device and storage medium

Publications (1)

Publication Number Publication Date
CN113239119A true CN113239119A (en) 2021-08-10

Family

ID=77136300

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110611254.7A Pending CN113239119A (en) 2021-06-01 2021-06-01 Data synchronization method, device and storage medium

Country Status (1)

Country Link
CN (1) CN113239119A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115328997A (en) * 2022-07-15 2022-11-11 深圳市数帝网络科技有限公司 Data synchronization method, system, device and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115328997A (en) * 2022-07-15 2022-11-11 深圳市数帝网络科技有限公司 Data synchronization method, system, device and storage medium

Similar Documents

Publication Publication Date Title
CN105739968B (en) Method and device for reviewing updated content based on distributed version control system Git
CN112036824A (en) Business approval method, system, storage medium and electronic equipment
CN109376088B (en) Automatic test system and automatic test method
CN111159049A (en) Automatic interface testing method and system
CN112905459B (en) Service interface testing method and device, electronic equipment and storage medium
CN111897738B (en) Automatic testing method and device based on atomic service
CN111966426A (en) API (application program interface) docking method, system, equipment and storage medium
CN113239119A (en) Data synchronization method, device and storage medium
CN112905460B (en) Device and method for simulating three-party receipt by automatic interface test
CN112905461A (en) Method and device for executing automatic interface test case
CN115328997B (en) Data synchronization method, system, device and storage medium
CN107562629B (en) Method and device for testing
CN111199390A (en) Invoice reimbursement method and device, storage medium and electronic equipment
CN113515447B (en) Automatic testing method and device for system
WO2014130790A1 (en) Supplier analysis and verification system and method
CN111124705B (en) Service request processing method and device
KR101691929B1 (en) An apparatus for implementing an automation of a web user interface and method therefor
US20060052965A1 (en) Event driven testing method, system and program product
CN113093965A (en) Account registration method, device, computer system and storage medium
CN108628750B (en) Test code processing method and device
CN111767233B (en) Service testing method and device based on intelligent express cabinet
CN113298538B (en) Customer service data processing method and device
CN116955161A (en) Multi-terminal service testing method and device, storage medium and computer equipment
CN113971020A (en) Software parallel development method and device
CN113568838A (en) Test data generation method, device, equipment, storage medium and program product

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