WO2021068692A1

WO2021068692A1 - Method, apparatus and device for workflow migration, and computer-readable storage medium

Info

Publication number: WO2021068692A1
Application number: PCT/CN2020/113492
Authority: WO
Inventors: 刘有; 尹强; 王和平; 黄山; 杨峙岳; 邸帅; 卢道和
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-10-10
Filing date: 2020-09-04
Publication date: 2021-04-15
Also published as: CN110674083B; CN110674083A

Abstract

A method, apparatus, and device for workflow migration, and a computer-readable storage medium. The method for workflow migration comprises: acquiring a workflow file to be migrated, converting the workflow file to obtain a workflow file of a preset format, and denoting same as a first workflow file (S10); acquiring a target scheduling system, and according to the category of the target scheduling system, converting the first workflow file to obtain a workflow file corresponding to the target scheduling system, and denoting same as a second workflow file (S20); and sending the second workflow file to the target scheduling system so as to implement migration (S30).

Description

Workflow migration method, device, equipment and computer readable storage medium

This application claims the priority of the Chinese patent application filed on October 10, 2019, with the application number 201910961072.5, titled "Workflow Migration Method, Device, Equipment, and Computer-readable Storage Medium", which is hereby incorporated in its entirety as reference.

Technical field

This application relates to the technical field of financial technology (Fintech), and in particular to a workflow migration method, device, equipment, and computer-readable storage medium.

Background technique

With the development of computer technology, more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) are applied in the financial field. The traditional financial industry is gradually transforming to Fintech. However, due to financial The industry's security and real-time requirements also place higher requirements 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. The execution of jobs requires unified management and scheduling. We generally Use Distributed Visual DAG (Directed acyclic graph, directed acyclic graph) workflow task scheduling system. At present, the more popular systems include Oozie (task scheduling framework), Azkaban (batch workflow task scheduler), Airflow (workflow platform), etc. They all support the DAG diagram to associate Tasks according to their dependencies. Get up, perform distributed scheduling and execution, and support a wealth of task types.

However, the workflow definitions of different scheduling systems are not compatible. After a user defines a workflow on a system, if the workflow scheduling system needs to be replaced, the user is often required to redesign the original workflow or manually migrate the workflow. When a system has been used for a long time, the workflow in it has become very complex and huge. The task of workflow migration is very arduous. If the migration is performed manually, the migration efficiency is low. At the same time, the dependence relationship Very complex workflows only rely on manual migration and it is difficult to ensure the correctness of dependencies.

Technical solutions

The main purpose of this application is to provide a workflow migration method, device, equipment, and computer-readable storage medium, aiming to solve the problems of low migration efficiency and low accuracy of existing workflow migration methods.

To achieve the above objective, the present application provides a workflow migration method, the workflow migration method includes:

Obtain a workflow file to be migrated, convert the workflow file to be migrated, and obtain a workflow file in a preset format, which is recorded as the first workflow file;

Acquiring a target scheduling system, converting the first workflow file according to the type of the target scheduling system, and obtaining a workflow file corresponding to the target scheduling system, which is recorded as a second workflow file;

The second workflow file is sent to the target scheduling system to implement migration.

In some embodiments, before the step of converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system, the method further includes:

Importing the first workflow file into a preset workflow editing system to generate a corresponding workflow editing page, the workflow editing page including a workflow view;

Receiving a node editing instruction triggered by a user based on the workflow view, and modifying corresponding node attributes according to the node editing instruction to obtain a third workflow file;

The step of converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system includes:

The third workflow file is converted according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system.

In some embodiments, before the step of receiving a node editing instruction triggered by a user based on the workflow view, the method further includes:

When receiving a node editing request triggered by a user based on the workflow view, acquiring a target editing node according to the node editing request;

The attribute drop-down box corresponding to the target editing node is displayed, so that the user can select the corresponding node attribute from the attribute drop-down box and trigger the corresponding node editing instruction.

In some embodiments, the step of obtaining a workflow file to be migrated, converting the workflow file to be migrated to obtain a workflow file in a preset format, and recording it as the first workflow file includes:

Read the workflow file to be migrated, and analyze the content of the workflow file to be migrated to obtain the first node definition and the first edge definition;

Performing mapping conversion on the first node definition and the first edge definition based on a preset mapping relationship to obtain a second node definition and a second edge definition;

Based on the second node definition and the second edge definition to construct a file directory, a workflow file in a preset format is generated, which is recorded as the first workflow file.

In some embodiments, the step of converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system includes:

Determine the target conversion plug-in according to the type of the target scheduling system, call the target conversion plug-in to parse the first workflow file, obtain the dependency relationship and hierarchical relationship of the nodes in the corresponding workflow, and convert the workflow Into a scheduling workflow;

Converting each node based on the scheduling workflow to generate a definition file corresponding to each node, wherein the directory in which the definition file is located is determined according to the hierarchical relationship;

Set the dependency relationship to the attribute of the corresponding node, download the dependent resource file of each node to the directory where the corresponding definition file is located, and convert the node variable of each node into a feature file and place it in the directory where the corresponding definition file is located. To obtain the workflow file corresponding to the target scheduling system.

In some embodiments, the step of converting each node based on the scheduling workflow to generate a definition file corresponding to each node includes:

Obtaining the node type of each node based on the scheduling workflow, and obtaining corresponding parameter information according to the node type;

Based on the parameter information, each node is converted, and a definition file corresponding to each node is generated.

In some embodiments, before the step of sending the second workflow file to the target scheduling system to implement the migration, the method further includes:

Sending the second workflow file to a preset test terminal, so that the preset test terminal performs a test on the second workflow file;

After the test is passed, perform the step of sending the second workflow file to the target scheduling system to implement migration.

In addition, in order to achieve the above objective, the present application also provides a workflow migration device, which includes:

The first conversion module is configured to obtain a workflow file to be migrated, convert the workflow file to be migrated, and obtain a workflow file in a preset format, which is recorded as the first workflow file;

The second conversion module is used to obtain a target scheduling system, and convert the first workflow file according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system, which is recorded as a second workflow file;

The migration module is used to send the second workflow file to the target scheduling system to implement migration.

In addition, in order to achieve the above object, the present application also provides a workflow migration device, the workflow migration device includes: a memory, a processor, and a workflow migration stored in the memory and running on the processor A program that implements the steps of the workflow migration method as described above when the workflow migration program is executed by the processor.

In addition, in order to achieve the above objective, this application also provides a computer-readable storage medium having a workflow migration program stored on the computer-readable storage medium, and when the workflow migration program is executed by a processor, the above-mentioned The steps of the workflow migration method.

This application provides a workflow migration method, device, equipment, and computer-readable storage medium. By acquiring the workflow file to be migrated, the workflow file to be migrated is converted, and a workflow file in a preset format is obtained, which is recorded as the first job Flow file; Obtain the target scheduling system, that is, the system to be migrated into, and then convert the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system, which is recorded as the first 2. Workflow file; and then send the second workflow file to the target scheduling system to achieve migration. Through the above method, a general workflow format is defined in this application, which can automatically convert the workflow file to be migrated into a workflow file in a preset general format (ie, the first workflow file), and then schedule according to the target The type of the system, the first workflow file is converted to obtain the workflow file corresponding to the target scheduling system, and then the migration is performed. Therefore, this application can realize the automatic conversion and migration of the workflow file to be migrated, which can improve the workflow Migration efficiency, at the same time, can realize automatic analysis of the dependencies between workflow nodes during the conversion process, avoid the problem of analytic errors in manual migration in the prior art, thereby improving the accuracy of workflow migration in certain procedures.

Description of the drawings

FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the application;

2 is a schematic flowchart of the first embodiment of the workflow migration method of this application;

Figure 3 is a schematic diagram of a Json structure directory involved in the workflow migration method of this application;

FIG. 4 is a schematic diagram of functional modules of the first embodiment of the workflow migration device of this 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.

Referring to FIG. 1, FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the application.

The workflow migration device in the embodiment of this application can be a smart phone or a PC (Personal Computer, personal computer), tablet computer, portable computer and other terminal equipment.

As shown in FIG. 1, the workflow migration device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. 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.

Those skilled in the art can understand that the structure of the workflow migration device shown in FIG. 1 does not constitute a limitation on the workflow migration device, and may include more or less components than shown in the figure, or combine certain components, or be different. The layout of the components.

As shown in FIG. 1, a memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a workflow migration program.

In the terminal shown in FIG. 1, the network interface 1004 is mainly used to connect to a back-end server and communicate with the back-end server; the user interface 1003 is mainly used to connect to a client and communicate with the client; and the processor 1001 can be used to Call the workflow migration program stored in the memory 1005, and perform the following operations:

In some embodiments, the processor 1001 may call a workflow migration program stored in the memory 1005, and also perform the following operations:

After the test is passed, the second workflow file is sent to the target scheduling system to implement migration.

Based on the above hardware structure, various embodiments of the workflow migration method of the present application are proposed.

This application provides a workflow migration method.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a first embodiment of a workflow migration method of this application.

In this embodiment, the workflow migration method includes:

Step S10, obtaining a workflow file to be migrated, and converting the workflow file to be migrated to obtain a workflow file in a preset format, which is recorded as the first workflow file;

The workflow migration method in this embodiment is implemented by a workflow migration device, and the device is described by taking a server as an example. In this embodiment, a general workflow data structure is defined first, and the workflow file of the scheduling system to be migrated (that is, the workflow file to be migrated) is automatically converted into a workflow file of a preset general format. (That is, the first workflow file). Specifically, the workflow file to be migrated is obtained first, and the workflow file to be migrated is converted to obtain a workflow file in a preset format, which is recorded as the first workflow file. Among them, the preset format can be selected as Json (JavaScript Object Notation, a lightweight data exchange format based on JavaScript language) format.

For example, to TSS (Task Schedule System, task scheduling system) The workflow migration in the workflow scheduling system is explained as an example. You can first export the workflow file in the TSS system (that is, the workflow file to be migrated), and then call the corresponding automated conversion tool to migrate the workflow The file is converted, and the workflow file in Json format is obtained. Because different systems have different workflow file formats, different automated conversion tools need to be called for conversion. The TSS workflow scheduling system exports workflow files in SBT (a file type) format, which can be transferred from TSS to DWS (DataWorkShop, Data workshop) tool for conversion. Among them, the TSS to DWS tool can convert the SBT format to be migrated workflow files into Json format files, and organize them according to the file directory hierarchy to obtain the first workflow file.

Specifically, step S10 includes:

Step a1, reading the workflow file to be migrated, and analyzing the content of the workflow file to be migrated to obtain the first node definition and the first edge definition;

Step a2: Perform mapping conversion on the first node definition and the first edge definition based on a preset mapping relationship to obtain a second node definition and a second edge definition;

In step a3, a file directory is constructed based on the second node definition and the second edge definition, and a workflow file in a preset format is generated, which is recorded as the first workflow file.

First read the workflow file to be migrated, analyze the content of the workflow file to be migrated, and obtain the first node definition and the first edge definition, that is, the description and definition of the node in the content of the workflow file to be migrated will be converted into java operable The node object (that is, the first node definition), converts the definition of the edge into an operable edge object in java (that is, the first edge definition). Then, based on the preset mapping relationship, the first node definition and the first edge definition are mapped and converted to obtain the second node definition and the second edge definition, that is, the mapping is the definition corresponding to the preset format, where the second node definition includes Node name, type, attribute information, execution command, dependency definition and other information. The second edge definition includes the starting point and end point information of the edge. Furthermore, a file directory is constructed based on the second node definition and the second edge definition, and a workflow file in a preset format is generated, which is recorded as the first workflow file.

Specifically, the method of constructing the file directory is as follows: each workflow corresponds to a Json file definition. For the existence of sub-workflows, create a new file directory (denoted as a subdirectory) in the current directory, and add subdirectories to the subdirectory. Json file definition of workflow. If there are multiple sub-workflows at the same level, you need to create multiple file directories (ie multiple sub-directories). If there is a deeper level of nesting in the sub-workflow, the next-level workflow directory is created in the same way. The final output workflow files in Json format are organized according to hierarchical directories. Refer to Figure 3, which is a schematic diagram of a Json structure directory. Among them, the first-level directory corresponds to the top-level workflow of the original workflow file to be migrated, which is the original top-level All workflows of a Group, because there may be multiple parallel workflows in a Group, they can be numbered according to the workflow number; if there are nested sub-workflows under the top-level Group, they will be placed in In the directory with the same name as the workflow, put the second-level directory; the number of the workflow and the number of the directory are defined in the format of the name of the group-the current level-the number of the workflow.

Through the above method, it is possible to automatically analyze the dependencies between workflow nodes, automatically split the workflow subtrees, and analyze the dependencies of nested workflows hierarchically, keeping the useful information of the original nodes as much as possible and shifting to general Workflow to convert the workflow file to be migrated into a workflow with a common Json-defined structure.

Step S20: Obtain a target scheduling system, and convert the first workflow file according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system, which is recorded as a second workflow file;

Then, obtain the target scheduling system, that is, the system to be migrated into the workflow to be migrated, and then convert the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system, which is recorded as the second Workflow file.

Wherein, the step of "converting the first workflow file according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system" includes:

Step b1: Determine the target conversion plug-in according to the type of the target scheduling system, call the target conversion plug-in to parse the first workflow file to obtain the dependency relationship and hierarchical relationship of the nodes in the corresponding workflow, and combine the The workflow is converted into a scheduling workflow;

First determine the target conversion plug-in according to the type of the target scheduling system, call the target conversion plug-in to parse the first workflow file, obtain the dependency relationship and hierarchical relationship of the nodes in the corresponding workflow, and convert the workflow into a scheduling workflow. Taking the target scheduling system as the Azkaban system as an example, the corresponding conversion plug-in can be called. The conversion plug-in has predefined workflow conversion interface parseFlow (parse flow) and node conversion interface parseNode (parse node), which can be converted The conversion interface parseNode of the nodes in the plug-in parses the first workflow file to obtain the dependencies and hierarchical relationships of the nodes in the corresponding workflow, and converts the workflow into SchedulerFlow (scheduler workflow) through the workflow conversion interface parseFlow.

Step b2, converting each node based on the scheduling workflow to generate a definition file corresponding to each node, wherein the directory where the definition file is located is determined according to the hierarchical relationship;

Then, each node is converted based on the scheduling workflow to generate a definition file corresponding to each node, wherein the directory where the definition file is located is determined according to the hierarchical relationship obtained by the above analysis. Among them, the format of the definition file can be the .job format. Specifically, step b2 includes:

Step b21: Obtain the node type of each node based on the scheduling workflow, and obtain corresponding parameter information according to the node type;

Step b22: Transform each node based on the parameter information, and generate a definition file corresponding to each node.

The conversion of nodes needs to be converted according to the type. The conversion of different types of nodes is completely different. Therefore, first obtain the node type of each node based on the scheduling workflow, and obtain the corresponding parameter information according to the node type, for example, for the conversion of the shell type node , The parameter information that needs to be obtained includes node name, node type, node command, agent execution user, variable, parameter, resource file, etc. For the conversion of Spark type nodes, the parameter information that needs to be obtained includes node name, node type, drive (Drive) parameters, executor (execution) parameters, execution scripts, third-party jars (a software package file format), custom functions, hadoop (distributed system infrastructure) users, cluster addresses, etc. Then, each node is converted based on the parameter information, and a definition file corresponding to each node is generated.

Step b3: Set the dependency relationship to the attribute of the corresponding node, download the dependent resource file of each node to the directory where the corresponding definition file is located, and convert the node variable of each node into a feature file and place it in the corresponding definition file. In the directory where it is located, a workflow file corresponding to the target scheduling system is obtained.

After the definition file corresponding to each node is generated, the dependency relationship obtained by the above analysis is set to the attribute of the corresponding node to be saved as an attribute in the definition file. At the same time, the dependent resource file of each node needs to be downloaded to the corresponding In the directory where the definition file is located, the node variables of each node are respectively transformed into a characteristic (properties) file and placed in the directory where the corresponding definition file is located to obtain a workflow file corresponding to the target scheduling system.

It should be noted that in the specific implementation, you only need to add the conversion plug-in corresponding to the scheduling system, and you can complete similar conversions through the added conversion plug-in, and get the workflow file corresponding to the scheduling system, which can support the generation of multiple types of scheduling. Workflow files required by the system.

Step S30: Send the second workflow file to the target scheduling system to implement migration.

After the workflow file corresponding to the target scheduling system (ie, the second workflow file) is obtained by conversion, the second workflow file is sent to the target scheduling system to implement migration. When sending the second workflow file, the project publishing interface of the target scheduling system can be called to upload.

The embodiment of the application provides a workflow migration method. By acquiring the workflow file to be migrated, the workflow file to be migrated is converted to obtain a workflow file in a preset format, which is recorded as the first workflow file; obtaining a target scheduling system, That is, the system to be migrated into the workflow to be migrated, and then the first workflow file is converted according to the type of the target scheduling system, and the workflow file corresponding to the target scheduling system is obtained, which is recorded as the second workflow file; Second, the workflow file is sent to the target scheduling system to achieve migration. Through the above method, a universal workflow format is defined in the embodiments of this application, which can automatically convert the workflow file to be migrated into a workflow file in a preset universal format (that is, the first workflow file), and then according to For the type of the target scheduling system, the first workflow file is converted to obtain the workflow file corresponding to the target scheduling system, and then the migration is performed. Therefore, the embodiment of the present application can realize the automatic conversion and migration of the workflow file to be migrated. Improve the efficiency of workflow migration. At the same time, it can automatically analyze the dependencies between workflow nodes during the conversion process, avoiding the analytic errors in manual migration in the prior art, thereby improving the accuracy of workflow migration in certain procedures. Sex.

Further, based on the first embodiment shown in FIG. 2, a second embodiment of the workflow migration method of the present application is proposed.

In this embodiment, before the step "converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system", the workflow migration method further includes :

Step A: Import the first workflow file into a preset workflow editing system to generate a corresponding workflow editing page, and the workflow editing page includes a workflow view;

Due to the differences in the definition of nodes between different workflow systems, although most systems support Shell-type jobs, they have different definitions and usage methods for signal nodes and big data nodes, such as node definitions and dependencies. The resource file reference method, environment variable definition, variable replacement, property file, etc. are different, which cannot be set in the prior art.

In this regard, in this embodiment, a workflow editing system is provided for editing the workflow converted into a preset format (that is, the first workflow file). Specifically, the first workflow file is imported into the preset work The flow editing system generates a corresponding workflow editing page, where the workflow editing page includes the workflow view, the annotation description of the icon, and the editing icon, etc., and the user performs editing and modification work based on the workflow editing page, For example, modify node attributes.

Step B, receiving a node editing instruction triggered by the user based on the workflow view, and modifying corresponding node attributes according to the node editing instruction to obtain a third workflow file;

Furthermore, the node editing instruction triggered by the user based on the workflow view is received, and the corresponding node attribute is modified according to the node editing instruction to obtain the third workflow file.

Before the above step B, the workflow migration method further includes:

Step C, when receiving a node editing request triggered by the user based on the workflow view, obtaining a target editing node according to the node editing request;

Step D: Display the attribute drop-down box corresponding to the target editing node, so that the user can select the corresponding node attribute from the attribute drop-down box and trigger the corresponding node editing instruction.

When users need to set node attributes, they can click the corresponding node box in the workflow view to trigger a node edit request. At this time, when the server receives a node edit request triggered by the user based on the workflow view, it will follow the node edit request Obtain the target edit node; then, display the attribute drop-down box corresponding to the target edit node, so that the user can select the corresponding node attribute from the attribute drop-down box and trigger the corresponding node editing instruction. Of course, in addition to the preset node attributes, the attribute drop-down box may also include manual input options to provide the function of manually inputting node attributes. Of course, other function options can be set correspondingly in the attribute drop-down box, such as the upload of resource files, the definition of global variables, etc., which can be set according to actual needs, and there is no specific limitation here.

At this time, in step S20, "converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system" includes:

After editing and modifying, the third workflow file is obtained, and then the third workflow file is converted according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system, and the subsequent steps are executed. For the specific execution process, please refer to The above-mentioned first embodiment will not be repeated here.

This embodiment implements visual workflow editing through a preset workflow editing system. It only needs to import the converted Json format workflow (that is, the first workflow file), and then the nodes in the workflow can be checked on the workflow editing page. Attributes are set to solve the problem of node attributes that cannot be automatically converted, such as the parameter setting of signal nodes, the upload of resource files, the definition of global variables, etc., and complex big data core batch business logic can be constructed.

Further, based on the foregoing embodiments, a third embodiment of the workflow migration method of the present application is proposed.

In this embodiment, before step S30, the workflow migration method further includes:

Step E, sending the second workflow file to a preset test terminal, so that the preset test terminal performs a test on the second workflow file;

After the test is passed, step S30 is executed: the second workflow file is sent to the target scheduling system to implement migration.

In this embodiment, after the corresponding second workflow file is converted according to the type of the target scheduling system, in order to ensure that the converted second workflow file has no problems and can be used normally, it can be used directly by the target scheduling system. The second workflow file is sent to the preset test terminal, so that the preset test terminal tests the second workflow file. Specifically, in the testing process, the tester corresponding to the preset test terminal can debug and execute the second workflow file in the test environment to detect whether there is a problem. After the test is passed, the second workflow file is sent to the target scheduling system to realize the migration. When sending the second workflow file, the project publishing interface of the target scheduling system can be called to upload.

When the test fails, the corresponding prompt message can be generated so that the staff can carry out further debugging and modification. When the test passes, the working file after debugging and modification can be sent to the target scheduling system.

Of course, it can be understood that during specific implementation, the second workflow file can be directly sent to the target scheduling system, and the target scheduling system is tested separately, and after the test passes, it is released to the production environment for use.

In the above manner, the converted second workflow file is tested in advance to ensure that the second workflow file has no problems and can be released to the production environment for use, which is convenient for direct use by the target scheduling system.

The application also provides a workflow migration device.

Referring to FIG. 4, FIG. 4 is a schematic diagram of the functional modules of the first embodiment of the workflow migration device of this application.

As shown in Figure 4, the workflow migration device includes:

The first conversion module 10 is configured to obtain a workflow file to be migrated, convert the workflow file to be migrated, and obtain a workflow file in a preset format, which is recorded as the first workflow file;

The second conversion module 20 is configured to obtain a target scheduling system, convert the first workflow file according to the type of the target scheduling system, and obtain a workflow file corresponding to the target scheduling system, which is recorded as the second job Stream file

The migration module 30 is configured to send the second workflow file to the target scheduling system to implement migration.

In some embodiments, the workflow migration device further includes:

A generating module, configured to import the first workflow file into a preset workflow editing system to generate a corresponding workflow editing page, and the workflow editing page includes a workflow view;

The modification module is configured to receive a node editing instruction triggered by a user based on the workflow view, and modify corresponding node attributes according to the node editing instruction to obtain a third workflow file;

The migration module 30 is specifically configured to convert the third workflow file according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system.

In some embodiments, the workflow migration device further includes:

The obtaining module is configured to obtain a target editing node according to the node editing request when a node editing request triggered by the user based on the workflow view is received;

The display module is used to display the attribute drop-down box corresponding to the target editing node, so that the user can select the corresponding node attribute from the attribute drop-down box and trigger the corresponding node editing instruction.

In some embodiments, the first conversion module 10 includes:

The first parsing unit is configured to read the workflow file to be migrated, and analyze the content of the workflow file to be migrated to obtain the first node definition and the first edge definition;

The second conversion unit is configured to perform mapping conversion on the first node definition and the first edge definition based on a preset mapping relationship to obtain a second node definition and a second edge definition;

The first generating unit is configured to construct a file directory based on the second node definition and the second edge definition, and generate a workflow file in a preset format, which is recorded as the first workflow file.

In some embodiments, the second conversion module 20 includes:

The second parsing unit is configured to determine the target conversion plug-in according to the type of the target scheduling system, call the target conversion plug-in to parse the first workflow file, and obtain the dependency relationship and hierarchical relationship of the nodes in the corresponding workflow, And convert the workflow into a scheduling workflow;

The second conversion unit is configured to convert each node based on the scheduling workflow to generate a definition file corresponding to each node, wherein the directory in which the definition file is located is determined according to the hierarchical relationship;

The second generating unit is used to set the dependency relationship to the attribute of the corresponding node, download the dependent resource file of each node to the directory where the corresponding definition file is located, and convert the node variable of each node into a feature file and place it Go to the directory where the corresponding definition file is located, and obtain the workflow file corresponding to the target scheduling system.

In some embodiments, the second conversion unit is specifically configured to:

In some embodiments, the workflow migration device further includes:

A test module, configured to send the second workflow file to a preset test terminal, so that the preset test terminal performs a test on the second workflow file;

The migration module 30 is specifically configured to send the second workflow file to the target scheduling system after the test is passed, so as to realize the migration.

Among them, the function realization of each module in the above-mentioned workflow migration apparatus corresponds to each step in the above-mentioned workflow migration method embodiment, and the functions and realization processes thereof will not be repeated here.

The present application also provides a computer-readable storage medium with a workflow migration program stored on the computer-readable storage medium. When the workflow migration program is executed by a processor, the workflow as described in any of the above embodiments is implemented. Steps of the migration method.

The specific embodiments of the computer-readable storage medium of the present application are basically the same as the embodiments of the above-mentioned workflow migration method, 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 system including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, method, article, or system. Without 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 system that includes the element.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the superiority 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) as described above. , Magnetic disks, optical disks), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) 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

A workflow migration method, wherein the workflow migration method includes:

Obtain a workflow file to be migrated, convert the workflow file to be migrated, and obtain a workflow file in a preset format, which is recorded as the first workflow file;

Acquiring a target scheduling system, converting the first workflow file according to the type of the target scheduling system, and obtaining a workflow file corresponding to the target scheduling system, which is recorded as a second workflow file; and

The second workflow file is sent to the target scheduling system to implement migration.
The workflow migration method according to claim 1, wherein before the step of converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system ,Also includes:

Importing the first workflow file into a preset workflow editing system to generate a corresponding workflow editing page, the workflow editing page including a workflow view; and

Receiving a node editing instruction triggered by a user based on the workflow view, and modifying corresponding node attributes according to the node editing instruction to obtain a third workflow file;

The step of converting the first workflow file according to the type of the target scheduling system to obtain the workflow file corresponding to the target scheduling system includes:

The third workflow file is converted according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system.
3. The workflow migration method according to claim 2, wherein before the step of receiving a node editing instruction triggered by a user based on the workflow view, the method further comprises:

When receiving a node editing request triggered by the user based on the workflow view, acquiring the target editing node according to the node editing request; and

The attribute drop-down box corresponding to the target editing node is displayed, so that the user can select the corresponding node attribute from the attribute drop-down box and trigger the corresponding node editing instruction.
The workflow migration method according to any one of claims 1 to 3, wherein said obtaining the workflow file to be migrated, converting the workflow file to be migrated to obtain a workflow file in a preset format, and recording The steps for the first workflow file include:

Read the workflow file to be migrated, and analyze the content of the workflow file to be migrated to obtain the first node definition and the first edge definition;

Performing mapping conversion on the first node definition and the first edge definition based on a preset mapping relationship to obtain a second node definition and a second edge definition; and

Based on the second node definition and the second edge definition to construct a file directory, a workflow file in a preset format is generated, which is recorded as the first workflow file.
The workflow migration method according to any one of claims 1 to 3, wherein the first workflow file is converted according to the type of the target scheduling system to obtain the corresponding to the target scheduling system The steps of the workflow file include:

Determine the target conversion plug-in according to the type of the target scheduling system, call the target conversion plug-in to parse the first workflow file, obtain the dependency relationship and hierarchical relationship of the nodes in the corresponding workflow, and convert the workflow Into a scheduling workflow;

Converting each node based on the scheduling workflow to generate a definition file corresponding to each node, wherein the directory in which the definition file is located is determined according to the hierarchical relationship; and

Set the dependency relationship to the attribute of the corresponding node, download the dependent resource file of each node to the directory where the corresponding definition file is located, and convert the node variable of each node into a feature file and place it in the directory where the corresponding definition file is located. To obtain the workflow file corresponding to the target scheduling system.
8. The workflow migration method according to claim 5, wherein the step of converting each node based on the scheduling workflow to generate a definition file corresponding to each node comprises:

Obtain the node type of each node based on the scheduling workflow, and obtain corresponding parameter information according to the node type; and

Based on the parameter information, each node is converted, and a definition file corresponding to each node is generated.
The workflow migration method according to any one of claims 1 to 3, wherein before the step of sending the second workflow file to the target scheduling system to implement the migration, the method further comprises:

Sending the second workflow file to a preset test terminal, so that the preset test terminal tests the second workflow file; and

After the test is passed, perform the step of sending the second workflow file to the target scheduling system to implement migration.
A workflow migration device, wherein the workflow migration device includes:

The first conversion module is configured to obtain a workflow file to be migrated, convert the workflow file to be migrated, and obtain a workflow file in a preset format, which is recorded as the first workflow file;

The second conversion module is used to obtain a target scheduling system, and convert the first workflow file according to the type of the target scheduling system to obtain a workflow file corresponding to the target scheduling system, which is recorded as a second workflow Files; and

The migration module is used to send the second workflow file to the target scheduling system to implement migration.
A workflow migration device, wherein the workflow migration device includes a memory, a processor, and a workflow migration program stored on the memory and running on the processor, and the workflow migration program is The processor implements the steps of the workflow migration method according to any one of claims 1 to 7 when executed.
A computer-readable storage medium, wherein a workflow migration program is stored on the computer-readable storage medium, and when the workflow migration program is executed by a processor, the workflow migration program as described in any one of claims 1 to 7 is realized. The steps of the workflow migration method.