System docking method, computer equipment, storage medium and product

Abstract

The invention relates to a system docking method, computer equipment, a storage medium and a product. The method comprises the following steps: acquiring a first interface docked with a second system in a first system, and acquiring a second interface docked with the first system in the second system; creating a first field group corresponding to the first interface and a second field group corresponding to the second interface according to the field information corresponding to the first interface and the second interface; determining a mapping relationship between the first field group and the second field group according to a system docking agreement; and respectively mapping the fields in the first field group into the corresponding second field groups according to the mapping relationship. By adopting the method, the problem of low system docking stability can be solved.

Description

Technical Field

[0001] The present application relates to the field of information system integration, and in particular to system docking methods, computer equipment, storage media and products. Background Art

[0002] In the field of information system integration, the docking of multiple systems is often involved. Traditional integration methods have many disadvantages. Usually, the docking parties must first agree on the docking interface fields, detailed field descriptions, message formats, and request methods, or directly select the existing ready-made interfaces of one party, and then enter the substantive code writing stage, followed by interface joint debugging and integration work. However, this docking mode involves multiple complex and time-consuming steps, and involves a large amount of manual code writing, which easily leads to deviations in the entire docking process and the problem of low system docking stability.

[0003] With regard to the problem of low system docking stability in related technologies, no effective solution has been proposed so far. Summary of the invention

[0004] Based on this, it is necessary to provide a system docking method, computer equipment, storage medium and product that can solve the problem of low system docking stability in response to the above technical problems.

[0005] In a first aspect, a system docking method is provided in this embodiment, and the method includes:

[0006] Acquire a first interface connected to a second system in the first system, and acquire a second interface connected to the first system in the second system;

[0007] Creating, according to the field information corresponding to the first interface and the second interface, a first field group corresponding to the first interface and a second field group corresponding to the second interface;

[0008] Determine a mapping relationship between the first field group and the second field group according to a system connection agreement;

[0009] The fields in the first field group are respectively mapped to the corresponding second field group according to the mapping relationship.

[0010] In some embodiments, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method includes:

[0011] Determining whether the message structure of the first field group conforms to a preset message structure;

[0012] If the message structure does not conform to the preset message structure, constructing a message template according to the preset message structure;

[0013] The values ​​in the first field group are filled into the message template to obtain a first field group that conforms to the preset structure.

[0014] In some embodiments, the determining whether the message structure of the first field group conforms to a preset message structure corresponding to the second interface includes:

[0015] Obtaining the preset message structure according to the markup language and / or hierarchical features corresponding to the second interface;

[0016] Determine whether the message structure in the first field group conforms to the preset message structure.

[0017] In some embodiments, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method further includes:

[0018] Construct a test case according to the first field group and the field verification rule of the first interface;

[0019] When it is verified based on the test case that the first system and the second system are successfully connected, the field groups in the first field group are mapped to the corresponding second field groups based on the mapping relationship.

[0020] In some embodiments, the step of constructing a test case according to the fields and field verification rules entered in the first interface includes:

[0021] combining the fields in the first field group;

[0022] Generate test data that complies with the field verification rule according to the combined fields;

[0023] The test case is constructed by combining the combined fields and the test data.

[0024] In some embodiments, creating a first field group corresponding to the first interface and a second field group corresponding to the second interface according to field information corresponding to the first interface and the second interface includes:

[0025] Dividing the fields entered into the first interface according to the message structure and field names corresponding to the fields required to be entered into the first interface to obtain the first field group;

[0026] According to the message structure and field name of the field that needs to be entered into the second interface, the fields entered into the second interface are divided to obtain the second field group.

[0027] In some embodiments, after mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method further includes:

[0028] According to the field mapping result between the first field group and the second field group within a preset time period, the number of users who use the first interface and the second interface to connect to the first system and the second system is adjusted.

[0029] In a third aspect, a computer device is provided in this embodiment, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the system docking method described in the first aspect is implemented.

[0030] In a fourth aspect, a computer-readable storage medium is provided in this embodiment, on which a computer program is stored. When the computer program is executed by a processor, the system docking method described in the first aspect is implemented.

[0031] In a fifth aspect, a computer program product is provided in this embodiment, including a computer program, which, when executed by a processor, implements the system docking method described in the first aspect above.

[0032] The above-mentioned system docking method, computer equipment, storage medium and product, by grouping the fields of the first interface and the second interface during system docking, distinguish the direction of the interface fields between the systems through the field group, reduce the docking error rate between the systems, and achieve the effect of improving the stability of system docking. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 An application environment diagram of a system docking method in an embodiment;

[0034] Figure 2 A schematic diagram of a flow chart of a system docking method in an embodiment;

[0035] Figure 3 A schematic diagram of a flow chart of a rule engine execution system docking method in one embodiment;

[0036] Figure 4 is a structural block diagram of a system docking device in an embodiment;

[0037] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0039] The system docking method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown in Figure 1 In the application environment shown. Figure 1 As shown, the terminal 102 communicates with N systems 104 through the network, and the terminal 102 connects to multiple systems to achieve intercommunication between multiple systems 104. Wherein, N is a positive integer, N ≥ 2. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, and tablet computers. Further, the terminal 102 can also communicate with the server through the network, and the data storage system stores the data that the server 104 needs to process, and the data storage system can also be placed on the cloud or other network servers. Further, the system 104 may include a server, a router, a gateway, and multiple devices.

[0040] In one embodiment, Figure 2 As shown, a system docking method is provided, which is applied to Figure 1 The terminal in is used as an example to illustrate, including the following steps:

[0041] Step 202: acquiring in the first system a first interface connected to the second system, and acquiring in the second system a second interface connected to the first system.

[0042] The first system and the second system may be any type of computer system; the system types of the first system and the second system may be the same or different, which is not limited here. The first interface and the second interface may use existing interfaces in the first system and the second system, or may be created according to the docking requirements of the first system and the second system. The first interface is used to exchange data with the second system, and the second interface is used to exchange data with the first system.

[0043] Optionally, according to system docking requirements, one or more first interfaces for docking with the second system are created in the first system, and one or more second interfaces for docking with the first system are created in the second system.

[0044] Step S204: Create a first field group corresponding to the first interface and a second field group corresponding to the second interface according to the field information corresponding to the first interface and the second interface.

[0045] The field information includes, but is not limited to, the content, format, and type of the field to be input into the first interface, and the content, format, and type of the field to be input into the second interface. Furthermore, the field information may also be a field mapping condition manually set according to business requirements.

[0046] Optionally, one or more first field groups are created under the first interface according to the field information corresponding to the first interface, and the corresponding field contents in different first field groups are different. Synchronously or asynchronously, one or more second field groups are created under the second interface according to the field information corresponding to the second interface, and the corresponding field contents in different second field groups are different.

[0047] Step S206: Determine a mapping relationship between the first field group and the second field group according to the system connection agreement.

[0048] The system connection agreement includes but is not limited to the first interface agreement, the second interface agreement, the message definition transmitted between the first system and the second system, the field verification rule and the request response format. Optionally, the upstream and downstream of the data mapping are determined according to the first interface agreement and the second interface agreement to obtain the data flow direction, and then the mapping relationship between each field group is established according to the data flow direction.

[0049] Step S208: Map the fields in the first field group to the corresponding second field group according to the mapping relationship.

[0050] Optionally, the field data to be transmitted is entered into the first interface, a first field group corresponding to the field data is determined, and the first field group is mapped to a corresponding second field group in the second interface according to a mapping relationship, thereby realizing upstream and downstream mapping.

[0051] Furthermore, the terminal includes a visualized rule engine, and the above steps S202 to S208 are implemented with the help of the visualized rule engine, so that the connection between the first system and the second system is easier to maintain and the direction of the data flow between the first system and the second system is clearer and more transparent.

[0052] In the above system docking method, the upstream and downstream fields are grouped in combination with the field information corresponding to the first interface and the second interface when the system is docked, and the first field group and the second field group, as well as the mapping relationship between the first field group and the second field group, are obtained; by distinguishing the direction of the interface fields between the systems through the mapping relationship, the docking error rate between the systems can be reduced, thereby achieving the effect of improving stability.

[0053] In one embodiment, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method includes: determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface; if the message structure does not conform to the preset message structure, constructing a message template according to the preset message structure; mapping the values ​​in the first field group to the message template to obtain a field group that conforms to the preset structure.

[0054] Among them, the message structure includes but is not limited to the hierarchical structure of the message; the data in the message header, message footer and message body adopts the protocol and format. Optionally, obtain the hierarchical structure of the message composed of each field in the first field group, the hierarchical structure of the message that the second interface needs to receive, and determine whether the hierarchical structure of the message corresponding to the first field group is the same as the hierarchical structure of the message corresponding to the second interface. If the same, the message structure conforms to the preset message structure. If not the same, execute the steps: construct a message template according to the preset message structure; fill the value in the first field group into the message template to obtain a field group that conforms to the preset structure.

[0055] Wherein, the message template includes a structural framework of a preset message structure. Optionally, the message template includes one or more expressions, and the expressions are used to indicate information about the value of the variable, access index, and access object corresponding to the key name. The value corresponding to the key name specified by the expression is selected from the first field group, and the value is filled into the expression to obtain a first field group that conforms to the preset structure. Optionally, the message template includes one or more expressions, and the expression dynamically references the attribute value of the variable or object in the first field group. The attribute value of each variable or object in the first field group is extracted through a script, and the value of each variable or object attribute in the first field group is mapped to the message template according to the expression to obtain a first field group that conforms to the preset structure.

[0056] Furthermore, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, data filtering and cleaning may be performed on the field data.

[0057] In this embodiment, by performing intermediate conversion on the structure of the message that constitutes the fields, the problems of configuration difficulties and code redundancy caused by different languages ​​between docking systems can be reduced, thereby reducing the problem of unstable system docking caused by complex configuration and redundant code. At the same time, it is convenient to modify the system docking method according to business requirements, which is beneficial to the operation and maintenance of the system.

[0058] Further, in one embodiment, determining whether the message structure of the first field group conforms to a preset message structure includes: obtaining a preset message structure based on a markup language and / or hierarchical features corresponding to the second interface; and determining whether the message structure in the first field group conforms to the preset message structure.

[0059] Among them, the markup language of the second interface refers to the language or format used to describe and define the interface structure, behavior and interaction method; the hierarchical feature refers to the organization method of each level of the message that the second interface needs to receive. Optionally, after determining the preset message structure according to the markup language and the hierarchical feature, a message template that conforms to the hierarchical feature corresponding to the second structure is constructed based on the markup language. In this embodiment, the preset message structure is obtained according to the markup language, so that when the system docking upstream and downstream use different markup languages, the message can be intermediately converted by judging the message structure; the preset message structure is obtained by the hierarchical feature, and the complexity of the upstream data level can be adjusted so that the adjusted field data corresponds to the complexity of the downstream data level; thereby reducing the error rate during the system docking process.

[0060] In one embodiment, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method also includes: constructing a test case according to the field verification rules of the first field group and the first interface; when it is verified based on the test case that the first system and the second system are successfully connected, mapping the field groups in the first field group to the corresponding second field group based on the mapping relationship.

[0061] Among them, the field verification rules of the first interface are obtained according to the system docking agreement, including but not limited to checking the format of the input field entered in the first interface and the content of the input field. Optionally, the parameters for constructing the test case are constructed according to the first field group and the field verification rules of the first interface, and multiple test cases are obtained by adjusting the parameters to simulate whether the docking of the first system and the second system under the currently configured parameters meets the docking requirements. Among them, the rationality and integrity of the content of the data transmitted between the first system and the second system, the data format and one or more aspects can be verified based on the docking requirements. If the simulation result of the test case does not meet the docking requirements, it is determined that the first system and the second system cannot be successfully docked, and there are errors in the configuration parameters of the first interface and the second interface. The configuration parameters can be adjusted until the first system and the second system are successfully docked. Optionally, the construction and verification of the test case can be realized through visual configuration, so as to realize effective system configuration evaluation through a small number of code snippets. Further, after automatically constructing the test case and completing the test case simulation request, the test structure can be recorded and a statistical report of the system response can be generated.

[0062] In this embodiment, by building and verifying test cases, the amount of code development and configuration logic problems are reduced, thereby achieving the effect of improving the stability of system docking.

[0063] Furthermore, in one embodiment, a test case is constructed based on the fields and field verification rules entered in the first interface, including: combining the fields in the first field group; generating test data that complies with the field verification rules based on the combined fields; and constructing a test case based on the combined fields and the test data.

[0064] Among them, the fields in one or more first field groups can be combined. Optionally, the following characteristics of the field are determined: the field is empty, the field is not empty, the field is a number, the field is a character, the field length is greater than the limited length, and the field length is less than the limited length, and the fields are randomly combined based on the above characteristics. Furthermore, the combination of fields can also be achieved in combination with the number of input parameters provided by the first interface to obtain the field combination results under different numbers of input parameters, and the combined fields are used as input parameter sample data. Optionally, the required fields in the combined fields are obtained, and one or more test data that conform to the field verification rules are randomly generated based on the required fields. In this embodiment, the automatic construction of test cases is achieved by combining upstream fields.

[0065] In one embodiment, based on the field information corresponding to the first interface and the second interface, a first field group corresponding to the first interface and a second field group corresponding to the second interface are created, including: dividing the fields entered into the first interface according to the message structure and field names corresponding to the fields entered into the first interface as needed to obtain the first field group; dividing the fields entered into the second interface according to the message structure and field names of the fields entered into the second interface as needed to obtain the second field group.

[0066] The message structure includes the hierarchical structure of the message, the composition of the message, etc. Optionally, one or more first field groups are obtained according to the hierarchy of the message composed of the fields of the first interface and the field division of each field. One or more second field groups are obtained according to the hierarchy of the message composed of the fields of the second interface and the field division of each field.

[0067] For example, if the message structure composed of the input fields in the first interface is as follows:

[0068]

[0069] Two first field groups are constructed based on the above fields, one of which is:

[0070]

[0071] Another first field group is:

[0072]

[0073]

[0074] The message structure received in the second interface is as follows:

[0075] {

[0076] "ad":"Zhejiang",

[0077] "moeny":12.23,

[0078] "t_d":"test"

[0079] }

[0080] The message received in the second structure is regarded as the second field group. The two first field groups in the above-mentioned first interface are mapped to the second field group together. It can be understood that the division rule of the first field group and the second field group can be adjusted according to business needs; for example, the fields in the first interface are directly regarded as the first field group, and the first field group is mapped to the third field group.

[0081] In this embodiment, field grouping is implemented according to the message structure and field name to meet the data flow requirements in different scenarios.

[0082] In one embodiment, after mapping the fields in the first field group to the corresponding second field group respectively based on the mapping relationship, the method also includes: adjusting the number of users who use the first interface and the second interface to connect the first system and the second system according to the field mapping result between the first field group and the second field group within a preset time period.

[0083] Among them, the field mapping results include but are not limited to the first and second interface call states, data flow, and data request data. Optionally, the configured first and second interfaces are published to the production environment, and the field mapping results within this period are obtained based on a preset time period. If the field mapping results meet business expectations, the number of users who use the first and second interfaces to connect to the first and second systems is increased; if. If the field mapping results do not meet business expectations, the number of users who use the first and second interfaces to connect to the first and second systems is maintained or reduced.

[0084] In this embodiment, by adjusting the number of users, it is helpful to reduce the connection risk between the first system and the second system before the first interface and the second interface are fully used to connect the first system and the second system.

[0085] In one embodiment, a visual rule engine is provided to achieve cross-system docking. By deploying the visual rule engine service in a specified environment, it is necessary to ensure that the network connection between the service and the existing services and the docking party services is stable and unobstructed, thereby providing a good network environment so that subsequent docking work can be carried out smoothly. Figure 3A schematic diagram of a rule engine execution system docking method is provided, such as Figure 3 As shown, including:

[0086] Step S301, agreeing on docking information. The agreed docking information includes: obtaining the system docking agreement by the rule engine. Optionally, according to the actual business needs of the first system and the second system and the characteristics of the first system and the second system, the first interface and the second interface are agreed on, the message is defined, the field verification rules and the request response format are formulated to cover various normal situations and various abnormal situations in the system docking process. The agreed docking information can be used to establish a framework for the docking work, and the interaction specifications and standards of the first system and the second system are clarified.

[0087] Step S302, create upstream and downstream groups, enter fields, field types, and field verification rules. Optionally, based on the system docking agreement, create corresponding upstream groups and downstream groups in the message mapping component of the rule engine. According to business needs, enter the required fields, field types, and field verification rules in the upstream interface. Optionally, the field verification rules are obtained by entering in the form of verification regularities. Enter the required fields, field types, and field verification rules in the downstream interface. Among them, if the first interface corresponds to the upstream, the upstream group is the first field group; if the second interface corresponds to the downstream, the downstream group is the second field group.

[0088] Among them, by creating upstream and downstream groups, the direction of interface data between systems can be clearly fed back; the number of interface interactions between the same systems can be indirectly fed back; the logical association between pushed data and received data can be determined; and daily operation and maintenance and modifications can be facilitated, and the error rate of system docking can be reduced.

[0089] Step S303: Create a corresponding relationship between upstream and downstream. By establishing a mapping relationship between upstream and downstream groups, the fields belonging to each group are automatically mapped and matched. After confirmation by the user, the upstream and downstream data transmission is completed. Figure 3 As shown in the figure, after creating the upstream field grouping and the downstream field grouping, the fields in the upstream grouping are cleaned and mapped, and the fields in the upstream grouping are forwarded. During the forwarding process, the mapping is automatically created based on the field name and level upstream grouping, or the corresponding downstream grouping is checked according to the pre-set conditions such as "$variable[data]->variable", and the fields in the upstream grouping are mapped to the corresponding downstream grouping.

[0090] Optionally, the rule engine also includes a script component, a judgment control component, and a data filtering and cleaning component. The upstream data can be intermediately transformed through the script component, the judgment control component, and the data filtering and cleaning component. Among them, data cleaning is used to intercept data that does not meet the system docking agreement. The script component is used to use a small number of script language fragments to complete the system docking business requirements that cannot be completed by the current configuration, or to achieve business docking requirements in scenarios with cumbersome configurations. The judgment control component is used to determine whether the upstream fields need to be intermediately transformed by the script component and the data filtering and cleaning component.

[0091] The judgment control component determines that the complexity of the upstream and downstream data does not match based on the complexity of the upstream data level and the complexity of the downstream data level, and the upstream data needs to be converted, and determines that the script component implements the intermediate conversion of the data. For example, if the upstream data structure is json, it is as follows:

[0092]

[0093] The downstream data structure is as follows:

[0094] {

[0095] "pdCode":"12",

[0096] "pdTime":"2024-12-12:12:12:12",

[0097] "t_d":"test"

[0098] }

[0099] The script component configures the following template to implement intermediate transformation of upstream data:

[0100] {

[0101] "pdCode":$test.$adf[0].$pdCode,

[0102] "pdTime":$test.$adf[0].$pdCode,

[0103] "t_d":$td.$t_d

[0104] }

[0105] Alternatively, the values ​​of the script components adf and td are mapped to the code provided by the following script component, with the value of adf being A and the value of td being B:

[0106] {

[0107] "pdCode":$A.$pdCode,

[0108] "pdTime":$A.$pdCode,

[0109] "t_d":$B.$t_d

[0110] }

[0111] The intermediate conversion method can simplify the configuration difficulty in complex scenarios, especially in scenarios where different markup languages ​​are used in the upstream and downstream. For example, the upstream uses the markup language in the XML format, and the downstream only accepts the markup language in the JSON format. This intermediate conversion can greatly reduce the configuration difficulty, facilitate real-time modification according to business requirements, reduce redundant code, and facilitate operation and maintenance.

[0112] Step S304, configure automated case (test case) verification. Optionally, obtain the upstream creation fields and field validation rules, and combine the fields according to the required features and non-required features corresponding to the fields. Randomly generate data that meets the field validation rules based on the required fields obtained after the combination, obtain a case set based on the data and the fields obtained after the combination, and automatically execute the case to provide statistical feedback on the execution results. Optionally, when combining fields, multiple combinations can also be obtained based on the input parameter arrangement of the interface, including: according to the number of input parameters and the following field characteristics: empty, not empty, number, character, greater than the specified length, less than the specified length, the combination constructs the input parameter sample data. Automatically complete the simulated request based on the input parameter sample data, record the results, and generate corresponding statistical reports. Among them, the configuration will only take effect after the automated case verification is successful based on the recorded results.

[0113] Step S305, the configuration takes effect and configures the traffic grayscale. According to the window confirmed in the system docking agreement, the above system docking configuration is published to the production environment. And according to the daily system docking results, adjust the open ratio of the system docking configuration in the production environment. Furthermore, the operation and maintenance personnel use the visualization page to obtain the detailed status of the interface calls in the docking systems of both parties in real time, including real-time dynamics of data flow, original data of data requests, intermediate data in the conversion process and other key information. In the subsequent operation process, if there are changes in requirements, they can be easily met by dynamically adjusting the system configuration, which truly saves time and effort, and realizes efficient and flexible cross-system docking.

[0114] In this embodiment, by using automatic mapping of message groups, automatic case generation and detection methods before configuration takes effect, the probability of error is reduced, ensuring that the effective configuration is the configuration that can be released for production, greatly reducing repeated debugging and confirmation, and reducing human errors. By introducing a visual rule engine, online configuration can be achieved, and the location and status of the flow nodes of the data flow can be monitored in real time, which significantly reduces the time cost required for docking, and can also greatly reduce or even achieve zero-code development, making the entire system easier to maintain, solving the problems of long system docking cycles, prone to errors, and reliance on code writing, which leads to waste of resources.

[0115] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0116] Based on the same inventive concept, the embodiment of the present application also provides a system docking device for implementing the system docking method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more system docking device embodiments provided below can refer to the limitations on the system docking method above, and will not be repeated here.

[0117] In one embodiment, Figure 4 As shown, a system docking device is provided, comprising:

[0118] An interface acquisition module, which acquires, in the first system, a first interface connected to the second system, and acquires, in the second system, a second interface connected to the first system;

[0119] A grouping module, which creates a first field group corresponding to the first interface and a second field group corresponding to the second interface according to the field information corresponding to the first interface and the second interface;

[0120] A connection module determines a mapping relationship between the first field group and the second field group according to a system connection agreement;

[0121] The mapping module maps the fields in the first field group to the corresponding second field group according to the mapping relationship.

[0122] In some of the embodiments, the system docking device further includes an intermediate conversion module, which is used to execute a method before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship: determining whether the message structure of the first field group conforms to the preset message structure; if the message structure does not conform to the preset message structure, constructing a message template according to the preset message structure; filling the value in the first field group into the message template to obtain the first field group conforming to the preset structure. Optionally, determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface includes: obtaining the preset message structure according to the markup language and / or hierarchical features corresponding to the second interface; determining whether the message structure in the first field group conforms to the preset message structure.

[0123] In some of the embodiments, the system docking device also includes a testing module, which is used to construct a test case according to the field verification rules of the first field group and the first interface before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship; when it is verified based on the test case that the first system and the second system are successfully docked, the field groups in the first field group are mapped to the corresponding second field group based on the mapping relationship.

[0124] In some of the embodiments, a test case is constructed based on the fields and field verification rules entered in the first interface, including: combining the fields in the first field group; generating test data that complies with the field verification rules based on the combined fields; and constructing a test case based on the combined fields and the test data.

[0125] In some of the embodiments, a first field group corresponding to the first interface and a second field group corresponding to the second interface are created based on the field information corresponding to the first interface and the second interface, including: dividing the fields entered into the first interface according to the message structure and field names corresponding to the fields entered into the first interface as needed to obtain the first field group; dividing the fields entered into the second interface according to the message structure and field names of the fields entered into the second interface as needed to obtain the second field group.

[0126] In some of the embodiments, the system docking device also includes a publishing module, which is used to adjust the number of users who use the first interface and the second interface to dock the first system and the second system according to the field mapping result between the first field group and the second field group within a preset time period after mapping the fields in the first field group to the corresponding second field group based on the mapping relationship.

[0127] Each module in the above-mentioned system docking device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0128] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface and the display unit are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a system docking method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen or a projection device. The display screen can be a liquid crystal display screen or an electronic ink display screen.

[0129] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0130] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0131] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0132] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0133] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited thereto. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited thereto.

[0134] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0135] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A system docking method, characterized in that: The method comprises: Acquire a first interface connected to a second system in the first system, and acquire a second interface connected to the first system in the second system; Creating, according to the field information corresponding to the first interface and the second interface, a first field group corresponding to the first interface and a second field group corresponding to the second interface; Determine a mapping relationship between the first field group and the second field group according to a system connection agreement; The fields in the first field group are respectively mapped to the corresponding second field group according to the mapping relationship.

2. The method according to claim 1, characterized in that Before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method includes: Determining whether the message structure of the first field group conforms to a preset message structure; If the message structure does not conform to the preset message structure, constructing a message template according to the preset message structure; The values ​​in the first field group are filled into the message template to obtain a first field group that conforms to the preset structure.

3. The method according to claim 2, characterized in that The determining whether the message structure of the first field group conforms to a preset message structure corresponding to the second interface includes: Obtaining the preset message structure according to the markup language and / or hierarchical features corresponding to the second interface; Determine whether the message structure in the first field group conforms to the preset message structure.

4. The method according to claim 1, characterized in that: Before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method further includes: Construct a test case according to the first field group and the field verification rule of the first interface; When it is verified based on the test case that the first system and the second system are successfully connected, the field groups in the first field group are mapped to the corresponding second field groups based on the mapping relationship.

5. The method according to claim 4, characterized in that The step of constructing a test case according to the fields and field verification rules entered in the first interface includes: combining the fields in the first field group; Generate test data that complies with the field verification rule according to the combined fields; The test case is constructed by combining the combined fields and the test data.

6. The method according to claim 1, characterized in that The step of creating a first field group corresponding to the first interface and a second field group corresponding to the second interface according to the field information corresponding to the first interface and the second interface includes: Dividing the fields entered into the first interface according to the message structure and field names corresponding to the fields required to be entered into the first interface to obtain the first field group; According to the message structure and field name of the field that needs to be entered into the second interface, the fields entered into the second interface are divided to obtain the second field group.

7. The method according to claim 1, characterized in that After mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method further includes: According to the field mapping result between the first field group and the second field group within a preset time period, the number of users who use the first interface and the second interface to connect to the first system and the second system is adjusted.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images