Low-code secondary development method and system for self-service channel backend microservices

Abstract

The present invention discloses a low-code secondary development method and system for self-service channel backend microservices, wherein the system includes a channel business system backend operating platform and a channel business system backend secondary development platform; the channel business system backend secondary development platform is used for project visualization development; the channel business system backend operating platform is used to run the projects developed by the channel business system backend secondary development platform, and provides channel access sub-services, channel business processing sub-services, and channel access sub-services. It can meet the visual development of self-service channel backend systems based on microservice architecture, especially meet the dynamic creation of channel access communication servers and channel access communication clients through visualization, meet multi-channel access and access, and perform message configuration and business process design under the channel through visualization. The developed project resources can be deployed to the channel business system backend operating platform, which can meet the visual development of multiple services.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a low-code secondary development method and system for self-service channel backend microservices. Background Art

[0002] As industries such as finance, insurance, government affairs, taxation, and transportation accelerate and deepen the development and transformation of self-service channels, their counter systems or other channel system businesses are constantly migrating to self-service channels (smart ATMs). As the business system of self-service channels, the self-service channel system plays a very important role in expanding the scale of the industry, diverting counter business, alleviating counter pressure, improving service efficiency, and enhancing competitiveness. Different industries and different businesses in the same industry have different implementations in scenarios, processes, and interaction methods. As a self-service channel service provider, in order to realize the self-service channel systems in these industries, there must be a large amount of customized development, which is developed in a non-visual way and consumes a lot of manpower costs for system development and maintenance, which greatly affects the speed of business migration and transformation of customers in these industries, and at the same time affects the market share of self-service channel service providers.

[0003] While many low-code development platforms exist, most are targeted at systems with rigid processes, such as OA systems, or those that are more oriented towards front-end interactive systems. Visual low-code development for back-end systems, especially those based on microservices for self-service channels, is rare, if not nonexistent. Self-service channel back-end systems require integration with multiple client systems and adaptability to a wide range of communication protocols, message protocols, and business logic. Implementing all of this through code would severely impact project delivery schedules and quality.

[0004] Therefore, providing a low-code visual secondary development system and method based on a more widely used technical framework can not only ensure its advanced nature, but also lower the technical threshold, and realize the low-code rapid development of business functions in multiple industries, multiple scenarios, and different processes, which has become an urgent problem to be solved by current self-service channel service providers. Summary of the Invention

[0005] In response to the shortcomings in the existing technology, the purpose of the present invention is to provide a low-code secondary development system and method for self-service channel back-end microservices, so as to lower the technical threshold and realize low-code rapid development of business functions in multiple industries, multiple scenarios and different processes.

[0006] First, a low-code secondary development method for self-service channel backend microservices is provided. This method is based on the channel business system backend operation platform and the channel business system backend secondary development platform, and includes the following steps:

[0007] Use the back-end secondary development platform of the channel business system to carry out project visual development, including: creating access channels and configuring corresponding adapters and messages, creating business processes, creating outgoing channels and configuring corresponding adapters and messages;

[0008] Deploy the projects developed using the secondary development platform of the channel business system backend to the channel business system backend operation platform for operation. The operation process includes the channel access sub-service, channel business processing sub-service, and channel access sub-service. When each sub-service is started, the business processes, various channels, corresponding adapters, and messages created by the secondary development platform of the channel business system backend are loaded into the cache for invocation.

[0009] The channel access sub-service creates a corresponding communication service end according to the access channel and the corresponding adapter and message, receives the request from the channel requester, parses the message, and forwards the parsed data to the channel business processing sub-service for processing; after the processing is completed, the processing result is assembled into a message and returned to the channel requester;

[0010] The channel business processing sub-service obtains and executes the corresponding business process based on the request forwarded by the channel access sub-service. If there is an outgoing request in the business, the channel outgoing sub-service is called to make an external system call; after the processing is completed, the processing result is returned to the channel access sub-service;

[0011] The channel access sub-service receives the request sent by the channel business processing sub-service, assembles the message, creates a communication client based on the access channel and the corresponding adapter, and sends the assembled message to the target external system for processing; after the processing is completed, the processing result is parsed and returned to the channel business processing sub-service.

[0012] Furthermore, the process of the channel accessing the sub-service specifically includes:

[0013] Create a corresponding communication server based on the access channel, corresponding adapter, and message, and receive requests from the channel requester;

[0014] Obtain the depacketization message configuration corresponding to the channel requester's request through the transaction code, and use the message depacketization component to parse the message;

[0015] According to the access channel, message, and business process relationship created by the secondary development platform of the channel business system backend, the parsed message is stored in the data structure of the unified data bus and forwarded to the channel business processing sub-service for processing;

[0016] After the processing is completed, the corresponding package message configuration requested by the channel requester is obtained through the transaction code, the message package component is used to assemble the processing result, and the assembled message is returned to the channel requester.

[0017] Furthermore, the process of the channel business processing sub-service specifically includes:

[0018] Based on the request forwarded by the channel access sub-service, the business process code is obtained from the data structure of the unified data bus, and the corresponding business process is found and executed;

[0019] If there is an outbound request in the business, the channel outbound sub-service is called to make an external system call and forward it to the external system for processing;

[0020] After the processing is completed, the processing results will be stored in the data structure of the unified data bus and returned to the channel access sub-service.

[0021] Furthermore, the specific process of the channel accessing the sub-service includes:

[0022] Receive requests from the channel business processing sub-service;

[0023] By obtaining the transaction code from the data structure of the unified data bus, finding the corresponding packet assembly message configuration for the request, and assembling the message using the message assembly component;

[0024] Create a communication client based on the transaction component parameters, where the transaction component parameters include the access channel number, the corresponding adapter number, and the transaction code;

[0025] Send the assembled message to the target external system for processing;

[0026] After the processing is completed, the unpacking message configuration corresponding to the request is obtained through the transaction code, and the message unpacking component is used to parse the processing result;

[0027] The parsed data is stored in the data structure of the unified data bus and returned to the channel business processing sub-service.

[0028] Furthermore, the back-end secondary development platform of the channel business system is used to carry out project visualization development. The process includes:

[0029] Create a project and configure it;

[0030] Conduct channel management based on projects, including creating access channels and outgoing channels;

[0031] Create corresponding adapters based on the inbound and outbound channels and configure the adapters;

[0032] Create corresponding messages based on the incoming and outgoing channels and configure them;

[0033] Create business systems based on projects and create new business processes;

[0034] Design business processes based on visual development methods;

[0035] Maintain the relationship between access channels, outgoing channels, messages, and business processes, and associate them through transaction codes.

[0036] Furthermore, after completing the business process design, it also includes process verification, sending the designed business process to the channel business system back-end operation platform for verification, so as to verify whether the business process is designed correctly.

[0037] Furthermore, the step of creating corresponding messages based on the access channel and the access channel and configuring the messages includes:

[0038] Create a new access channel depacketization message based on the access channel and configure the access channel depacketization message;

[0039] Create a new access channel grouping message based on the access channel and configure the access channel grouping message;

[0040] Create a new outgoing channel packet grouping message based on the outgoing channel and configure the outgoing channel packet grouping message;

[0041] Create an outgoing channel depacketization message based on the outgoing channel and configure the outgoing channel depacketization message.

[0042] In a second aspect, a low-code secondary development system for self-service channel backend microservices is provided, which is used to implement the low-code secondary development method for self-service channel backend microservices as described above, and the system includes a channel business system backend operation platform and a channel business system backend secondary development platform;

[0043] The channel business system backend secondary development platform is used for project visualization development;

[0044] The channel business system backend operation platform is used to run the projects developed by the channel business system backend secondary development platform, and provides channel access sub-services, channel business processing sub-services, and channel access sub-services.

[0045] Furthermore, the channel business system backend secondary development platform includes backend services and client tools; the client tools are used to provide a visual editing interface for project visual development; the backend services provide interface services for the client tools and process operation requests submitted by the client tools.

[0046] Furthermore, the back-end operating platform and back-end services of the channel business system adopt the Spring Cloud microservice architecture, and the client tool adopts the VUE+Element UI+HTML5+MXGRAPH architecture.

[0047] The present invention proposes a low-code secondary development method and system for self-service channel back-end microservices, which can meet the visual development of self-service channel back-end systems based on microservice architecture, and especially meet the requirements of dynamic creation of channel access communication server and channel access communication client in a visual manner, meet multi-channel access and access, and at the same time, can perform message configuration and business process design under the channel in a visual manner. The developed project resources can be respectively deployed to the channel access sub-service, channel access sub-service and business processing sub-service of the channel business system back-end operation platform. The secondary development platform provided by the present invention can simultaneously meet the visual development of multiple services. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0049] Figure 1 This is a schematic diagram of a low-code secondary development system framework for self-service channel backend microservices provided by an embodiment of the present invention;

[0050] Figure 2 This is a schematic diagram of the functional modules of the back-end operation platform of the channel business system provided by an embodiment of the present invention;

[0051] Figure 3 Schematic diagram of the channel access sub-service processing flow provided by an embodiment of the present invention;

[0052] Figure 4 This is a schematic diagram of the channel business processing sub-service processing flow provided by an embodiment of the present invention;

[0053] Figure 5 This is a schematic diagram of the channel access sub-service processing flow provided by an embodiment of the present invention;

[0054] Figure 6 This is a schematic diagram of the architecture of the back-end secondary development platform of the channel business system provided by an embodiment of the present invention;

[0055] Figure 7 This is a schematic diagram of the low-code secondary development process for self-service channel backend microservices provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] To make the objectives, technical solutions, and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other implementations obtained by those of ordinary skill in the art without inventive effort are within the scope of protection of the present invention.

[0057] like Figure 1 As shown, an embodiment of the present invention provides a low-code secondary development system for self-service channel backend microservices, which includes a channel business system backend operation platform and a channel business system backend secondary development platform.

[0058] The backend operation platform of the channel business system adopts the Spring Cloud microservice architecture. It includes channel access sub-service, channel business processing sub-service, and channel outgoing sub-service, corresponding to Figure 1 In the channel access layer service, business processing layer service, and channel output layer service, each service loads the channel, adapter, message, and business process data generated by the secondary development platform of the channel business system backend into the cache for use when it is started. The services use a unified data bus as the data structure for message transmission. Figure 2 As shown, a functional module diagram of the back-end operating platform of the channel business system is provided; it includes a resource configuration module, a channel access and access module, a business processing module, and a platform basic module; the channel access and access module can load the resource configuration module and call the platform basic module to implement the channel access sub-service and the channel access sub-service; the business processing module can load the resource configuration module and call the platform basic module to implement the channel business processing sub-service; two-way calls are made between the channel access and access module and the business processing module.

[0059] Specifically, the process of the channel access sub-service includes: creating a corresponding communication service end according to the access channel and the corresponding adapter and message, receiving the request from the channel requester; obtaining the unpacking message configuration corresponding to the channel requester's request through the transaction code, and parsing the message using the message unpacking component; storing the parsed message in the data structure of the unified data bus according to the access channel, message, and business process relationship created by the secondary development platform of the channel business system backend, and forwarding it to the channel business processing sub-service for processing; after the processing is completed, obtaining the packaged message configuration corresponding to the channel requester's request through the transaction code, using the message package component to assemble the processing result, and returning the assembled message to the channel requester. Figure 3 The figure shows a specific processing flow diagram of the channel access sub-service.

[0060] The process of the channel business processing sub-service includes: according to the request forwarded by the channel access sub-service, by obtaining the business process code from the data structure of the unified data bus, finding the corresponding business process and executing it; if there is an outbound request in the business (accessing other external services), calling the channel outbound sub-service to call the external system and forwarding it to the external system for processing; after the processing is completed, the processing result is stored in the data structure of the unified data bus and returned to the channel access sub-service. Figure 4 The figure shows the specific processing flow diagram of the channel business processing sub-service.

[0061] The process of the channel access sub-service includes: receiving a request from the channel business processing sub-service; obtaining the transaction code from the data structure of the unified data bus, finding the packet configuration corresponding to the request, and assembling the message using the message assembly component; creating a communication client according to the transaction component parameters, where the transaction component parameters include the access channel number, the corresponding adapter number, and the transaction code; sending the assembled message to the target external system for processing; after the processing is completed, obtaining the unpacking message configuration corresponding to the request through the transaction code, and using the message unpacking component to parse the processing result; storing the parsed data in the data structure of the unified data bus and returning it to the channel business processing sub-service. Figure 5 The figure shows the specific processing flow diagram of the channel access sub-service.

[0062] The channel business system backend operation platform also provides process verification and project deployment service interfaces for the channel business system backend secondary development platform to call, making it convenient to perform operation verification on projects created by the channel business system backend secondary development platform.

[0063] In this embodiment, the channel business system back-end secondary development platform includes back-end services and client tools, such as Figure 6 The following is a schematic diagram of the back-end secondary development platform architecture of the channel business system. Figure 6 The service layer and WEB layer correspond to the backend services and client tools respectively.

[0064] The backend service uses the Spring Cloud microservices architecture. It provides interface services for client tools and handles operation requests submitted by client tools, such as workspace creation, project maintenance (creation, deletion, and configuration), channel maintenance (creation, deletion, and configuration), communication adapter maintenance (creation, deletion, and configuration), message maintenance (creation, deletion, and configuration), business maintenance (creation, deletion, and configuration), and business process maintenance (creation, deletion, and configuration).

[0065] The backend service is also used to receive process verification requests initiated by client tools and send the designed and developed business processes to the channel business system backend operation platform for verification to verify whether the business processes are designed correctly. It is also used to receive project deployment requests initiated by client tools and send the designed and developed project resources to the channel business system backend operation platform for deployment and implementation to complete project deployment. It is also used to receive platform public business component record requests initiated by client tools and return a list of platform public business components provided by the channel business system backend operation platform to the client tool.

[0066] The client tool adopts the VUE+Element UI+HTML5+MXGRAPH architecture and has the following features:

[0067] 1) Use Electron to package it into an executable graphical desktop EXE program;

[0068] 2) After the client tool is started, it first obtains workspace information from the backend service and provides the operation functions of selecting and entering the workspace on the interface;

[0069] 3) After entering the workspace, enter the tool main interface, which adopts a left-right structure layout, with the project directory tree view area on the left and the business process design view area on the right;

[0070] 4) The project directory tree view area provides interface operation functions in the workspace;

[0071] 5) Provide interface operation functions for creating projects in the workspace;

[0072] 6) Provide interface operation functions for creating channels, adapters, messages, and relationships in the project;

[0073] 7) Provide interface operation functions for creating business systems and business processes in the project;

[0074] 8) Business process visual design can be performed in the business process design view;

[0075] 9) The business process design view area includes the function area, component library toolbox, and process display and editing area;

[0076] 10) The function area includes save and compile function buttons;

[0077] 11) The component library toolbox includes process components, business components, and sub-process components;

[0078] 12) Process components include start, script, end, signal, branch node, merge node, parallel branch, and parallel merge icons

[0079] 13) Business components display public platform business components;

[0080] 14) The sub-process component displays other business processes besides the current business process;

[0081] 15) Provide public platform business component loading function for reference in process design.

[0082] The low-code secondary development system for self-service channel backend microservices provided in the above embodiment can meet the visual development of self-service channel backend systems based on microservice architecture, and in particular can meet the requirements of dynamic creation of channel access communication server and channel access communication client in a visual manner, meet multi-channel access and access, and at the same time can perform message configuration and business process design under the channel in a visual manner. The developed project resources (channel configuration, adapter configuration, message configuration, process configuration) can be deployed to the channel access sub-service, channel access sub-service, and channel business processing sub-service of the backend operation platform respectively. The secondary development platform provided by the present invention can meet the visual development of multiple services at the same time.

[0083] Based on the low-code secondary development system for self-service channel backend microservices provided in the above embodiment, an embodiment of the present invention further provides a low-code secondary development method for self-service channel backend microservices, including the following steps:

[0084] Step 1: Create a workspace through the client tool interface of the channel business system backend secondary development platform;

[0085] Step 2: Create a project in the client tool interface workspace;

[0086] Step 3: Configure the project (project release path, database configuration) on the client tool interface;

[0087] Step 4: Manage channels on the client tool interface (create new access channels, create new outgoing channels, delete channels);

[0088] Step 5: Perform communication adapter maintenance (create a new adapter, delete an adapter, modify adapter parameters) on the client tool interface.

[0089] Step 6: Perform communication message maintenance (creating new messages, deleting messages, and configuring messages) on the client tool interface.

[0090] Step 7: Manage business on the client tool interface (create a new business system, delete a business system, create a new business process, delete a business process);

[0091] Step 8: Design the business process on the client tool interface (develop the business process and business sub-process on the process design interface using the icons, connections, process nodes, and components provided on the interface). After completing the business process design, you can verify the process using the process verification function on the interface.

[0092] Step 9: Maintain the relationships between channels, messages, and business processes on the client tool interface (create, edit, and delete relationships), and associate channels, messages, and business processes using transaction codes.

[0093] Step 10: Perform public function maintenance on the client tool interface (creating a new platform process, deleting a new platform process, and maintaining platform component parameters);

[0094] Step 11: Through the project deployment function, the channels, messages, business processes, and their relationships developed by the secondary development platform of the channel business system backend are packaged and published to the channel business system backend operation platform for automatic deployment and operation;

[0095] Step 12: During the operation of the back-end operation platform of the channel business system, the channel access sub-service, channel business processing sub-service, and channel access sub-service are started and run.

[0096] Below, taking the implementation of a self-service balance inquiry channel of a financial institution as an example, its working mechanism is explained, and how to develop from scratch using the secondary development system and method provided by the present invention is demonstrated, including the following process.

[0097] S01: Create a workspace. Click the [Select] button on the client tool interface of the channel business system backend secondary development platform, select the specified directory as the current project workspace, and click the [OK] button to create the workspace and enter the workspace.

[0098] S02: Create a new project. In the project directory tree on the left side of the client tool interface, select [Project], right-click, and select [New Project] from the pop-up menu. In the pop-up New Project dialog box, enter the project name "A Certain Bank Self-Service Channel Project" and click [Confirm] in the dialog box to complete the project creation. A project directory tree node "A Certain Bank Self-Service Channel Project" will be generated in the project directory tree.

[0099] S03: Configure the project. Select the project directory tree node "A Certain Bank Self-Service Channel Project" on the interface, right-click, and select [Project Configuration] from the pop-up menu. In the pop-up Project Configuration dialog box, enter the project name "A Certain Bank Self-Service Channel Project" and configure the project (project release path, database configuration).

[0100] S04: Create a new access channel. Double-click the "Self-service channel project of a certain bank" tree node on the interface. The tree node will expand the sub-nodes "Channel", "Business", and "Public". Select the sub-node "Channel" and right-click. Select the [New Access Channel] menu item in the pop-up menu. In the pop-up New Access Channel dialog box, enter the channel code: 101 and the channel name: Self-service channel. Click [Confirm] in the dialog box to complete the access channel creation. At this time, the "101 [Self-service channel]" channel directory tree node will be generated in the project directory tree.

[0101] S05: Create a new access channel adapter. Double-click the "101 [Self-service Channel]" channel directory tree node on the interface. The tree node will expand the sub-nodes "Adapter", "Message", and "Relationship". Select the sub-node "Adapter", right-click the mouse, and select the [New Adapter] menu item in the pop-up menu. In the pop-up New Adapter dialog box, select the adapter type as "HTTP_SERVER" and enter the adapter code: 101. Click [Confirm] in the dialog box to complete the creation of the communication adapter. At this time, the "101 [HTTP_SERVER]" adapter directory tree node will be generated in the directory tree. Double-click the node and enter the maximum flow limit in the pop-up dialog box. The default is 0 (unlimited). Click the [Save] button in the dialog box to complete the adapter parameter configuration.

[0102] S06: Create a new access channel unpacking message. Select the "Message" subnode under the "101 [Self-service Channel]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "decode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the access channel general unpacking message. At this time, the subnode "decode.msg" is generated under the "Message" node in the directory tree; select the "Message" subnode under the "101 [Self-service Channel]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "1011010001_decode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the access channel balance inquiry (channel transaction code 1011010001) transaction unpacking message. At this time, the subnode "1011010001_decode.msg" is generated under the "Message" node in the directory tree;

[0103] S07: Configure the access channel to unpack the message. Double-click the general unpacked message node "decode.msg" created in step S06, and edit the message in the message configuration dialog box that pops up. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "decode-unpacking" and the message policy to "json-JSON format" in the form on the right. Click the [Submit] button on the form to submit and save. Select the default root node in the directory tree on the left of the dialog box, right-click, and select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node. Select the "Field" node and configure the field name to "p_trans_code" in the form on the right. Set the field description to "Transaction Code", set the field type to "string", set the JPATH path to "chanHeader.transId", set whether it is required to "true", and click the [Submit] button on the form to submit and save; in the message configuration dialog box, select the root node in the directory tree on the left, right-click, and select [Add Child Node] - [Reference] menu item in the pop-up menu to generate the "Reference" child node, select the "Reference" node, and configure the reference message definition to "${p_trans_code}+"_decode"" in the form on the right, and click the [Submit] button on the form to submit and save. At this time, the channel access general decompression message "decode.msg" configuration is completed.Double-click the balance inquiry transaction unpacking message node "1011010001_decode.msg" created in step S06, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "decode-unpacking" and the message strategy to "json-JSON format" in the form on the right. Click the [Submit] button on the form to submit and save; select the default root node in the directory tree on the left of the dialog box, right-click, and select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node. Select the "Field" node, and in the form on the right, configure the field name to "cardNo", set the field description to "Card Number", and set the field type to "string-character String", set the JPATH path to "business.cardNo", set whether it is required to "true-Yes", and click the [Submit] button on the form to submit and save; similarly, right-click on the root node, select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node, select the "Field" node, configure the field name to "pin" in the form on the right, set the field description to "Card Password", set the field type to "string-String", set the JPATH path to "business.pin", set whether it is required to enter to "true-Yes", and click the [Submit] button on the form to submit and save; now the configuration of the balance query transaction channel access decompression message "1011010001_decode.msg" is complete;.

[0104] S08: Create a new business process. Select the subnode "Business" under the "A Bank Self-Service Channel Project" tree node on the interface, right-click, and select the [New Business System] menu item in the pop-up menu. In the pop-up New Business System dialog box, enter the business system code as "100" and the business system name as "Self-Service Business". Click the [Confirm] button in the dialog box to complete the business system creation. At this time, the subnode "100 [Self-Service Business]" is generated under the node "Business". Select this node, right-click, and select the [New Business Process] menu item in the pop-up menu. In the pop-up New Business Process dialog box, enter the business process code as "100001" and the business process name as "Balance Inquiry". Click the [Confirm] button in the dialog box to complete the business process creation. At this time, the business process node "100001 [Balance Inquiry]" is generated under the business system node "100 [Self-Service Business]".

[0105] S09: Design the business process. Double-click the business process node "100001 [Balance Inquiry]" generated in step S08. The business process view will open on the right. Select the [Start] icon in the component library toolbox and drag it to the process editing area. Select the [End] icon in the component library toolbox and drag it to the process editing area. Select the [Background Request Component] in the component library toolbox and drag it to the process editing area. Click the [Start] icon in the process editing area and drag the mouse over the [Background Request Component] icon to generate a connection between [Start] and [Background Request Component]. Click the [Background Request Component] icon in the process editing area and drag the mouse over the [End] icon to generate a connection between [Background Request Component] and [End]. Right-click the [Background Request Component] icon in the process editing area to edit the component parameters. Enter the component parameter channel access transaction code 5015010001 in the component parameter edit box. Click the [Save] icon in the component library toolbox to save the business process and complete the business process design.

[0106] S10: Create a new outgoing channel. Select the "Channel" subnode under the "A Bank Self-Service Channel Project" tree node on the interface, right-click, and select "New Outgoing Channel" from the pop-up menu. In the New Outgoing Channel dialog box that pops up, enter the channel code: 501 and the channel name: Integrated Front-End System. Click "Confirm" in the dialog box to complete the creation of the outgoing channel. At this time, the "501 [Integrated Front-End System]" channel directory tree node will be generated in the project directory tree.

[0107] S11: Create a new outgoing channel adapter. Double-click the "501 [Integrated Front-end System]" channel directory tree node on the interface. The tree node will expand the sub-nodes "Adapter" and "Message". Select the sub-node "Adapter", right-click the mouse, and select the [New Adapter] menu item in the pop-up menu. In the pop-up New Adapter dialog box, select the adapter type as "TCP_SHORT_CLIENT", enter the adapter code: 501, and click [Confirm] in the dialog box to complete the creation of the communication adapter. At this time, the "501 [TCP_SHORT_CLIENT]" adapter directory tree node will be generated in the directory tree. Double-click the node and configure the communication adapter parameters in the pop-up dialog box. Set the communication address to the integrated front-end system address "127.0.0.1:9527" and set the packet receiving strategy to "0-fixed".

[0108] Set the pre-read length to 0, the length field start position to 0, the length field end position to 0, the length field encoding format to "ASCII", the length correction value to 0, the timeout period to 60000, and click the [Save] button in the dialog box to complete the adapter parameter configuration;

[0109] S12: Create a new outgoing channel package message, select the "Message" sub-node under the "501 [Integrated Front-end System]" directory tree node on the interface, right-click the mouse, select the [New Message] menu item in the pop-up menu, enter the message name "encode" in the pop-up new message dialog box, click [Confirm] in the dialog box to complete the creation of the outgoing channel general package message, and now the sub-node "encode.msg" is generated under the "Message" node in the directory tree; select the "501 [Integrated Front-end System]" on the interface. Right-click the "Message" subnode under the "System" directory tree node and select "New Message" from the pop-up menu. In the pop-up New Message dialog box, enter the message name "5015010001_encode" and click "Confirm" in the dialog box to complete the creation of the transaction package message for the outgoing channel balance query (prefix transaction code 5015010001). A subnode "5015010001_encode.msg" is now generated under the "Message" node in the directory tree.

[0110] S13: Configure the outgoing channel package message. Double-click the universal package message node "encode.msg" created in step S12, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "encode-package" and the message policy to "xml-XML format" in the form on the right. Click the [Submit] button on the form to submit and save. In the message configuration dialog box, select the root node in the directory tree on the left, right-click, and select [Add Child Node] - [Reference] in the pop-up menu to generate the "Reference" child node. Select the "Reference" node and configure the reference message definition as "${p_backend_trans_code}+"_encode"" in the form on the right. Click the [Submit] button on the form to submit and save. The channel outgoing universal package message "encode.msg" configuration is now completed. Double-click the balance inquiry transaction package message node "5015010001_encode.msg" created in step S12, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "encode-package" and the message strategy to "xml-XML format" in the form on the right. Click the [Submit] button on the form to submit and save; select the default root node in the directory tree on the left of the dialog box, right-click, and select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node. Select the "Field" node, and in the form on the right, configure the field name to "cardNo", set the field description to "Transaction Account Number", set the field type to "string-string", and set the XPATH path to " / transac tion / body / request / priAccountNumber", set "Required" to "true", and click the [Submit] button on the form to submit and save. Similarly, right-click on the root node, select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node, select the "Field" node, and in the form on the right, configure the field name to "pin", set the field description to "Card Password", set the field type to "string", set the XPATH path to " / transaction / body / request / pin", set "Required" to "true", and click the [Submit] button on the form to submit and save. At this time, the configuration of the balance query transaction channel to extract the package message "5015010001_encode.msg" is completed.

[0111] S14: Create a new unpacked message for the access channel. Select the "Message" subnode under the "501 [Integrated Front-end System]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "decode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the access channel general unpacked message. At this time, the subnode "decode.msg" is generated under the "Message" node in the directory tree; select the "Message" subnode under the "501 [Integrated Front-end System]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "5015010001_decode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the unpacked message for the outgoing channel balance inquiry (transaction code 5015010001) transaction. At this time, the subnode "5015010001_decode.msg" is generated under the "Message" node in the directory tree;

[0112] S15: Configure the outgoing channel unpacking message. Double-click the general unpacking message node "decode.msg" created in step S14, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "decode-unpacking" and the message policy to "xml-XML format" in the form on the right. Click the [Submit] button on the form to submit and save. In the message configuration dialog box, select the root node in the directory tree on the left, right-click, and select [Add Child Node] - [Reference] in the pop-up menu to generate the "Reference" child node. Select the "Reference" node and configure the reference message definition as "${p_backend_trans_code}+"_decode"" in the form on the right. Click the [Submit] button on the form to submit and save. The channel outgoing general unpacking message "decode.msg" configuration is now completed.Double-click the balance inquiry transaction unpacking message node "5015010001_decode.msg" created in step S14. In the pop-up message configuration dialog box, edit the message. Select the default root node in the directory tree on the left of the dialog box. Then, in the form on the right, set the message type to "decode" and the message strategy to "xml-XML format". Click the [Submit] button on the form to submit and save. Select the default root node in the directory tree on the left of the dialog box. Right-click and select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node. Select the "Field" node. In the form on the right, configure the field name to "retCode", set the field description to "Response Code", set the field type to "string-string", set the XPATH path to " / transaction / body / retCode", set whether the input is required to "true-yes", and click the [Submit] button on the form to submit and save. Similarly, right-click on the root node and select [Add Child Node] - [Field] in the pop-up menu. Generate a "Field" child node. Select the "Field" node. In the form on the right, configure the field name to "retMsg", set the field description to "Response Message", set the field type to "string", set the XPATH path to " / transaction / body / desc", set whether the input is required to "true", and click the [Submit] button on the form to save. Similarly, right-click the root node and select [Add Child Node] - [Field] from the pop-up menu to create a "Field" child node. Select the "Field" node. In the form on the right, configure the field name to "currentBalance", set the field description to "Current Balance", set the field type to "string", set the XPATH path to " / transaction / body / currentBalance", set whether the input is required to "true", and click the [Submit] button on the form to save. This completes the configuration of receiving the decompressed message "5015010001_decode.msg" from the balance query transaction channel.

[0113] S16: Create a new access channel package message. Select the "Message" subnode under the "101 [Self-Service Channel]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "encode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the access channel general package message. At this time, the subnode "encode.msg" is generated under the "Message" node in the directory tree; select the "Message" subnode under the "101 [Self-Service Channel]" directory tree node on the interface, right-click the mouse, select the "New Message" menu item in the pop-up menu, enter the message name "1011010001_encode" in the pop-up New Message dialog box, and click "Confirm" in the dialog box to complete the creation of the access channel balance inquiry (transaction code 1011010001) transaction package message. At this time, the subnode "1011010001_encode.msg" is generated under the "Message" node in the directory tree;

[0114] S17: Configure the access channel package message. Double-click the universal package message node "encode.msg" created in step S16, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, and then set the message type to "encode-package" and the message policy to "json-JSON format" in the form on the right. Click the [Submit] button on the form to submit and save. In the message configuration dialog box, select the root node in the directory tree on the left, right-click, and select [Add Child Node] - [Reference] in the pop-up menu to generate the "Reference" child node. Select the "Reference" node and configure the reference message definition as "${p_trans_code}+"_decode"" in the form on the right. Click the [Submit] button on the form to submit and save. At this time, the channel access universal package message "encode.msg" configuration is completed.Double-click the balance inquiry transaction package message node "1011010001_encode.msg" created in step S16, and edit the message in the pop-up message configuration dialog box. Select the default root node in the directory tree on the left of the dialog box, then set the message type to "encode-package" and the message strategy to "json-JSON format" in the form on the right, and click the [Submit] button on the form to submit and save. Select the default root node in the directory tree on the left of the dialog box, right-click, and select [Add Child Node] - [Field] in the pop-up menu to generate the "Field" child node. Select the "Field" node, and in the form on the right, configure the field name to "retCode", set the field description to "Response Code", set the field type to "string-string", set the JPATH path to "chanHeader.retCode", set whether it is required to be entered to "true-Yes", and click the [Submit] button on the form to submit and save. Similarly, right-click on the root node, and select [Add Child Node] - [Field] in the pop-up menu. ] menu item to generate a "Field" child node. Select the "Field" node. In the form on the right, configure the field name to "retMsg", set the field description to "Response Message", set the field type to "string", set the JPATH path to "chanHeader.retMsg", set whether the input is required to "true", and click the [Submit] button on the form to submit and save. Similarly, right-click on the root node and select [Add Child Node] - [Field] menu item in the pop-up menu to generate a "Field" child node. Select the "Field" node. In the form on the right, configure the field name to "currentBalance", set the field description to "Available Balance", set the field type to "string", set the JPATH path to "retData.currentBalance", set whether the input is required to "true", and click the [Submit] button on the form to submit and save. This completes the configuration of the balance query transaction channel access package message "1011010001_encode.msg".

[0115] S18: Create a relationship mapping between channels, messages, and business processes. Select the "Relationship" subnode under the "101 [Self-Service Channel]" directory tree node on the interface, right-click, and select the "New Relationship" menu item in the pop-up menu. In the pop-up relationship dialog box, set the transaction code to "1011010001" and select "100 [Self-Service] - 100001 [Balance Inquiry]" for the business process. Click "Save" in the dialog box to complete the relationship mapping between channels, messages, and business processes.

[0116] S19: Project deployment. Select the "A bank's self-service channel project" tree node on the interface, right-click, and select the [Deploy / Export] menu item in the pop-up menu. In the pop-up project deployment dialog box, check "Channel", "Business", and "Public". Click the [Deploy] button in the dialog box to package the resources generated in the above steps and publish them to the back-end operation platform of the channel business system for automatic deployment and effectiveness.

[0117] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0118] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0119] Although the embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and are not to be construed as limitations on the present invention. A person skilled in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

Claims

1. A low-code secondary development method for self-service channel backend microservices, characterized in that: This is based on the channel business system backend operation platform and the channel business system backend secondary development platform, and includes the following steps: Use the back-end secondary development platform of the channel business system to carry out project visual development, including: creating access channels and configuring corresponding adapters and messages, creating business processes, creating outgoing channels and configuring corresponding adapters and messages; Deploy the projects developed using the secondary development platform of the channel business system backend to the channel business system backend operation platform for operation. The operation process includes the channel access sub-service, channel business processing sub-service, and channel access sub-service. When each sub-service is started, the business processes, various channels, corresponding adapters, and messages created by the secondary development platform of the channel business system backend are loaded into the cache for invocation. The channel access sub-service creates a corresponding communication service end according to the access channel and the corresponding adapter and message, receives the request from the channel requester, parses the message, and forwards the parsed data to the channel business processing sub-service for processing; after the processing is completed, the processing result is assembled into a message and returned to the channel requester; The channel business processing sub-service obtains and executes the corresponding business process based on the request forwarded by the channel access sub-service. If there is an outgoing request in the business, the channel outgoing sub-service is called to make an external system call; after the processing is completed, the processing result is returned to the channel access sub-service; The channel access sub-service receives the request sent by the channel business processing sub-service, assembles the message, creates a communication client based on the access channel and the corresponding adapter, and sends the assembled message to the target external system for processing; after the processing is completed, the processing result is parsed and returned to the channel business processing sub-service.

2. The low-code secondary development method for self-service channel backend microservices according to claim 1 is characterized in that: The process of channel accessing sub-service specifically includes: Create a corresponding communication server based on the access channel, corresponding adapter, and message, and receive requests from the channel requester; Obtain the depacketization message configuration corresponding to the channel requester's request through the transaction code, and use the message depacketization component to parse the message; According to the access channel, message, and business process relationship created by the secondary development platform of the channel business system backend, the parsed message is stored in the data structure of the unified data bus and forwarded to the channel business processing sub-service for processing; After the processing is completed, the corresponding package message configuration requested by the channel requester is obtained through the transaction code, the message package component is used to assemble the processing result, and the assembled message is returned to the channel requester.

3. The low-code secondary development method for self-service channel backend microservices according to claim 1 is characterized in that: The process of the channel business processing sub-service specifically includes: Based on the request forwarded by the channel access sub-service, the business process code is obtained from the data structure of the unified data bus, and the corresponding business process is found and executed; If there is an outbound request in the business, the channel outbound sub-service is called to make an external system call and forward it to the external system for processing; After the processing is completed, the processing results will be stored in the data structure of the unified data bus and returned to the channel access sub-service.

4. The low-code secondary development method for self-service channel backend microservices according to claim 1 is characterized in that: The specific process of the channel accessing the sub-service includes: Receive requests from the channel business processing sub-service; By obtaining the transaction code from the data structure of the unified data bus, finding the corresponding packet assembly message configuration for the request, and assembling the message using the message assembly component; Create a communication client based on the transaction component parameters, where the transaction component parameters include the access channel number, the corresponding adapter number, and the transaction code; Send the assembled message to the target external system for processing; After the processing is completed, the unpacking message configuration corresponding to the request is obtained through the transaction code, and the message unpacking component is used to parse the processing result; The parsed data is stored in the data structure of the unified data bus and returned to the channel business processing sub-service.

5. The low-code secondary development method for self-service channel backend microservices according to any one of claims 1 to 4, characterized in that: Utilize the channel business system back-end secondary development platform to carry out project visualization development. The process includes: Create a project and configure it; Conduct channel management based on projects, including creating access channels and outgoing channels; Create corresponding adapters based on the inbound and outbound channels and configure the adapters; Create corresponding messages based on the incoming and outgoing channels and configure them; Create business systems based on projects and create new business processes; Design business processes based on visual development methods; Maintain the relationship between access channels, outgoing channels, messages, and business processes, and associate them through transaction codes.

6. The low-code secondary development method for self-service channel backend microservices according to claim 5 is characterized in that: After completing the business process design, it also includes process verification, sending the designed business process to the channel business system back-end operation platform for verification to verify whether the business process is designed correctly.

7. The low-code secondary development method for self-service channel backend microservices according to claim 5 is characterized in that: The creating of corresponding messages based on the access channel and the access channel and performing message configuration includes: Create a new access channel depacketization message based on the access channel and configure the access channel depacketization message; Create a new access channel grouping message based on the access channel and configure the access channel grouping message; Create a new outgoing channel packet grouping message based on the outgoing channel and configure the outgoing channel packet grouping message; Create an outgoing channel depacketization message based on the outgoing channel and configure the outgoing channel depacketization message.

8. A low-code secondary development system for self-service channel backend microservices, characterized in that: Used to implement the low-code secondary development method for self-service channel backend microservices as described in any one of claims 1 to 7, the system includes a channel business system backend operation platform and a channel business system backend secondary development platform; The channel business system backend secondary development platform is used for project visualization development; The channel business system backend operation platform is used to run the projects developed by the channel business system backend secondary development platform, and provides channel access sub-services, channel business processing sub-services, and channel access sub-services.

9. The low-code secondary development system for self-service channel backend microservices according to claim 8 is characterized in that: The channel business system backend secondary development platform includes backend services and client tools; the client tools are used to provide a visual editing interface for project visual development; the backend services provide interface services for the client tools and process operation requests submitted by the client tools.

10. The low-code secondary development system for self-service channel backend microservices according to claim 9 is characterized in that: The back-end operating platform and back-end services of the channel business system adopt the Spring Cloud microservice architecture, and the client tool adopts the VUE + Element UI + HTML5 + MXGRAPH architecture.

Images