Integrated docking system

Abstract

The application discloses an integrated docking system, which comprises a standardized integrated module for standardizing integrated basic data and business data and performing data synchronization docking between three-party systems according to the standardized integrated basic data and business data; a customized integrated module for generating plug-in customized docking data according to customized requirements of a target object and performing data synchronization docking between three-party systems according to the plug-in customized docking data; and a visual module for realizing the visualization of a docking process when the standardized integrated module or the customized integrated module performs data docking with the three-party systems. The standardized integrated module is used for standardizing the basic data and the business data commonly existing between different objects, realizing the standardized docking of data of different three-party systems, and reducing the development cost, thereby solving the technical problem of high development cost caused by the fact that different enterprises need to develop different docking integrated platforms in the prior art.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular, relates to an integrated docking system. BACKGROUND

[0002] With the rapid development of the Internet, in the process of daily management, enterprises often purchase third-party professional information systems to improve their management efficiency, such as purchasing enterprise resource planning (ERP) system to fully organize and effectively transmit information, so that enterprise resources in purchasing, storage, production, sales, personnel, finance, and material can be reasonably configured and utilized, thereby realizing the improvement of enterprise management efficiency, purchasing human resource management (HR) system to help enterprises plan, recruit, train, assess, pay, and mobilize human resources, and purchasing financial management system to comprehensively manage analysis, prediction, planning, control, and supervision in enterprise financial management.

[0003] The above-mentioned third-party systems are generally relatively independent, and the data between them cannot be connected. The same operator in the same enterprise often needs to log in to different systems to operate related work processes. Therefore, the coordination of daily work of the enterprise is relatively cumbersome and inefficient.

[0004] At present, enterprises usually select a secondary development customized docking integration platform to realize data connection of the third-party systems. However, since the third-party systems purchased by each enterprise are different, different docking integration platforms need to be developed for different enterprises, resulting in high development cost.

[0005] In view of the problem that different enterprises need to develop different docking integration platforms in the related art, resulting in high development cost, no effective solution has been proposed at present. SUMMARY

[0006] The main purpose of the present application is to provide an integrated docking system to solve the problem that different enterprises need to develop different docking integration platforms in the related art, resulting in high development cost.

[0007] In order to achieve the above-mentioned purpose, the present application provides an integrated docking system.

[0008] According to the integrated docking system of the present application, the standardization integration module is used to standardize the integration of basic data and business data, and to synchronize and dock the data between at least two third-party systems according to the basic data and business data of the standardization integration. The basic data and business data are data commonly existing between different objects.

[0009] The customized integration module is configured to generate plug-in customized docking data according to the customized requirements of the target object, and to perform data synchronization docking between at least two three-party systems according to the plug-in customized docking data.

[0010] The visualization module is configured to visualize the docking process when the standardized integration module or the customized integration module performs data docking with the at least two three-party systems.

[0011] In a possible implementation manner of the present application, the standardized integration module is configured with data models respectively corresponding to the basic data and the business data.

[0012] The standardized integration module is configured to perform standardized processing on the corresponding basic data and the business data according to the data models.

[0013] In a possible implementation manner of the present application, the basic data includes department data, personnel data, role data and archive data; and the business data includes login data, message notification data, to-do task data and attendance data.

[0014] In a possible implementation manner of the present application, if the data to be synchronized and docked is basic data, the standardized integration module is configured to:

[0015] obtain a data configuration instruction and a synchronization docking instruction, wherein the synchronization docking instruction carries a data type of the basic data to be synchronized and docked;

[0016] perform data configuration according to the data configuration instruction, and access a first three-party system of the at least two three-party systems in response to the synchronization docking instruction, to obtain first basic data in the first three-party system that matches the data type carried in the synchronization docking instruction;

[0017] access a second three-party system of the at least two three-party systems in response to the synchronization docking instruction, to obtain second basic data in the second three-party system that matches the first basic data according to a preset matching rule, and to synchronize the first basic data to the second three-party system.

[0018] In a possible implementation manner of the present application, the standardized integration module is further configured to record a synchronization log in response to a synchronization result fed back by the second three-party system.

[0019] In a possible implementation manner of the present application, if the data to be synchronized and docked is message notification data, to-do task data or attendance data in the business data, the standardized integration module is configured to:

[0020] obtain a creation configuration instruction and a synchronization organization data instruction, perform creation configuration according to the creation configuration instruction, and perform organization data synchronization in response to the synchronization organization data instruction;

[0021] obtaining an outbound message generated by a second tripartite system in the at least two tripartite systems in response to an event initiation instruction;

[0022] processing the outbound message to obtain a message log, and sending a corresponding message to a first tripartite system in the at least two tripartite systems according to the message log, so as to realize synchronization of business data of the second tripartite system to the first tripartite system.

[0023] In a possible implementation manner of the present application, the standardized integration module is further configured to:

[0024] parsing the outbound message and generating an outbound message log;

[0025] converting the outbound message into a target message corresponding to the type of the business data according to the type of the business data;

[0026] generating the message log according to the target message.

[0027] In a possible implementation manner of the present application, if the data to be synchronized and connected is login data in the business data, the standardized integration module is configured to:

[0028] obtaining a synchronization personnel data instruction and synchronizing personnel data in response to the synchronization personnel data instruction;

[0029] obtaining a first temporary login address obtained by a first tripartite system in the at least two tripartite systems according to a single sign-on instruction, and obtaining corresponding personnel information in a second tripartite system in the at least two tripartite systems according to the first temporary login address;

[0030] generating a temporary access address according to the obtained personnel information and sending the temporary access address to the second tripartite system;

[0031] feeding a second temporary login address generated by the second tripartite system in response to the temporary access address to the first tripartite system, so as to realize single sign-on of the first tripartite system to the second tripartite system based on the second temporary login address.

[0032] In a possible implementation manner of the present application, the visualization module is further configured to data checking in the data synchronization and connection process and / or troubleshooting connection problems according to the log generated in the data synchronization and connection process.

[0033] In a possible implementation manner of the present application, the standardized integration module, the customized integration module and the visualization module are deployed based on containerization technology.

[0034] In the present application, the common basic data and business data between different objects are standardized integrated by the standardized integration module, and the data synchronization docking between at least two three-party systems is performed according to the standardized integrated basic data and business data, so that the same docking module is avoided to be repeatedly developed for different objects, thereby realizing the standardized docking. Meanwhile, the application generates the plug-in customized docking data according to the customized requirements of the target object through the customized integration module, so that the difference customization of the integrated docking system by different objects can be realized, which can not only reduce the development cost and save manpower, but also meet the customized requirements of different objects. Further, the technical problem that different enterprises need to develop different docking integration platforms in the related art, resulting in high development cost, is solved. BRIEF DESCRIPTION OF DRAWINGS

[0035] The accompanying drawings, which form a part of the present application, are intended to provide further understanding of the present application, and to make apparent the other features, objectives and advantages of the present application. The illustrative embodiments of the present application and their description serve the purpose of explanations and are not intended to be limiting of the present application. In the drawings:

[0036] Figure 1 is a schematic diagram of an application scenario of the integrated docking system provided in the embodiments of the present application;

[0037] Figure 2 is a schematic diagram of a structure of the integrated docking system provided in the embodiments of the present application;

[0038] Figure 3 is a service topology diagram of the integrated docking system provided in the embodiments of the present application;

[0039] Figure 4 is a flowchart of synchronizing part data provided in the embodiments of the present application;

[0040] Figure 5 is a flowchart of synchronizing personnel data provided in the embodiments of the present application;

[0041] Figure 6 is a flowchart of synchronizing role data provided in the embodiments of the present application;

[0042] Figure 7 is a flowchart of synchronizing attendance data provided in the embodiments of the present application;

[0043] Figure 8 is a flowchart of synchronizing message notification data provided in the embodiments of the present application;

[0044] Figure 9 is a flowchart of synchronizing to-do task data provided in the embodiments of the present application;

[0045] Figure 10 is a flowchart of synchronously logging data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should belong to the scope of protection of the present application.

[0047] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0048] In the present application, the terms "upper", "lower", "left", "right", "front", "back", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate the orientation or positional relationship shown in the drawings. These terms are mainly used to better describe the present application and its embodiments, and are not intended to limit the indicated devices, elements or components to have a specific orientation, or to be constructed and operated in a specific orientation.

[0049] In addition, in addition to being used to indicate the orientation or positional relationship, the above-mentioned part of the terms can also be used to indicate other meanings, for example, the term "upper" can also be used to indicate a certain dependent relationship or connection relationship in some cases. For those skilled in the art, the specific meaning of these terms in the present application can be understood according to the specific circumstances.

[0050] In addition, the meaning of the term "a plurality of" should be two and more than two.

[0051] It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict. The present application will be described in detail below with reference to the drawings and in combination with the embodiments.

[0052] Before introducing the integrated docking system of the present application, first introduce the docking integrated platform in the related art.

[0053] Generally, enterprises often purchase third-party professional information systems to improve their management efficiency in the process of daily management, such as ERP systems, HR systems, financial management systems, etc. These third-party systems are generally relatively independent, and the data between them cannot be connected. The same operator in the same enterprise often needs to log in to different systems to operate related work processes. Thus, the coordination of daily work of the enterprise is relatively cumbersome, and the work efficiency is not high.

[0054] Generally, large-scale enterprises have a relatively high degree of informatization, have their own information technology (IT) departments and information security departments, and have certain requirements for data storage and data transmission. In order to ensure the safety of enterprise data, internal network isolation is generally required, and related data is required to be stored locally, and core services need to be run on the internal network.

[0055] During the development of the enterprise, the third-party systems purchased by the enterprise are different, and there may be data of organizational personnel using system A, attendance documents using system B, and financial budget using system C. A standard integrated solution is usually difficult to meet the actual use scenarios of customers, and customized demands are difficult to avoid.

[0056] At present, enterprises usually select a secondary development customized docking integrated platform to realize data connection of various third-party systems. However, due to the differences between the third-party systems purchased by each enterprise, different docking integrated platforms need to be developed for different enterprises, which results in high development cost.

[0057] Therefore, the present application provides an integrated docking system, please refer to Figure 1 , Figure 1 is an application scenario diagram of the integrated docking system provided in the embodiments of the present application. The integrated docking system 100 can be used to dock each third-party system of the target object, such as the first third-party system 201, the second third-party system 202, and the third third-party system 203. In the embodiments of the present application, the docking between systems can be understood as data sharing, data synchronization, etc. between systems.

[0058] It is worth noting that in the embodiments of the present application, the number of third-party systems of the target object, i.e., the target enterprise, can be determined according to the actual application scenario. The three third-party systems exemplified here are only one example, and do not limit the number of third-party systems docked by the integrated docking system of the embodiments of the present application.

[0059] The data of at least two third-party systems enables data sharing between the third-party systems. For exampleFigure 1 three-party system A, three-party system B and three-party system C in FIG.

[0060] Please refer to Figure 2 , Figure 2 is a structural schematic diagram of an integrated docking system provided in the embodiments of the present application. The integrated docking system 100 can include a standardized integrated module 101, a customized integrated module 102 and a visualization module 103.

[0061] The standardized integrated module 101 can be used for standardized integration of basic data and business data, and data synchronization docking between at least two three-party systems according to the standardized integrated basic data and business data. The basic data and business data are data commonly existing between different objects.

[0062] The customized integrated module 102 can be used for generating plug-in customized docking data according to customized requirements of a target object, and performing data synchronization docking between at least two three-party systems according to the plug-in customized docking data.

[0063] The visualization module 103 can be used for visualizing the docking process when the standardized integrated module 101 or the customized integrated module 103 performs data docking with at least two three-party systems.

[0064] Based on the existing integrated project analysis, the embodiments of the present application involve two major blocks of integrated business. The first block is synchronization update of basic data, which can include department data, personnel data, role data, archive data, etc. The second block is synchronization update of business data, which can include login data, message notification data, to-do task data and attendance data, etc.

[0065] It can be understood that the above-mentioned basic data and business data are data that an enterprise usually has. Therefore, for the data commonly existing between different objects, the standardized integrated module 101 can be set to perform standardized integration of the commonly existing basic data and business data, so as to avoid repeated development of the same integrated module for each object or enterprise.

[0066] For differentiated data or systems between different objects, the customized integrated module 102 in the embodiments of the present application can generate plug-in customized docking data according to customized requirements of a target object, so as to meet docking requirements of different customers.

[0067] In the embodiments of the present application, the visualization module 103 can visualize the docking process when the standardized integrated module 101 or the customized integrated module 103 performs data docking with at least two three-party systems, so that problems existing in the data docking process can be found in time.

[0068] In the present application, the basic data and business data commonly existing between different objects are standardized and integrated by the standardized integration module 101, and data synchronization docking between at least two three-party systems is performed according to the standardized and integrated basic data and business data, so that the same docking module is avoided to be repeatedly developed for different objects, thereby realizing standardized docking. Meanwhile, the customized integration module 102 generates plug-in customized docking data according to the customized requirements of the target object, so that the difference customization of the integrated docking system by different objects can be realized, which can not only reduce the development cost and save manpower, but also meet the customized requirements of different objects, thereby solving the technical problem that different enterprises need to develop different docking integration platforms in the related art, resulting in high development cost.

[0069] In some embodiments of the present application, the standardized integration module 101 can be configured with data models respectively corresponding to the basic data and the business data; the standardized integration module 101 can be used for standardized processing of the corresponding basic data and business data according to the data models.

[0070] In the embodiments of the present application, by abstracting the integrated related data, the integrated bottom data model is abstracted into an object model, an object field model, an object data model, and an object field data model, which can cover most of the data scenarios of the integrated business.

[0071] As shown in Table One, the data model corresponding to the basic data is as follows:

[0072] Table One Basic Data

[0073] Attribute Number Enterprise Number Creation Time Modification Time Deletion Mark Identification id corp_id create_time update_time deleted

[0074] As shown in Table Two, the data model corresponding to the system configuration is as follows:

[0075] Table Two System Configuration

[0076] Attribute Tenant Name Tenant Type Configuration Data Identification corp_name corp_type config

[0077] As shown in Table Three, the data model corresponding to the main data is as follows:

[0078] Table Three Main Data

[0079] Attribute Object Number Unique Attribute Source Data Target Source Data Identification object_id unique_field source_json target_json

[0080] As shown in Table Four, the data model corresponding to the object is as follows:

[0081] Table Four Object

[0082] Attribute Application Type Variable Name Display Name Identification app_type variable_name display_name

[0083] Attribute Icon Description Extended Information Object Type Identification icon remark data_json object_type

[0084] The data model for the object data is as shown in Table 5 below:

[0085] Table 5 Object Data

[0086] Attribute Source Enterprise Number Target Source Enterprise Number Source Object Number Identification source_corp_id target_corp_id source_object_id

[0087] Attribute Target Source Enterprise Number Object Data Identification target_object_id data_json

[0088] The data model for the field is as shown in Table 6 below:

[0089] Table 6 Field

[0090]

[0091]

[0092] The data model for the field data is as shown in Table 7 below:

[0093] Table 7 Field Data

[0094]

[0095] The data model for the role is as shown in Table 8 below:

[0096] Table 8 Role

[0097] Attribute Role Number User Number Remark Identification role_id ebridge_user_id remark

[0098] Attribute Synchronization Status Department Number Identification state dept_id

[0099] The data model for the attendance configuration is as shown in Table 9 below:

[0100] Table 9 Attendance Configuration

[0101] Attribute Application Type Enable Status Configuration Data Identification app_type enable config_data

[0102] The data model for the outbound message is as shown in Table 10 below:

[0103] Table 10 Outbound Message

[0104] Attribute Process Number Form Detail logsmd5 Value Object Data Identification flow_id form_logs_md5 message

[0105] The data model for the document details is as shown in Table 11 below:

[0106] Table 11 Document Details

[0107] Attribute Form Detail logsmd5 Value Form Detail Identification form_logs_md5 form_detail

[0108] The data model for the message history is as shown in Table 12 below:

[0109] Table XII message history record

[0110] Attribute Form Detail logsmd5 Value Form Title Form Description Identification form_logs_md5 form_title form_desc

[0111] Attribute Process Number Process Node Number Event Name Operator Name Identification flow_id node_id action_name user_name

[0112] Attribute Type Request Data Corresponding Data Push Status Identification type request response message_send_status

[0113] The data model corresponding to the synchronization request log is shown in Table XIII as follows:

[0114] Table XIII synchronization request log

[0115] Attribute Application Type Business Type Synchronization Type Identification app_type business_type sync_mode

[0116] Attribute Task Number Execution Action Operator Number Operator Name Identification task_id action opt_user_id opt_user_name

[0117] Attribute Operator Number Result Description Request URL Interface Description Request Parameters Identification opt_user_id result_desc req_url api_desc req_content

[0118] Attribute State Method Name Class Name Identification state method_name class_name

[0119] The data model corresponding to the system log is shown in Table XIV as follows:

[0120] Table XIV system log

[0121] Attribute Log Type Form Detail Task number Identification log_type Business ID Task ID

[0122] Attribute Operator number Operator name Log details Identification operater_id operater_name data_json

[0123] Please refer to Figure 3 , Figure 3 is a service topology of an integrated docking system provided in an embodiment of the present application, as shown in Figure 3 , the standardized integration module 101 can be ebridge-server, the customized integration module 102 can be ebridge-plugins, and the visualization module 103 can be ebridge-web. The integrated docking system adopts front and back separation to develop front-end and back-end services, wherein the front-end is developed by using an antd framework, and the back-end is developed by using a springboot. A web service uses Nginx for routing, uses Redis for caching, and uses mysql for persistence. The integrated docking system uses docker containerization to deploy, that is, the standardized integration module, the customized integration module, and the visualization module are uniformly packaged and installed based on containerization technology, and are deployed in a customer's local environment, store customer data locally, and are deployed in a customer's intranet environment.

[0124] The integrated docking system of the embodiments of the present application can be deployed to the local environment of a customer by containerizing ebridge-server, ebridge-plugins, ebridge-web, ebridge-auth, Nginx, Redis, Mysql, and by scripts, and can complete data initialization, and can be truly ready for use, greatly expanding the application scenarios of the system.

[0125] In some embodiments of the present application, if the data to be synchronized and docked is basic data, the standardized integration module can be further used to:

[0126] obtain data configuration instructions and synchronization docking instructions, wherein the synchronization docking instructions carry the data type of the basic data to be synchronized and docked;

[0127] configure data according to the data configuration instructions, and access a first third-party system in the at least two third-party systems in response to the synchronization docking instructions, to obtain first basic data in the first third-party system that matches the data type carried by the synchronization docking instructions;

[0128] access a second third-party system in the at least two third-party systems in response to the synchronization docking instructions, to obtain second basic data in the second third-party system that matches the first basic data according to a preset matching rule, and synchronize the first basic data to the second third-party system.

[0129] For example, the basic data is department data, as shown in Figure 4 is a flowchart of synchronization of department data provided in the embodiments of the present application, wherein Yiqiao is the integrated docking system of the embodiments of the present application, information system is a first third-party system, and Yi Kuai Bao is a second third-party system, and the process of full-increment synchronization of the department data of the information system to Yi Kuai Bao is as follows:

[0130] The user sends a data configuration instruction to the bridge, the bridge configures data according to the data configuration instruction, and feeds back configuration success information to the user, the user sends a synchronous docking instruction to the bridge, the synchronous docking instruction carries a data type of basic data to be synchronously docked, in the embodiment, the synchronous docking instruction is a synchronous department data instruction, the instruction can be used to indicate that the data docked this time is department data; the bridge accesses the information system in response to the synchronous department data instruction, obtains first basic data in the information system that matches the synchronous department data instruction, that is, department data in the information system, after the department data in the information system is obtained successfully, the bridge accesses the easy report, and according to a preset matching rule such as matching by name, the easy report feeds back a matching result to the bridge, if the matching result represents matching success, the bridge synchronously matches the department data to the easy report, the easy report feeds back a synchronous result to the bridge, the bridge records a synchronous department log according to the received synchronous result, and feeds back synchronous department data completion to the user; otherwise, if the matching result represents matching failure, data error correction can be performed by using a visual module.

[0131] As shown in Figure 5 , it is a flowchart of synchronizing personnel data provided in the embodiment of the application, if the basic data is personnel data, the process of synchronizing the full amount of the personnel data in the information system to the easy report is as follows:

[0132] The user sends a data configuration instruction to the bridge, the bridge configures data according to the data configuration instruction, and feeds back configuration success information to the user, the user sends a synchronous docking instruction to the bridge, the synchronous docking instruction carries a data type of basic data to be synchronously docked, in the embodiment, the synchronous docking instruction is a synchronous department data instruction, the instruction can be used to indicate that the data docked this time is department data; the bridge accesses the information system in response to the synchronous department data instruction, obtains first basic data in the information system that matches the synchronous department data instruction, that is, department data in the information system, after the department data in the information system is obtained successfully, the bridge accesses the easy report, and according to a preset matching rule such as matching by name, the easy report feeds back a matching result to the bridge, if the matching result represents matching success, the bridge synchronously matches the department data to the easy report, the easy report feeds back a synchronous result to the bridge, the bridge records a synchronous department log according to the received synchronous result, and feeds back synchronous department data completion to the user; otherwise, if the matching result represents matching failure, data error correction can be performed by using a visual module.

[0133] As shown in Figure 6 , it is a flowchart of synchronizing role data provided in the embodiment of the application, if the basic data is role data, the process of synchronizing the full amount of the role data in the information system to the easy report is as follows:

[0134] The user sends a data configuration instruction to the YiQiao, the YiQiao configures data according to the data configuration instruction, and feeds back configuration success information to the user, the user sends a synchronous docking instruction to the YiQiao, the synchronous docking instruction carries a data type of basic data to be synchronized and docked, in the embodiment, the synchronous docking instruction is a synchronous role data instruction, the instruction can be used to indicate that the data docked this time is role data; the YiQiao accesses the information system in response to the synchronous role data instruction, obtains third basic data in the information system that matches the synchronous role data instruction, namely role data in the information system, after the role data in the information system is obtained successfully, the YiQiao accesses the YiKuaiBao, and according to a preset matching rule such as matching through a work number, the YiKuaiBao feeds back a matching result to the YiQiao, if the matching result represents matching success, the YiQiao synchronizes the matched role data to the YiKuaiBao, the YiKuaiBao feeds back a synchronization result to the YiQiao, the YiQiao records a synchronization role log according to the received synchronization result, and feeds back synchronization role data completion to the user; otherwise, if the matching result represents matching failure, data error correction can be performed by using a visual module.

[0135] In some embodiments of the present application, if the data to be synchronized and docked is message notification data, to-be-done task data and attendance data in business data, the standardized integration module can be further used for:

[0136] obtaining a creation configuration instruction and a synchronous organization data instruction, performing creation configuration according to the creation configuration instruction, and performing organization data synchronization in response to the synchronous organization data instruction;

[0137] obtaining an outbound message generated by a second third-party system in the at least two third-party systems in response to an event initiation instruction;

[0138] processing the outbound message to obtain a message log, and sending a corresponding message to a first third-party system in the at least two third-party systems according to the message log, so as to realize synchronization of business data of the second third-party system to the first third-party system.

[0139] As shown in Figure 7 FIG. 1 is a flowchart of synchronization of attendance data provided in an embodiment of the present application, if the business data is attendance data, the process of synchronizing attendance data of the YiKuaiBao such as attendance documents to the information system is as follows:

[0140] Users send configuration creation instructions, such as an attendance configuration creation instruction, to Yiqiao. Yiqiao creates the configuration according to the instruction and sends a successful attendance configuration message to the user. Users also send organization data synchronization instructions to Yiqiao. In this embodiment, the organization data synchronization instruction instructs Yiqiao to synchronize department data and personnel data. After successfully synchronizing department data and personnel data, Yiqiao sends a successful organization data synchronization message to the user. Users can also send event initiation instructions, such as an attendance approval message event instruction, to YiKuaiBao. In response, YiKuaiBao sends an outbound message callback to Yiqiao. Yiqiao parses the outbound message, generates an outbound message log, converts the log into an Yiqiao message, generates an Yiqiao message log, and sends the attendance message to the information system. After receiving the attendance message, the information system sends a successful attendance message message to Yiqiao, thus synchronizing the attendance messages from YiKuaiBao to the information system.

[0141] like Figure 8 The diagram shown illustrates a process for synchronizing message notification data in an embodiment of this application. If the business data is message notification data, the process for synchronizing the document approval message notification data of EasyQuickReport to the information system is as follows:

[0142] Users send configuration creation instructions, such as a message configuration creation instruction, to YiBridge. YiBridge creates the configuration according to the instruction and sends a configuration success message back to the user. Users also send organization data synchronization instructions to YiBridge. In this embodiment, the organization data synchronization instruction instructs YiBridge to synchronize department data and personnel data. After successfully synchronizing department data and personnel data, YiBridge sends a synchronization success message back to the user. Users can also send event initiation instructions, such as message event instructions, to YiKuaiBao. In response, YiKuaiBao sends an outbound message callback to YiBridge. YiBridge parses the outbound message, generates an outbound message log, converts the log into an YiBridge message, generates an YiBridge message log, and sends the message to the information system. After receiving the message, the information system sends a message success message back to YiBridge, thus synchronizing YiKuaiBao's message notification data to the information system.

[0143] like Figure 9 The diagram shown is a flowchart illustrating the process of synchronizing pending task data provided in this embodiment of the application. If the business data is pending task data, the process of synchronizing pending task data from EasyQuick Report to the information system is as follows:

[0144] The user sends a creation configuration instruction, such as a to-be-created configuration instruction, to the easy bridge, the easy bridge creates a configuration according to the to-be-created configuration instruction, and feeds back to-be-created configuration success information to the user, the user sends a synchronization organization data instruction to the easy bridge, in the embodiment, the synchronization organization data instruction is used to instruct the easy bridge to synchronize department data and personnel data, and the easy bridge feeds back synchronization organization data success information to the user after successfully synchronizing the department data and the personnel data; the user initiates a to-be-created event instruction to the easy fast report, the easy fast report sends an outbound message callback to the easy bridge in response to the to-be-created event instruction, the easy bridge analyzes the outbound message, generates an outbound message log, and converts the outbound message log into an easy bridge to-be-created message, generates an easy bridge to-be-created log, and sends the to-be-created message to the information system, after the information system receives the to-be-created message, feeds back a sending message success information to the easy bridge, so as to realize synchronization of the to-be-created task data of the easy fast report to the information system.

[0145] In some embodiments of the present application, if the data synchronized and connected is login data in the business data, the standardized integration module can be further used for:

[0146] obtaining a synchronization personnel data instruction, and synchronizing personnel data in response to the synchronization personnel data instruction;

[0147] obtaining a first temporary login address obtained by a first third-party system in the at least two third-party systems according to the single sign-on instruction, and obtaining corresponding personnel information in a second third-party system in the at least two third-party systems according to the first temporary login address;

[0148] generating a temporary access address according to the obtained personnel information and sending the temporary access address to the second third-party system;

[0149] feeding back a second temporary login address generated by the second third-party system in response to the temporary access address to the first third-party system, so as to realize single sign-on of the first third-party system to the second third-party system based on the second temporary login address.

[0150] As shown in Figure 10 , it is a flowchart of synchronization of login data provided in the embodiments of the present application, if the business data is login data, the process of single sign-on to the easy fast report through the information system is as follows:

[0151] The user sends a synchronization personnel data instruction to the Yi Bridge, the Yi Bridge synchronizes personnel data according to the synchronization personnel data instruction, and accesses the Yi Kuabao according to the first temporary login address, queries personnel information corresponding to the first temporary login address in the Yi Kuabao and obtains the personnel information; the Yi Bridge generates a temporary access address according to the obtained personnel information and sends it to the Yi Kuabao, the Yi Kuabao generates a second temporary login address in response to the temporary access address and feeds back to the Yi Bridge, and then the Yi Bridge sends it to the information system and the user, so that the user can realize single sign-on to the Yi Kuabao based on the second temporary login address through the information system.

[0152] In the related art, due to the independent operation of the business among the three-party systems purchased by the enterprise customers, for the same set of data organization structure, it is necessary to switch systems back and forth for processing, resulting in low work efficiency, and the integrated docking system of the embodiments of the present application can break through the data barriers among the systems, maintain the standardization of integrated business through standardized integration modules, realize unified authentication login, centralized processing of notification messages, approval tasks, attendance documents, etc., greatly reduce the cost of integrated business development and implementation, greatly improve the work efficiency, and through customized integrated module for customized integrated business plug-in development, it can meet the customized requirements of different customers according to the customer's own business demands, and expand the application scenarios.

[0153] Further, the integrated docking system of the embodiments of the present application can perform data checking in the data synchronization docking process and / or troubleshoot docking problems according to the logs generated in the data synchronization docking process through the visual module, and the related data of departments, personnel, roles, etc. are visualized in the Yi Bridge object data, and the message logs, data synchronization logs, and related specific business exception records are recorded in the log center, which can greatly improve the troubleshooting efficiency of integrated business problems.

[0154] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. An integrated docking system, characterized in that, include: A standardization integration module is used to standardize and integrate the basic data and business data of the target object, and to perform data synchronization and docking between at least two third-party systems based on the standardized integrated basic data and business data; wherein, the basic data and the business data are data that coexist between different objects; the standardization integration module is configured with data models that correspond to and match the basic data and the business data respectively; the standardization integration module is used to perform standardization processing on the corresponding basic data and the business data according to each of the data models. A customized integration module is used to generate pluggable customized docking data according to the customized requirements of the target object, and to perform data synchronization docking between the at least two third-party systems based on the pluggable customized docking data. A visualization module is used to visualize the data connection process when the standardized integration module or the customized integration module connects with the at least two third-party systems. If the data to be synchronized is message notification data, pending task data, and attendance data in the business data, then the standardized integration module is used to: obtain creation configuration instructions and synchronization organization data instructions; perform creation configuration according to the creation configuration instructions; and perform organization data synchronization in response to the synchronization organization data instructions; obtain outbound messages generated by the second third-party system in response to the event initiation instructions in the at least two third-party systems; process the outbound messages to obtain message logs; and send corresponding messages to the first third-party system in the at least two third-party systems according to the message logs, so as to realize the synchronization of business data of the second third-party system to the first third-party system; If the data to be synchronized is the basic data, the standardized integration module is used to: obtain a data configuration instruction and a synchronization connection instruction, wherein the synchronization connection instruction carries the data type of the basic data to be synchronized; configure the data according to the data configuration instruction, and in response to the synchronization connection instruction, access the first third-party system in the at least two third-party systems to obtain the first basic data in the first third-party system that matches the data type carried by the synchronization connection instruction; in response to the synchronization connection instruction, access the second third-party system in the at least two third-party systems, obtain the second basic data in the second third-party system that matches the first basic data according to a preset matching rule, and synchronize the first basic data to the second third-party system.

2. The system according to claim 1, characterized in that, The basic data includes department data, personnel data, role data, and file data; the business data includes login data, message notification data, to-do task data, and attendance data.

3. The system according to claim 2, characterized in that, The standardized integration module is also used to: record synchronization logs in response to the synchronization results fed back by the second or third-party system.

4. The system according to claim 1, characterized in that, The standardized integration module is also used for: Parse the outbound message and generate an outbound message log; Based on the type of the business data, the outbound message is converted into a target message corresponding to the type of the business data; The message log is generated based on the target message.

5. The system according to claim 1, characterized in that, If the data to be synchronized is login data from the business data, then the standardized integration module is used for: Obtain a command to synchronize personnel data, and synchronize personnel data in response to the command; Obtain the first temporary login address obtained by the first third-party system in the at least two third-party systems according to the single sign-on instruction, and obtain the corresponding personnel information in the second third-party system in the at least two third-party systems according to the first temporary login address; A temporary access address is generated based on the obtained personnel information and sent to the second or third-party system; The second temporary login address generated by the second third-party system in response to the temporary access address is fed back to the first third-party system, so that the first third-party system can log in to the second third-party system based on the second temporary login address.

6. The system according to claim 1, characterized in that, The visualization module is also used for data inspection during the data synchronization and / or to troubleshoot integration problems based on logs generated during the data synchronization and integration process.

7. The system according to claim 1, characterized in that, The standardized integration module, customized integration module, and visualization module are orchestrated and deployed based on containerization technology.

Images