WO2021093672A1

WO2021093672A1 - Method for embedding external system, workflow system, device and computer readable storage medium

Info

Publication number: WO2021093672A1
Application number: PCT/CN2020/126823
Authority: WO
Inventors: 刘有; 尹强; 王和平; 黄山; 杨峙岳; 冯朝阁; 邸帅; 卢道和
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-11-13
Filing date: 2020-11-05
Publication date: 2021-05-20
Also published as: CN110874278A

Abstract

A method for embedding an external system, a workflow system, a device and a computer readable storage medium, relating to the field of financial science and technology. The method comprises the steps of: upon detecting a loading instruction for loading an external system in a front-end subsystem of a workflow system, determining the node type of a workflow node corresponding to the loading instruction by means of a preset node type table (S10); obtaining node parameters of the workflow node in a preset parameter configuration table according to the node type (S20); and generating a front-end control of the workflow node in the front-end subsystem according to the node parameters to embed the external system into the workflow system as the workflow node (S30).

Description

Embedding method, workflow system, equipment and computer readable storage medium of external system

This application claims the priority of the Chinese patent application filed on November 13, 2019, with the application number 201911110030.7, and the name "External system embedding method, workflow system, equipment and storage medium", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of big data technology of financial technology (Fintech), and in particular to an external system embedding method, workflow system, equipment, and computer-readable storage medium.

Background technique

With the development of computer technology, more and more technologies are applied in the financial field. The traditional financial industry is gradually transforming to Fintech. Big data technology is no exception. However, due to the security and real-time requirements of the financial industry, It also places higher demands on technology.

In the field of big data, complex business data processing scenarios, especially in offline batch calculation and report processing, are inseparable from solving the intricate dependencies in the data processing process. Therefore, the execution of jobs requires unified management and scheduling. Currently, distributed visualization DAG (Database Availability Group, database availability group) workflow task scheduling system. At present, the more popular scheduling systems include Azkaban and Airflow. Azkaban is a batch workflow task scheduler open sourced by Linkedin; Airflow is a programmable, scheduling and monitoring workflow platform, based on a directed acyclic graph (DAG), Airflow can define a set of dependent tasks and execute them in turn according to the dependencies. They all support DAG diagrams to associate workflows according to the dependencies of tasks for distributed scheduling execution, but the current scheduling system focuses on solving problems such as dependent execution, concurrent execution, and timing execution. Because the current business processing process involves multiple aspects of data processing, including data import, data desensitization, data quality inspection, data ETL (Extract-Transform-Load, extraction, transformation, and loading), and data visualization And the outflow of data and other links, each link will have a special system to be responsible for processing. Therefore, currently a new type of workflow node is added to the workflow system, and both the front-end subsystem and the back-end subsystem of the workflow system require a lot of development.

It can be seen that it is currently difficult to add workflow nodes corresponding to external systems in the workflow system.

Technical solutions

The main purpose of this application is to provide an external system embedding method, workflow system, equipment, and computer-readable storage medium, aiming to solve the existing difficulty of adding workflow nodes corresponding to the external system in the workflow system. technical problem.

In order to achieve the above objective, the present application provides an embedding method of an external system. The embedding method of the external system includes the steps:

When it is detected that the load instruction of the external system is loaded in the front-end subsystem of the workflow system, the node type of the workflow node corresponding to the load instruction is determined through the preset node type table;

Acquiring the node parameters of the workflow node in a preset parameter configuration table according to the node type;

The front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node in the workflow system.

In an embodiment, after the step of generating the front-end control of the workflow node in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node in the workflow system ,Also includes:

After detecting the start instruction to start the external system subpage in the workflow node, obtain the uniform resource locating system URL address of the subpage, and obtain the start parameter corresponding to the start instruction;

Generate a transmission request according to the URL address and the startup parameters, and set the transmission request to a text label, so as to realize the communication between the child page and the parent page of the workflow system through the text label .

In an embodiment, the transmission request is generated according to the URL address and the startup parameters, and the transmission request is set in a text tag, so as to realize the sub-page and the workflow through the text tag After the steps of communication between the parent pages of the system, it also includes:

After detecting a message transmission instruction for using the text tag to send a message across domains between the parent page and the child page, obtain the message to be transmitted corresponding to the message transmission instruction through the parent page;

The message to be transmitted is assembled into a transmission message in a preset format and sent to the sub-page.

After detecting the design command for chart design in the sub-page, obtain the setting parameters corresponding to the design command;

According to the setting parameter setting chart, the setting parameters are stored as a Kanban task, so that the setting parameters are displayed in the parent page through the Kanban task.

After detecting the access request for accessing the external system, obtain the security authentication information of the external system from the back-end subsystem of the workflow system;

The security authentication information is added to the access request, and the access request carrying the security authentication information is sent to the external system, so that the external system can determine the location based on the security authentication information in the access request. State the legitimacy of the access request.

Acquiring a standard interface for docking with the external system in the back-end subsystem of the workflow system, and acquiring interface information of the external system through the front-end subsystem;

Through the front-end subsystem, a workflow task is created in the external system according to the standard interface and the interface information.

After detecting that the execution instruction of the workflow node corresponding to the external system is executed, determine the scheduling system corresponding to the execution instruction;

The tasks of the workflow node are converted according to the scheduling format of the scheduling system to obtain the converted tasks to be executed, and the converted tasks to be executed are sent to the Linkis client through the scheduling system to pass the Linkis The client executes the task to be executed after the conversion.

In one embodiment, after detecting that the load instruction of the external system is loaded in the front-end subsystem of the workflow system, the node type of the workflow node corresponding to the load instruction is determined through a preset node type table. Before the steps, it also includes:

After detecting the embedding instruction of the workflow node corresponding to the external system in the workflow system, the node type of the workflow node is added to the node type table, and the job is added to the parameter configuration table The node parameters of the flow node.

In addition, in order to achieve the above objective, the present application also provides a workflow system, the workflow system including:

The determining module is used to determine the node type of the workflow node corresponding to the load instruction through the preset node type table after detecting that the load instruction of the external system is loaded in the front-end subsystem of the workflow system;

An obtaining module, configured to obtain the node parameters of the workflow node in a preset parameter configuration table according to the node type;

The generating module is configured to generate the front-end control of the workflow node in the front-end subsystem according to the node parameters, so as to embed the external system as a workflow node in the workflow system.

In addition, in order to achieve the above objective, the present application also provides an embedded device of an external system. The embedded device of the external system includes a memory, a processor, and an external system stored on the memory and capable of running on the processor. The embedded program of the external system, when the embedded program of the external system is executed by the processor, realizes the steps of the above-mentioned embedding method of the external system.

In addition, in order to achieve the above-mentioned object, the present application also provides a computer-readable storage medium with an embedded program of an external system stored on the computer-readable storage medium. When the embedded program of the external system is executed by a processor, the above The steps of the embedding method of the external system described.

This application determines the node type of the workflow node corresponding to the load instruction through the preset node type table after detecting the loading instruction of the external system in the front-end subsystem of the workflow system. Obtain the node parameters of the workflow node in the parameter configuration table; generate the front-end control of the workflow node in the front-end subsystem according to the node parameters, so as to embed the external system as the workflow node in the workflow system, and realize the work In the process of adding workflow nodes corresponding to external systems in the flow system, there is no need to perform a lot of front-end subsystems and back-end subsystems of the workflow system. You only need to obtain the node parameters of the workflow nodes corresponding to the external system, which reduces the work flow. The difficulty of adding a new external system corresponding to the workflow node in the workflow system, and improving the efficiency of adding a new external system corresponding to the workflow node in the workflow system.

Description of the drawings

Fig. 1 is a schematic flowchart of a first embodiment of an embedding method of an external system of the present application;

2 is a schematic flowchart of a second embodiment of the method for embedding an external system of the present application;

3 is a schematic flowchart of a third embodiment of the method for embedding an external system of the present application;

FIG. 4 is a functional schematic block diagram of a preferred embodiment of the workflow system of the present application;

Fig. 5 is a schematic structural diagram of a hardware operating environment involved in a solution of an embodiment of the present application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the application, and not used to limit the application.

This application provides an embedding method for an external system. Refer to FIG. 1, which is a schematic flowchart of a first embodiment of the embedding method for an external system of this application.

The embodiments of the present application provide an embodiment of an embedding method of an external system. It should be noted that although the logical sequence is shown in the flowchart, in some cases, the sequence shown here can be executed in a different order. Or the steps described.

Embedding methods for external systems include:

Step S10, after detecting that the loading instruction of the external system is loaded in the front-end subsystem of the workflow system, the node type of the workflow node corresponding to the loading instruction is determined through a preset node type table.

In the embodiment of this application, the workflow system uses Linkis's powerful background computing engine aggregation capabilities, as well as Linkis's task management, resource management and isolation, task scheduling and execution features, result sets and log processing capabilities, which are very convenient for external The system is integrated into the real-time execution and scheduling execution of a workflow. Linkis is a data middleware that integrates multiple computing storage engines, provides a unified interface to the outside world, and submits and executes SQL (Structured Query Language), Pyspark, HiveQL, Scala and other scripts. The workflow system includes a front-end subsystem and a back-end subsystem. The front-end subsystem is used to create workflow nodes corresponding to the external system and the interaction between the pages of the workflow system and the external system. In order to facilitate the distinction, the workflow system page is recorded as the parent page, and the external system page is recorded as the child page. In the back-end subsystem, a node type table and a node parameter attribute table are set. The node type table is used to store the node type of each workflow node, and the node parameter attribute table is used to store the node parameters of different types of workflow nodes. Node types include data exchange nodes, data development nodes, data visualization nodes, data output nodes, signal nodes, and function nodes. Node parameters include but are not limited to node startup parameters, the memory size of the node corresponding to the external system, and the CPU (central CPU) of the node corresponding to the external system. The number of processing units (central processing units), node parameter names, parameter types, parameter value ranges, parameter verification rules, and whether the corresponding fields of the parameters are required, etc. The parameter types include but are not limited to character and numeric types. The node parameters corresponding to different types of workflow nodes may be the same or different.

After the current terminal system detects the load instruction for loading the external system, the front-end subsystem determines the node type of the workflow node corresponding to the load instruction in the node type table preset in the back-end subsystem. Among them, the workflow node corresponding to the load instruction is the workflow node corresponding to the external system. When the external system is successfully embedded in the workflow system, the external system exists as a workflow node in the workflow system. The load instruction can be triggered by the user as needed, or can be triggered actively by the workflow system. It should be noted that the load instruction carries the identification information of the external system. The identification information can be used to determine the node type of the workflow node corresponding to the load instruction in the node type table. The identification information can be the name of the external system or uniquely indicate the external system. The identification code of the system. Specifically, the load instruction may be a page refresh instruction.

Further, the embedding method of the external system includes:

Step a: After detecting the embedding instruction of the workflow node corresponding to the external system in the workflow system, add the node type of the workflow node to the node type table, and add it to the parameter configuration table The node parameter of the workflow node.

Further, when the front-end subsystem of the workflow system detects the embedded instruction of the external system as the workflow node, the front-end subsystem sends the embedded instruction to the back-end subsystem, and the back-end subsystem obtains the corresponding work of the external system according to the embedded instruction The node type and node parameters of the flow node, and the node type of the workflow node corresponding to the external system is added to the node type table, and the node parameter of the workflow node corresponding to the external system is added to the parameter configuration table. It should be noted that the node type of the workflow node corresponding to the external system is determined by the function that the external system can implement. The external system should be embedded in the workflow system as a workflow node. The external system should first be registered in the workflow system. During the registration process of the external system in the workflow system, the workflow system can obtain the relevant data of the external system. According to the relevant data Determine the node type of the workflow node corresponding to the external system. Relevant data includes, but is not limited to, the system name of the external system, safety certification information and the functions that can be realized. The security authentication information includes at least one of Cookie content and Token content. The type of cookie is a "small text file", which is the data (usually encrypted) stored on the user's local terminal by certain websites in order to identify the user and perform session tracking. The information is temporarily or permanently stored by the user's client computer.

Step S20: Obtain the node parameters of the workflow node from a preset parameter configuration table according to the node type.

After determining the node type of the workflow node corresponding to the external system, the front-end subsystem obtains the node parameters of the workflow node corresponding to the external system from the parameter configuration table in the back-end subsystem according to the node type. Specifically, after the front-end subsystem detects the load instruction, it sends the load instruction to the back-end subsystem. The back-end subsystem determines the node type of the workflow node corresponding to the external system in the node type table according to the load instruction, and then pre- The node parameter corresponding to the node type is obtained from the set parameter configuration table to obtain the node parameter of the workflow node corresponding to the external system, and then the node parameter is returned to the front-end subsystem.

Step S30: Generate a front-end control of the workflow node in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node in the workflow system.

After the current terminal system obtains the node parameters, the front-end subsystem generates a front-end control corresponding to the workflow node of the external system according to the node parameters, so as to embed the external system as a workflow node into the workflow system. It should be noted that when the front-end control corresponding to the workflow node of the external system is generated, it means that the external system has become a workflow node in the workflow system. Further, the front-end subsystem can generate a node selectable list according to the node parameters in the parameter configuration table. The user can select the corresponding node parameter in the node selectable list. The front-end subsystem dynamically loads according to the node parameters selected by the user, and the external system It is embedded in the workflow system as a workflow node.

It should be noted that, in this embodiment, the workflow system essentially changes the front-end subsystem through SQL configuration, and embeds the external system as a workflow node into the workflow system. Specifically, the workflow system sets the method of adding workflow nodes through SQL as a template. When an external system needs to be embedded in the workflow system as a workflow node, the front-end subsystem adds the obtained node parameters to the corresponding template At the location, the external system can be embedded in the workflow system as a workflow node. It can be seen that this embodiment hides the complex logic implemented by SQL, and even users who do not use SQL can easily embed the external system as a workflow node into the workflow system.

In this embodiment, after detecting that the load instruction of the external system is loaded in the front-end subsystem of the workflow system, the node type of the workflow node corresponding to the load instruction is determined through the preset node type table, and the node type of the workflow node corresponding to the load instruction is determined according to the node type. Obtain the node parameters of the workflow node in the parameter configuration table; generate the front-end control of the workflow node in the front-end subsystem according to the node parameters, so as to embed the external system as the workflow node in the workflow system, and realize the In the process of adding workflow nodes corresponding to external systems in the workflow system, there is no need to perform a lot of front-end subsystems and back-end subsystems of the workflow system. You only need to obtain the node parameters of the workflow nodes corresponding to the external system, which reduces the cost The difficulty of adding a new external system corresponding to the workflow node in the workflow system, and improving the efficiency of adding a new external system corresponding to the workflow node in the workflow system.

Further, a second embodiment of the embedding method of the external system of the present application is proposed.

The difference between the second embodiment of the external system embedding method and the first embodiment of the external system embedding method is that, referring to FIG. 2, the external system embedding method further includes:

Step S40, after detecting the start instruction for starting the external system subpage in the workflow node, obtain the uniform resource locating system URL address of the subpage, and obtain the start parameter corresponding to the start instruction.

When the workflow system detects the start instruction to start the subpage of the external system in the corresponding workflow node of the external system, the workflow system obtains the URL of the subpage (Uniform Resource Locator (Uniform Resource Locator) address, and the startup parameters corresponding to the startup instruction. Startup parameters include, but are not limited to, the display mode of the subpage, page size, page layout parameters, and business parameters displayed on the subpage. Business parameters include, but are not limited to, the project number corresponding to the content displayed on the subpage, and the user information of the user corresponding to the subpage. , The node name of the workflow node and the task ID corresponding to the workflow node, the user information can be a user name or user ID number, etc., and the project number is the project code or project ID of the project corresponding to the content displayed on the subpage. It is understandable that the start instruction can be triggered by the user according to specific needs, or triggered by a timing task in the workflow system.

Step S50: Generate a transmission request according to the URL address and the startup parameters, and set the transmission request to a text tag, so as to realize the relationship between the child page and the parent page of the workflow system through the text tag. Inter-communication.

After the workflow system obtains the URL address and the startup parameters, the workflow system splices the URL address startup parameters into a transmission request according to a preset splicing format, that is, generates a transmission request based on the URL address and the startup parameters. In this embodiment, the specific manifestation of the splicing format is not limited. For example, the URL address can be placed in the front, and the startup parameters can be placed in the back for splicing. Specifically, in this embodiment, the transfer request may be HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol) request. It is understandable that, in other embodiments, the URL address and the startup parameters can also be spliced into requests corresponding to other transmission protocols.

After the workflow system generates the transmission request, it sets the transmission request to the text label, so as to realize the communication between the child page and the parent page of the workflow system through the text label. Among them, the text tag is an IFrame tag, and IFrame is an HTML (HyperText Markup Language) tag, which functions as a document in a document or a floating frame (IFrame). The IFrame element will create an inline frame containing another document (That is, the frame of the line). It should be noted that the child page of the external system can be used as a workflow node of the workflow system through the IFrame tag to realize the communication between the parent page and the child page of the workflow system. In the communication process between the parent page and the child page, IFrame tags are used to send messages across domains. Cross domain refers to when any of the protocol, domain name, and port of a request URL is different from the current page URL. This embodiment mainly uses The window.postMessage method solves the problem of sending messages across domains.

Further, the embedding method of the external system further includes:

Step b: After detecting a message transmission instruction using the text tag to send a message across domains between the parent page and the child page, obtain the message transmission instruction to be transmitted corresponding to the message transmission instruction through the parent page news.

Further, when the parent page of the workflow system and the child page of the external system communicate via IFrame, the workflow system detects whether it detects that the text tag is used between the parent page and the child page to send a message across domains Message transmission instructions. After the workflow system detects the message transmission instruction, the workflow system obtains the message to be transmitted corresponding to the message transmission instruction through the parent page. It should be noted that the message to be transmitted includes the project number, user information, the node name of the workflow node corresponding to the subpage, and the task identifier of the task corresponding to the message to be transmitted.

Step c: Assemble the message to be transmitted into a transmission message in a preset format and send it to the sub-page.

After the workflow system obtains the message to be transmitted, the workflow system assembles the message to be transmitted into a transmission message in a preset format and sends it to the sub-page. Specifically, the workflow system assembles the messages to be transmitted into JSON (JavaScript Object Notation, JavaScript object notation) format to send to the child page. It should be noted that the parent page detects the message transmission instruction through the message monitoring method, and uses the JSON format to transmit the message content of the message transmission instruction, that is, the message to be transmitted is transmitted in the JSON format. The message structure of the message to be transmitted is determined by the workflow system and the external The system has agreed in advance. In this embodiment, the JSON format is used to transmit the message, which is the advantage of simple application and good compatibility of JSON. JSON is compatible with lower versions of IE (Internet Explorer, web browser). When the workflow system receives an acquisition request from the child page to obtain the message to be transmitted in JSON format from the child page through the parent page, the workflow system obtains the corresponding message to be transmitted according to the acquisition request, converts the message to be transmitted into JSON format, and places it To the fixed parameter position in the preset callback function, the message to be transmitted in JSON format is sent to the subpage, that is, the message to be transmitted in JSON format is sent to the external system to realize the communication between the external system and the workflow system.

Further, the message sending function is also added to the subpage of the external system. Specifically, the click event of the save button is set in the subpage of the external system, and the message sending function is added to the click event method. By using The window.parent.postMessage method sends a message to the parent page of the workflow system. When the external system stores data through the save button of the subpage, the subpage will send the key information of the stored data to the workflow system, specifically, to the front-end subsystem of the workflow system. The key information includes but is not limited to the external system The stored data corresponds to the task ID, node name and project number of the task. It should be noted that the external system only sends key information to the front-end subsystem of the workflow system through the sub-page, and other related information can be obtained when the corresponding task is executed, which reduces the amount of data transmission between the external system and the workflow system , Simplifies the content of the data transmitted by the external system and the workflow system. The complex task definition is completed in the external system, and the workflow system is not required to perform complex task definition operations.

This embodiment solves the problem of data interaction between the child page of the external system and the parent page of the workflow system after the external system is embedded in the workflow system as a workflow node. In addition to directly embedding the child page of the external system in the workflow system, work The flow system can also send messages to the external system, and the external system can also send the message to the workflow system. By using the external system as the workflow node in the workflow system, the data processing and analysis in the external system can be made clearer. Enables the corresponding developers to complete the development of the entire business process in the visual workflow system, avoids developers from repeatedly logging in to different external systems to design the business logic of the business process, reduces the difficulty for developers to develop business processes, and improves developers Design efficiency of design business logic.

Further, the embedding method of the external system further includes:

Step d, after detecting the design command for chart design in the subpage, obtain the setting parameters corresponding to the design command.

When the workflow system detects the design instruction for chart design in the subpage, the workflow system obtains the setting parameters corresponding to the design instruction through the subpage. The setting parameters include the data source of the chart data, the chart name, and the performance of the chart. Style, color configuration and chart size, etc., performance styles include, but are not limited to, histogram, table, and radar chart. The chart corresponding to the design command in this embodiment is a visual chart. Specifically, the user can trigger the design instruction in the subpage of the external system embedded in the workflow system.

Step e: According to the setting parameter setting chart, and storing the setting parameters as a Kanban task, so as to display the setting parameters in the parent page through the Kanban task.

After the workflow system obtains the setting parameters corresponding to the design instruction, the workflow system sets the chart in the child page according to the setting parameters, stores the setting parameters as a dashboard task, and sends the dashboard task to the parent page to pass The kanban task displays the setting parameters in the parent page. It should be noted that the related information of the set chart can be displayed on the parent page through the Kanban task, specifically, it can be displayed on the parent page in the form of a list. It is understandable that the child page is also cross-domain through Iframe, and the Kanban task is sent to the parent page in the form of a string, where the string is a type of JSON format. It should be noted that in this embodiment, the user only needs to perform corresponding operations on the external system, and the external system saves the user's operation information, and then sends the core information in the operation information to the parent page of the workflow system, and executes the corresponding operation. During the task, the workflow system returns the core information to the external system for the external system to execute the corresponding task according to the core information, where the core information is information that can determine which task the task is.

This embodiment implements the Iframe method in the workflow system, using an external system to create the visualization chart. In the process of creating the visualization chart in the workflow system, since the external system is embedded in the workflow system as a workflow node, no user login is required. The external system for chart creation can be done directly in the workflow system, which simplifies the difficulty of chart creation and improves the efficiency of chart creation.

Further, a third embodiment of the embedding method of the external system of the present application is proposed.

The difference between the third embodiment of the external system embedding method and the first and/or the second embodiment of the external system embedding method is that, referring to FIG. 3, the external system embedding method further includes:

Step S60, after detecting the access request for accessing the external system, obtain the security authentication information of the external system from the back-end subsystem of the workflow system.

Step S70: Add the security authentication information to the access request, and send the access request carrying the security authentication information to the external system, so that the external system can authenticate according to the security authentication in the access request. The information determines the legitimacy of the access request.

When the workflow system detects the access request to the external system, the workflow system obtains the security authentication information of the external system from its back-end subsystem, and adds the security authentication information to the access request. The access request can be triggered by the user in the workflow system or the external system as needed, and the security authentication information is pre-stored in the back-end subsystem. It should be noted that the access request carries the system name of the external system, and the security authentication information of the external system can be obtained in the back-end subsystem according to the system name.

After the security authentication information is added to the access request, the workflow system sends the access request carrying the security authentication information to the external system. When the external system receives the access request, the external system obtains the security authentication information in the access request, and compares the obtained security authentication information with the pre-stored security authentication information. If the obtained security authentication information is compared with the stored security authentication information If the information is consistent, the external system determines that the access request is legal and executes the access request; if the obtained security authentication information is inconsistent with the stored security authentication information, the external system determines that the access request is illegal and does not execute the access request. It should be noted that the communication between the external system and the workflow system is the communication between the child page of the external system and the parent page of the workflow system.

In this embodiment, during the communication process between the external system and the workflow system, the external system uses security authentication information to ensure the legitimacy of the access request sent by the workflow system, thereby ensuring the security of the external system's execution of the workflow system access request process.

Further, the embedding method of the external system further includes:

Step f: Obtain a standard interface for docking with the external system in the back-end subsystem of the workflow system, and obtain the interface information of the external system through the front-end subsystem.

The workflow system obtains the standard interface to the external system in the back-end subsystem, and obtains the interface information of the external system through the front-end subsystem. It should be noted that the external system needs to perform tasks such as quality inspection tasks, data export tasks, and data analysis, and each task needs to be defined in the corresponding external system. Therefore, the external system generally has a login interface, a creation interface for creating tasks, an update interface for updating tasks, and a deletion interface for deleting tasks. In the process of task execution, the external system also needs to obtain the execution status of the task. Workflow system The execution results and logs of the tasks will be sent to the external system. The realization of these functions also requires corresponding interfaces. It can be seen that, in the external system, each interface has its own function to be implemented and the corresponding return data type. In this embodiment, in order to simplify the complexity of the front-end subsystem calling the external system, the back-end subsystem performs standardized operations on various interfaces corresponding to the external system, and uniformly defines the standard interfaces for connecting with the external system, such as the unified definition of the back-end subsystem Login interface, create interface to create task, update interface to update task, delete interface to delete task, etc. The interface information includes, but is not limited to, the URL address of the external system, the node name of the workflow node corresponding to the interface, and interface parameters. The interface parameters can be used to determine which interface the current interface is.

Step g, through the front-end subsystem, create a workflow task in the external system according to the standard interface and the interface information.

After obtaining the standard interface and interface information for docking with the external system, the workflow system obtains the interface code corresponding to the standard interface in the back-end subsystem, and then writes the interface information into the corresponding position of the interface code to obtain the callable interface. At this time, The front-end subsystem can create workflow tasks in the external system through the callable interface. It should be noted that in the back-end subsystem of the workflow system, each standard interface has a corresponding interface code. The interface code is preset. When you want to use it, you only need to write the corresponding interface code in the set interface code. Interface information.

In this embodiment, by defining the standard interface for docking with external systems in the back-end subsystem of the workflow system, the front-end subsystem of the workflow system does not need to make special work flow nodes corresponding to each external system when docking with the external system. Call processing, to interface with the external system through the interface code of the standard interface in the back-end subsystem. Since the data capacity of the front-end subsystem is weaker than that of the back-end subsystem, the design of the standard interface in the back-end subsystem is less difficult than through the front-end subsystem. Calling the workflow node corresponding to the external system reduces the difficulty of the front-end subsystem of the workflow system calling the external system, and adds an interface framework for docking with the external system in the back-end subsystem to avoid the front-end subsystem directly corresponding to various external systems In order to realize the call to the external system without modifying the code of the front-end subsystem.

Further, a fourth embodiment of the embedding method of the external system of the present application is proposed.

The difference between the fourth embodiment of the external system embedding method and the first, second, and/or third embodiments of the external system embedding method is that the external system embedding method further includes:

Step h: After detecting that the execution instruction of the workflow node corresponding to the external system is executed, determine the scheduling system corresponding to the execution instruction.

After successfully embedding the external system as a workflow node into the workflow system, the workflow system detects whether the execution instruction of the corresponding workflow node of the external system is detected. If the execution instruction is detected, the workflow system determines the scheduling system corresponding to the execution instruction. Among them, the execution instruction may be a real-time execution instruction or a scheduled execution instruction. When the execution instruction is a scheduling execution instruction, the task of the workflow node corresponding to the external system needs to be released to the corresponding scheduling system for regular execution. It should be noted that the execution instruction carries a scheduling identifier corresponding to the scheduling system, and the scheduling system corresponding to the execution instruction can be determined according to the scheduling identifier.

Step i: Convert the tasks of the workflow node according to the scheduling format of the scheduling system to obtain the converted tasks to be executed, and send the converted tasks to be executed to the Linkis client through the scheduling system to pass The Linkis client executes the task to be executed after the conversion.

After the workflow system determines the scheduling system corresponding to the execution instruction, the workflow system converts the tasks of the workflow node according to the scheduling format of the scheduling system to obtain the converted tasks to be executed. It should be noted that each scheduling system has its own input format. Therefore, to send the tasks of the workflow node corresponding to the external system to the scheduling system, the format of the task needs to be converted. The specific conversion is determined by the scheduling system. Details are not described in the embodiment. When the converted task to be executed is obtained, the workflow system sends the converted task to be executed to the scheduling system for the scheduling system to send the converted task to be executed to the Linkis client, and execute the converted task through the Linkis terminal. Task to be performed. Specifically, regardless of whether the execution instruction is a real-time execution instruction or a scheduled execution instruction, the Linkis client uses the system identifier in the task to be executed to determine whether the node corresponding to the task to be executed is the workflow node of the external system or the original node of the workflow system. The original node of the system is the original node of the workflow system. If the Linkis client determines that the node corresponding to the task to be executed is the original node of the workflow system, the Linkis client submits the task to be executed to its execution engine to execute the task to be executed through the engine; if the Linkis client determines to be executed The node corresponding to the task is the workflow node of the external system, and the Linkis client determines the node type of the workflow node corresponding to the task to be executed, and then sends the task to be executed to the external system corresponding to the determined node type, and the external system executes the task to be executed. task. When the external system finishes executing the task to be executed, it will generate the execution result and return the execution result.

If the scheduling system is the Azkaban system, the workflow system needs to convert the tasks corresponding to the workflow nodes of the external system into job files, then compress the job files into a compressed package, and send the compressed package to the Azkaban system, and the Azkaban system will get the result The compressed package is parsed into an execution task flow, according to the Directed Acyclic Graph (Directed Acyclic Graph, DAG) scheduling, using the Azkaban plugin that wraps the Linkis client, submitted to the External Entrance (external interface) of the backend of the Linkis client, and it will execute The task flow is uniformly sent to the external system, and the external system is responsible for the corresponding task analysis and execution of the execution task flow. The format of the compressed package can be zip or RAR (Roshal ARchive), etc. Specifically, the Linkis client can identify the system name of the external system that performs the corresponding task through the compressed package, and the corresponding external system can be determined based on the system name. The Linkis client can use Job Type identifies the system name, and a workflow node corresponds to a Node type.

It should be noted that, in this embodiment, the Linkis client implements the execution of external system workflow node tasks, and can use the system-level and user-level multi-tenant isolation, concurrent current limiting, and context sharing capabilities of the Linkis client. When an external system needs to access Linkis to perform tasks, it only needs to implement the interface content of External Entrance in the background of the Linkis client to realize the access of the external system. The External Entrance of the Linkis client provides the Context class, which allows the external system corresponding to the workflow node to share variables and parameters for use by the workflow nodes of other external systems during the execution of the tasks corresponding to the workflow node.

This embodiment uses Linkis' system-level and user-level multi-tenant isolation, concurrent current limiting, and context sharing capabilities, so that the interaction between the workflow system and the external system has a unified execution entry, and the interaction between the workflow system and the external system is reduced. The difficulty.

In addition, referring to FIG. 4, the present application also provides a workflow system, which includes:

The determining module 10 is configured to determine the node type of the workflow node corresponding to the load instruction through a preset node type table after detecting that the load instruction of the external system is loaded in the front-end subsystem of the workflow system;

The obtaining module 20 is configured to obtain the node parameters of the workflow node in a preset parameter configuration table according to the node type;

The generating module 30 is configured to generate front-end controls of the workflow node in the front-end subsystem according to the node parameters, so as to embed the external system as a workflow node in the workflow system.

Further, the obtaining module 20 is also configured to obtain the uniform resource locating system URL address of the sub-page after detecting the start instruction for starting the external system sub-page in the workflow node, and obtain all the sub-pages. The startup parameters corresponding to the startup command;

The generating module 30 is further configured to generate a transmission request according to the URL address and the startup parameters;

The workflow system also includes:

The setting module is configured to set the transmission request to a text label, so as to realize the communication between the child page and the parent page of the workflow system through the text label.

Further, the acquiring module 20 is further configured to acquire all information through the parent page after detecting a message transmission instruction for using the text tag to send a message across domains between the parent page and the child page. The message to be transmitted corresponding to the message transmission instruction;

The workflow system also includes:

The first sending module is configured to assemble the to-be-transmitted message into a transmission message in a preset format and send it to the sub-page.

Further, the obtaining module 20 is also configured to obtain the setting parameters corresponding to the design command after the design command for chart design in the subpage is detected;

The setting module is also used to set the chart according to the setting parameters;

The workflow system also includes:

The storage module is configured to store the setting parameters as a Kanban task, so as to display the setting parameters in the parent page through the Kanban task.

Further, the obtaining module 20 is further configured to obtain the security authentication information of the external system from the back-end subsystem of the workflow system after detecting an access request to the external system;

The workflow system also includes:

The first adding module is configured to add the security authentication information to the access request;

The second sending module is configured to send an access request carrying the security authentication information to the external system, so that the external system can determine the legitimacy of the access request according to the security authentication information in the access request.

Further, the acquisition module 20 is also configured to acquire a standard interface for connecting to the external system in the back-end subsystem of the workflow system, and acquire interface information of the external system through the front-end subsystem;

The workflow system also includes:

The creation module is configured to create a workflow task in the external system according to the standard interface and the interface information through the front-end subsystem.

Further, the workflow system further includes:

The determining module is used to determine the scheduling system corresponding to the execution instruction after detecting the execution instruction of the workflow node corresponding to the external system;

The conversion module is used to convert the tasks of the workflow node according to the scheduling format of the scheduling system to obtain the tasks to be executed after conversion;

The acquisition module 20 is further configured to send the converted task to be executed to the Linkis client through the scheduling system, so as to execute the converted task to be executed through the Linkis client.

Further, the workflow system further includes:

The second adding module is used to add the node type of the workflow node in the node type table after detecting the embedding instruction of the workflow node corresponding to the external system in the workflow system, and add the node type of the workflow node to the parameter The node parameter of the workflow node is added to the configuration table.

It should be noted that the various embodiments of the workflow system are basically the same as the above-mentioned embodiments of the embedding method of the external system, and will not be described in detail here.

In addition, this application also provides an embedded device of an external system. As shown in FIG. 5, FIG. 5 is a schematic structural diagram of the hardware operating environment involved in the solution of the embodiment of the present application.

It should be noted that FIG. 5 can be a structural schematic diagram of the hardware operating environment of the embedded device of the external system. The embedded device of the external system in the embodiment of the present application may be a terminal device such as a PC and a portable computer.

As shown in FIG. 5, the embedded device of the external system may include: a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, and a communication bus 1002. Among them, the communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a magnetic disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

Optionally, the embedded device of the external system may also include a camera, RF (Radio Frequency, radio frequency) circuits, sensors, audio circuits, WiFi modules, etc.

Those skilled in the art can understand that the structure of the embedded device of the external system shown in FIG. 5 does not constitute a limitation on the embedded device of the external system, and may include more or less components than those shown in the figure, or a combination of certain components, Or different component arrangements.

As shown in FIG. 5, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an embedded program of an external system. Among them, the operating system is a program that manages and controls the embedded device hardware and software resources of the external system, and supports the operation of the embedded program of the external system and other software or programs.

In the embedded device of the external system shown in FIG. 5, the user interface 1003 is mainly used to connect to the client and to communicate data with the client; the network interface 1004 is mainly used to communicate with the back-end server and perform data communication; the processor 1001 can It is used to call the embedding program of the external system stored in the memory 1005 and execute the steps of the embedding method of the external system as described above.

The specific implementation of the embedding device of the external system of the present application is basically the same as the above embodiments of the embedding method of the external system, and will not be repeated here.

In addition, an embodiment of the present application also proposes a computer-readable storage medium with an embedded program of an external system stored on the computer-readable storage medium. When the embedded program of the external system is executed by a processor, the external system as described above is realized. Steps of the system's embedding method.

The specific implementation of the computer-readable storage medium of the present application is basically the same as the above embodiments of the embedding method of the external system, and will not be repeated here.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, It also includes other elements not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to enable a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of the application, and do not limit the scope of the patent for this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of the application, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

An embedding method of an external system, wherein the embedding method of the external system includes the following steps:

When it is detected that the load instruction of the external system is loaded in the front-end subsystem of the workflow system, the node type of the workflow node corresponding to the load instruction is determined through the preset node type table;

Acquiring the node parameters of the workflow node in a preset parameter configuration table according to the node type;

The front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node in the workflow system.
The method for embedding an external system according to claim 1, wherein the front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node After the steps in the workflow system, it further includes:

After detecting the start instruction to start the external system subpage in the workflow node, obtain the uniform resource locating system URL address of the subpage, and obtain the start parameter corresponding to the start instruction;

Generate a transmission request according to the URL address and the startup parameters, and set the transmission request to a text label, so as to realize the communication between the child page and the parent page of the workflow system through the text label .
The method for embedding an external system according to claim 2, wherein said generating a transmission request according to said URL address and said startup parameters, and setting said transmission request in a text tag, so as to realize through said text tag After the step of communication between the child page and the parent page of the workflow system, it further includes:

After detecting a message transmission instruction for using the text tag to send a message across domains between the parent page and the child page, obtain the message to be transmitted corresponding to the message transmission instruction through the parent page;

The message to be transmitted is assembled into a transmission message in a preset format and sent to the sub-page.
The method for embedding an external system according to claim 2, wherein said generating a transmission request according to said URL address and said startup parameters, and setting said transmission request in a text tag, so as to realize through said text tag After the step of communication between the child page and the parent page of the workflow system, it further includes:

After detecting the design command for chart design in the sub-page, obtain the setting parameters corresponding to the design command;

According to the setting parameter setting chart, the setting parameters are stored as a Kanban task, so that the setting parameters are displayed in the parent page through the Kanban task.
The method for embedding an external system according to claim 1, wherein the front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node After the steps in the workflow system, it further includes:

After detecting the access request for accessing the external system, obtain the security authentication information of the external system from the back-end subsystem of the workflow system;

The security authentication information is added to the access request, and the access request carrying the security authentication information is sent to the external system, so that the external system can determine the location based on the security authentication information in the access request. State the legitimacy of the access request.
The method for embedding an external system according to claim 1, wherein the front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node After the steps in the workflow system, it further includes:

Acquiring a standard interface for docking with the external system in the back-end subsystem of the workflow system, and acquiring interface information of the external system through the front-end subsystem;

Through the front-end subsystem, a workflow task is created in the external system according to the standard interface and the interface information.
The method for embedding an external system according to claim 1, wherein the front-end control of the workflow node is generated in the front-end subsystem according to the node parameter, so as to embed the external system as a workflow node After the steps in the workflow system, it further includes:

After detecting that the execution instruction of the workflow node corresponding to the external system is executed, determine the scheduling system corresponding to the execution instruction;

The tasks of the workflow node are converted according to the scheduling format of the scheduling system to obtain the converted tasks to be executed, and the converted tasks to be executed are sent to the Linkis client through the scheduling system to pass the Linkis The client executes the task to be executed after the conversion.
The method for embedding an external system according to any one of claims 1 to 7, wherein, after detecting that the loading instruction of the external system is loaded in the front-end subsystem of the workflow system, it passes through a preset node type table Before the step of determining the node type of the workflow node corresponding to the load instruction, the method further includes:

After detecting the embedding instruction of the workflow node corresponding to the external system in the workflow system, the node type of the workflow node is added to the node type table, and the job is added to the parameter configuration table The node parameters of the flow node.
A workflow system, wherein the workflow system includes:

The determining module is used to determine the node type of the workflow node corresponding to the load instruction through the preset node type table after detecting that the load instruction of the external system is loaded in the front-end subsystem of the workflow system;

An obtaining module, configured to obtain the node parameters of the workflow node in a preset parameter configuration table according to the node type;

The generating module is configured to generate the front-end control of the workflow node in the front-end subsystem according to the node parameters, so as to embed the external system as a workflow node in the workflow system.
An embedded device of an external system, wherein the embedded device of the external system includes a memory, a processor, and an embedded program of the external system that is stored on the memory and can run on the processor. When the embedded program is executed by the processor, the steps of the external system embedding method according to any one of claims 1 to 8 are realized.
A computer-readable storage medium, wherein an embedded program of an external system is stored on the computer-readable storage medium, and when the embedded program of the external system is executed by a processor, the implementation is as defined in any one of claims 1 to 8. The steps of the embedding method of the external system described.