Rapid partner docking method based on configuration driving

Abstract

The invention discloses a rapid partner docking method based on configuration driving. The method comprises the following steps: S1, unifying standard data models in a system; s2, designing docking development contents into components and customization rules; s3, using a service orchestration engine to connect components and rules in series according to the whole docking process; s4, performing configuration on the development configuration platform, and performing storage in a structured data mode; s5, assembling the release package according to the batch version, and distributing the release package to an execution application server; s6, the execution application server locally stores and caches the configuration data in the batch release packet through a dynamic loading function, and dynamically loads the dynamic script; s7, storing all configuration and deployment operations in a production environment server; batch management is bound with release dates, and specific release content is framed. According to the invention, interface requirements under different partners or business scenes can be rapidly adapted, and the bottleneck problem of speed and efficiency improvement of partner docking is solved.

Description

Technical Field

[0001] The present invention relates to a method for connecting with online Internet business partners, and in particular to a configuration-driven rapid partner connection method. Background Art

[0002] With the rapid development of information technology and the deepening of digital transformation, the demand for online services is growing, especially the rapid growth of online Internet docking services, which has become an important fulcrum for the growth of financial enterprises. For Internet docking services, partners usually require quick and easy launch. How to quickly and efficiently complete technical docking and speed up the development process, debugging and testing process, and launch process is the key.

[0003] The existing mainstream technical solutions are mainly based on interface standardization and partial configurability, with the support of agile development mode and fully automatic release platform to accelerate the overall docking process. However, this solution still faces many traditional technical problems, such as: the long development period of customized interface code, the long offline interface joint debugging, and the limited and long process of enterprise deployment version cycle. Different enterprises have huge differences in organizational structure, technical base construction, manpower, etc., and further speeding up and improving efficiency will encounter significant bottlenecks. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a configuration-driven rapid partner docking method that can quickly adapt to the interface requirements of different partners or business scenarios, greatly reduce the experience requirements and maintenance difficulty of developers, and solve the bottleneck problem of speeding up and improving the efficiency of partner docking.

[0005] The technical solution adopted by the present invention to solve the above-mentioned technical problems is to provide a configuration-driven rapid partner docking method, including the following steps: S1, unifying the standard data model within the system; S2, designing the docking development content as components and customized rules to form interface docking components and rule libraries; S3, using the service orchestration engine to connect the components and rules in series according to the entire docking process; S4, using the page method to configure all standard data models, components, rules, and service orchestration contents on the development configuration platform, and storing them in the form of structured data; S5, encapsulating the configuration data, dynamic scripts, and third-party packages of the service orchestration, components, rules, and models generated by the development configuration, assembling the release package according to the batch version, and distributing them to the execution application server; S6, the execution application server uses the dynamic loading function to locally store and cache the configuration data in the batch release package, and dynamically load the dynamic script; S7, storing all configuration and deployment operations in the production environment server; binding with the release date through batch management to frame the specific release content.

[0006] Furthermore, the step S1 converts the interface parameters in different formats from different partners into an internal standardized model through a parameter conversion and mapping tool, and maps it to the data structure required for calling the internal business system.

[0007] Furthermore, the step S1 maps the partner docking interface field to the internal standard data model field in the following manner: direct mapping: when the source attribute and the target attribute are in a simple corresponding relationship, directly configure the source attribute node corresponding to the target attribute, map the data as is during conversion, and support setting default values. When the source attribute data is empty, take the set default value as the target attribute data; default value: when the target attribute has no corresponding source attribute, and it is a fixed value during conversion, only configure the target default value, and perform fixed filling of the default value; enumeration conversion: when the source attribute and the target attribute are enumeration types, configure the enumeration mapping relationship during conversion, enumerate the data during conversion, and then fill it into the target attribute; mapping processing through custom groovy script: when the value of the target attribute cannot be obtained from the source attribute through direct mapping or enumeration conversion, add custom rules and write groovy script code to process the value rules of the target attribute.

[0008] Furthermore, the step S2 analyzes the entire process of interfacing with the partner, splits each process action, identifies and extracts the common functional parts in each process action, and defines them as reusable common components; and sets the input and output parameters of each common component, and implements the specific functions within the common component using dynamic scripts.

[0009] Furthermore, the process actions include data reception, security verification, interface model conversion, verification, business logic processing, backend system call and response message assembly; the general function part includes data encryption and decryption, model conversion and rule verification.

[0010] Furthermore, the step S2 is to insert customized rules into the general component, the customized rules are implemented using dynamic scripts, and dynamic loading is selected during the configuration process.

[0011] Furthermore, the step S3 configures each node of the interface docking and its execution steps through a page-based flowchart, binds the corresponding execution components and rules to each node, and then connects all components and rule contents in series according to the business logic.

[0012] Furthermore, step S6 supports executing dual operation of primary and backup within the application, dynamically loading and publishing content when the backup is running without affecting the primary operation, swapping the primary and backup after loading is complete, and switching the backup operation to the primary operation, thereby realizing seamless deployment and switching of the interface service.

[0013] Furthermore, step S7 provides one-click deployment, rollback and version upgrade operations.

[0014] Furthermore, the dynamic script is a groovy dynamic script.

[0015] Compared with the prior art, the present invention has the following beneficial effects: the configuration-driven rapid partner docking method provided by the present invention can solve the bottleneck problem of partner docking speed and efficiency improvement, and realize the unified interface and full process control of partner docking. The specific advantages are as follows:

[0016] 1. Improve development efficiency through reusability and configurability:

[0017] The reuse rate of common functions is improved by detailed splitting of interface actions and extraction of common components.

[0018] The support for customized rules and the flexible configuration platform enable developers to quickly respond to changing needs of different partners or business scenarios, reducing development difficulty and cost.

[0019] 2. Enhance system flexibility and scalability:

[0020] The introduction of the service orchestration engine allows the interface docking process to be flexibly adjusted according to business logic, making it easy to cope with complex business scenarios.

[0021] Standardized parameter formats and conversion mechanisms ensure that the system can easily access data sources in different formats, improving the system's compatibility and scalability.

[0022] 3. Optimize user experience and operational convenience:

[0023] The intuitive and easy-to-use development configuration platform provides a page-based interface and rich configuration options, which lowers the operational threshold and enables non-technical personnel to participate in the configuration of interface docking.

[0024] A testing and joint debugging platform can be established to improve the quality and stability of interface docking through automated testing and joint debugging, and reduce the problems encountered by users during use. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is a schematic diagram of the configuration-driven rapid partner docking process of the present invention;

[0026] Figure 2 Insure flow chart for reduced standard interface. DETAILED DESCRIPTION

[0027] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0028] This invention focuses on solving the problems that affect the speed and efficiency of partner docking, and focuses on the solution to improve the overall development and deployment of the docking process:

[0029] Aiming at the high cost and long development period of customized interface code: the present invention introduces a development configuration platform, disassembles the docking development content, and divides it into steps and components, converts the original docking code development process into a page-based configuration process, supports version management, can quickly adapt to the interface requirements of different partners or business scenarios, and greatly reduces the developer experience requirements and maintenance difficulty.

[0030] In view of the limitations of system release versions and the long process: the present invention introduces a deployment platform, connects with the development platform and the execution application service, and makes the online process operation platform-based, online and visual. The online version content is pushed to the business application cluster through a series of hot deployment mechanisms, and the data and files are pushed to the business application cluster to take effect and provide services. It no longer follows the traditional online mode of compiling code, packaging and publishing content, executing data scripts, and deploying and restarting applications, and also avoids many limitations of the release version.

[0031] Developing platforms, deploying platforms, and executing application functions are not within the scope of partner docking to speed up and improve efficiency, and the traditional development and launch model can still be used.

[0032] See also Figure 1 The present invention aims to provide a more flexible, efficient and convenient interface docking optimization solution to meet the growing Internet docking business needs of enterprises. Specifically, it includes:

[0033] 1. Configuration development platform: Provides a one-stop page-based configuration development environment, including model management, component management, rule editing, service orchestration configuration, etc. It supports version management of configuration content, and developers can quickly and conveniently complete the configuration of interface docking.

[0034] 1. Standard model establishment: define a set of internal standardized data models as a "bridge" between external interfaces and other internal business systems. Through parameter conversion and mapping tools, interface parameters from different partners with different formats are converted into internal standardized models, and based on this, subsequent interface actions are performed, including mapping to the data structure required to call the internal business system. This process not only simplifies the data processing process, but also improves the compatibility and scalability of the system. Standard model metadata can be saved through the database.

[0035] 2. Extraction of common components: Conduct an in-depth analysis of the entire process of interface docking with partners, and carefully split each process action (such as data reception, security verification, interface model conversion, verification, business logic processing, back-end system calls, response message assembly, etc.). Subsequently, identify and extract the common functional parts in each process, such as data encryption and decryption, model conversion, rule verification, etc., and define them as reusable common components. Define the input and output parameters of each component, and the specific functions within the component can be implemented using dynamic scripts. The design of these components follows the principle of high cohesion and low coupling to ensure their flexibility and reusability in different interface docking scenarios.

[0036] 3. Customized rule support: Based on the common components, a flexible extension mechanism is designed to allow customized rules to be inserted outside the general logic of the components. For example, the blacklist verification component can choose whether to enable or use different blacklist data sources in different business scenarios. These rules can be selected and dynamically loaded during the configuration process to meet the special needs of specific partners or business scenarios. The specific functions of the rules can also be implemented using dynamic scripts.

[0037] 4. Service orchestration engine: The service orchestration engine is designed to provide interface function execution chain management capabilities, and all components and rule contents are connected in series according to business logic. Through page-based flowchart configuration, each node of interface docking and its execution steps can be flexibly defined. At each node, the corresponding components and rules can be bound. Service orchestration configuration data can be saved in the database. The engine can be implemented using tools such as rule flow and workflow.

[0038] 5. Version management: Service orchestration, components, rules, models, etc. all have independent versions, and all data, scripts, and files are stored in the production environment server. Batch management can be bound to the release date to frame the specific release content.

[0039] 2. Deployment management platform:

[0040] 1. Deployment content distribution: Encapsulate the service orchestration, components, rules, model configuration data, dynamic scripts, and third-party packages generated by the development configuration, assemble the release package by batch version, and distribute it to the execution application server.

[0041] 2. Dynamic loading of execution applications: On the execution application server, the configuration data in the batch release package is locally stored and cached through the dynamic loading function, and the dynamic scripts are dynamically loaded. It supports the execution of the main and standby dual runtimes in the application. The dynamic loading of the release content during the standby runtime does not affect the main runtime. After the loading is completed, the main and standby are swapped, and the standby runtime is switched to the main runtime, realizing seamless deployment and switching of the interface service.

[0042] 3. Deployment management function: The platform can complete service deployment, rollback, version upgrade and other operations with one click, and necessary approval processes can be added if necessary.

[0043] The present invention structurally decomposes the docking content into: interface standards, message parsing, model mapping, basic verification, business verification, routing, serial connection or distribution of downstream business systems. By encapsulating the above functions into components in accordance with business differences, using a service orchestration engine to serialize the functional components, and supporting the orchestration configuration process through a graphical interface, the full configuration of the docking development content is achieved. On the basis of full configuration of the docking content, all function verification tests, online debugging of partners, and deployment processes are carried out in the "Partner Online Docking Full Lifecycle Management Platform" of the production environment, which is very different from the traditional development environment to test environment to production environment, and effectively avoids the limitations of traditional deployment versions and technical platforms.

[0044] Here is a specific implementation example:

[0045] 1. Structurally define the interface definition, and quickly enter the fields defined in the partner's document into the system in a structured manner through import, text recognition, etc., as shown in the tree structure on the left of the figure below.

[0046] 2. Figure 2 A reduced standard interface insurance flow chart has been completed with structural decomposition and drawn using service orchestration and nodes.

[0047] 3. The original partner sends a request message, and the partner decrypts the received message.

[0048] 4. The first node of the interface is "Decryption Message". The configuration personnel select AFS decryption at this node and enter the secret key agreed with the partner. After the "Decryption Message" node is executed, the decrypted message is output to the execution context, and the process is executed to the next node.

[0049] 5. Execute to "Pre-model conversion". The input parameters of the corresponding component are "decrypted message of partner docking" (generated by the previous node), "partner interface field definition" (defined in step 1), and "standard model field definition" (standard unified, predefined), and the output parameter is "standard model". The rule parameter is the model mapping relationship, which needs to be entered manually.

[0050] 6. Specific model mapping, that is, mapping the partner docking interface fields to the standard model fields in the present invention, and configuring manual rules through the page:

[0051] (1) Direct mapping:

[0052] When the source attribute and the target attribute are simply corresponding, directly configure the source attribute node corresponding to the target attribute. The data will be mapped as is during conversion. It also supports setting default values. When the source attribute data is empty, the default value will be used as the target attribute data. After the page is configured, the actual business logic is implemented in the service orchestration process node through the customized model conversion component.

[0053] (2) Default value

[0054] When the target attribute has no corresponding source attribute and is a fixed value in the conversion, you can configure the target default value without configuring the source attribute and fill it with the default value. After the page is configured, the actual business logic is implemented in the service orchestration process node through the customized model conversion component.

[0055] (3) Enumeration conversion

[0056] When the source attribute and the target attribute are enumeration types, you can configure the enumeration mapping relationship in the conversion. During the conversion, the data will be enumerated and mapped, and then filled into the target attribute. After the page is configured, in the service orchestration process node, the actual business logic is implemented through the customized model conversion component.

[0057] (4) Complex processing mapping, processed by custom groovy scripts

[0058] When the value of the target attribute cannot be obtained from the source attribute through direct mapping or enumeration conversion, you can add custom rules and write groovy script code to process the value rules of the target attribute, such as the rules for obtaining birthday and gender through ID cards, the rules for processing target characteristic information, etc. After the page is configured, the customized rule script will be obtained in the service orchestration process node to implement the actual business logic.

[0059] 7. After the "Pre-model conversion" node is executed, the standard model is obtained and placed in the execution context as the input parameter required by the subsequent nodes, and the process flows to the next node.

[0060] 8. This process continues in this way until the service orchestration process is completed and a response message is returned to the partner.

[0061] As can be seen from the above, the present invention disassembles the routing / forwarding, verification, field mapping, enumeration value mapping, and business call processes in the docking development process, completes component standardization, and realizes full configuration on this basis. The docking service is separated from the configuration during runtime, and the business docking service function is realized through dynamic loading. The debugging process is assisted in visualization and automation to achieve one-stop debugging. Based on the above sub-platforms, combined with the formulation of personnel and processes, an effective operation and management mechanism covering the entire life cycle of the docking is formed.

[0062] After the technical solution of the present invention is launched, the overall development cycle is compressed by 50% to 0-3 days, the partner debugging cycle is compressed by 50% to 0-4 days, and the development and launch cycle is compressed by 50% to 2-10 days. It is no longer dependent on the traditional release version restrictions, and the docking and launch efficiency is greatly improved.

[0063] Although the present invention has been disclosed as above with preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art may make some modifications and improvements without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be based on the definition of the claims.

Claims

1. A configuration-driven rapid partner docking method, characterized in that: The steps include: S1. Standard data model within the unified system; S2. Design the docking development content into components and customized rules to form a component and rule library for interface docking; S3. Use the service orchestration engine to connect components and rules in series according to the entire docking process; S4. Configure all standard data models, components, rules, and service orchestration content in a page-based manner on the development configuration platform and store them in a structured data manner; S5. Encapsulate the service orchestration, components, rules, model configuration data, dynamic scripts, and third-party packages generated by the development configuration, assemble the release package by batch version, and distribute it to the execution application server; S6. The execution application server uses the dynamic loading function to locally store and cache the configuration data in the batch release package and dynamically load the dynamic script; S7. Store all configuration and deployment operations in the production environment server; Batch management is bound to the release date to define the specific release content.

2. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The step S1 converts the interface parameters in different formats from different partners into an internal standardized model through a parameter conversion and mapping tool, and maps them to the data structure required for calling the internal business system.

3. The configuration-driven rapid partner docking method according to claim 2, characterized in that: The step S1 maps the partner docking interface fields to the internal standard data model fields in the following manner: Direct mapping: When the source attribute and the target attribute are in a simple correspondence relationship, directly configure the source attribute node corresponding to the target attribute, and map the data as it is during conversion. It also supports setting default values. When the source attribute data is empty, the default value set is used as the target attribute data; Default value: When the target attribute has no corresponding source attribute and is a fixed value in the conversion, only the target default value is configured and the default value is fixedly filled; Enumeration conversion: When the source attribute and the target attribute are of enumeration type, configure the enumeration mapping relationship in the conversion, perform enumeration mapping on the data during the conversion, and then fill it into the target attribute; Mapping processing through custom groovy scripts: When the value of the target attribute cannot be obtained from the source attribute through direct mapping or enumeration conversion, add custom rules and write groovy script code to process the value rules of the target attribute.

4. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The step S2 analyzes the entire process of interface docking with the partner, and after splitting each process action, identifies and extracts the common functional parts in each process action, defining them as reusable common components; and sets the input and output parameters of each common component, and the specific functions in the common component are implemented using dynamic scripts.

5. The configuration-driven rapid partner docking method according to claim 4, characterized in that: The process actions include data reception, security verification, interface model conversion, verification, business logic processing, backend system call and response message assembly; the general function part includes data encryption and decryption, model conversion and rule verification.

6. The configuration-driven rapid partner docking method according to claim 4, characterized in that: The step S2 is to insert customized rules into the general component. The customized rules are implemented using dynamic scripts, and dynamic loading is selected during the configuration process.

7. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The step S3 configures each node and its execution steps of the interface docking through a page-based flowchart, binds the corresponding execution components and rules to each node, and then connects all components and rule contents in series according to the business logic.

8. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The step S6 supports the execution of dual operation of the main and backup in the application, dynamically loading the published content when the backup is running without affecting the main operation, and swapping the main and backup after loading is completed, and switching the backup operation to the main operation to achieve seamless deployment and switching of the interface service.

9. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The step S7 provides one-click deployment, rollback and version upgrade operations.

10. The configuration-driven rapid partner docking method according to claim 1, characterized in that: The dynamic script is a groovy dynamic script.

Images