CN111208992A - System scheduling workflow generation method and system - Google Patents
System scheduling workflow generation method and system Download PDFInfo
- Publication number
- CN111208992A CN111208992A CN202010027930.1A CN202010027930A CN111208992A CN 111208992 A CN111208992 A CN 111208992A CN 202010027930 A CN202010027930 A CN 202010027930A CN 111208992 A CN111208992 A CN 111208992A
- Authority
- CN
- China
- Prior art keywords
- service module
- node
- module
- called
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/33—Intelligent editors
Abstract
The embodiment of the application provides a system scheduling workflow generation method, which comprises the following steps: providing a configuration interface for a user to configure each service module required to be called for realizing financial services, parameters of each service module and a connection relation between each service module; after the user finishes configuration operation, generating a configuration file for realizing financial service according to the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial service, parameter configuration information of each service module and a connection relation between each service module; and converting the configuration file into an XML file executable by the workflow engine. The embodiment of the application can save the development time required by realizing the business target, reduce the cost and has higher flexibility.
Description
Technical Field
The embodiment of the application relates to the technical field of cloud, in particular to a system scheduling workflow generation method, a system, equipment and a computer readable storage medium.
Background
The workflow technology is a core technology for realizing business process automation. The workflow mainly solves the problem of automatically transferring documents, information or tasks between a plurality of participants according to predetermined rules by using a computer in order to achieve a certain business objective.
However, the traditional workflow technology can only realize a certain service goal by connecting different functional interfaces in series in a single system, and if an external system needs to be connected in series to realize the service goal, customized code development needs to be performed, so that the cost is high, and the flexibility is poor.
Disclosure of Invention
The embodiment of the application aims to provide a system scheduling workflow generation method, a system, computer equipment and a computer readable storage medium, which are used for solving the problems that customized code development is needed when an external system is connected in series to achieve a business target, the cost is high and the flexibility is poor in the traditional workflow technology.
One aspect of the present embodiment provides a method for generating a system scheduling workflow, where the method for generating the system scheduling workflow includes: providing a configuration interface for a user to configure each service module required to be called for realizing financial services, parameters of each service module and a connection relation between each service module; after the user finishes configuration operation, generating a configuration file for realizing financial service according to the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial service, parameter configuration information of each service module and a connection relation between each service module; and converting the configuration file into an XML file executable by a workflow engine, wherein the parameter configuration information comprises the calling type information of each service module, and the converting the configuration file into the XML file executable by the workflow engine comprises the following steps: converting each service module to be called into a corresponding flow activity node according to the calling type information of each service module, wherein the flow activity node is an executable XML fragment; adding the parameter configuration information of each service module except the calling type information into the process activity node; and connecting the obtained flow activity nodes in series according to the connection relation to obtain a final executable XML file.
Optionally, the invoking type information includes a synchronous interface invocation and an asynchronous interface invocation, and the converting each service module to be invoked into a corresponding flow activity node according to the invoking type information of each service module includes: if the calling type of the service module needing to be called currently is synchronous interface calling, converting the service module needing to be called currently into an atomic flow active node; if the calling type of the service module needing to be called currently is asynchronous interface calling, the service module needing to be called currently is converted into three atomic flow activity nodes, namely a calling flow activity node, a waiting callback flow activity node and a callback result processing flow activity node.
Optionally, after the step of converting each service module to be called into a corresponding flow activity node according to the calling type information of each service module, the method further includes: and adding transaction rollback operation which needs to be executed when calling each service module fails in the process activity node.
Optionally, the parameter configuration information includes logic judgment information, and after the step of converting each service module to be called into a corresponding flow activity node according to the call type information of each service module, the method further includes: and generating a branch judgment condition according to the logic judgment information, and adding the branch judgment condition to the flow activity node.
Optionally, the parameter configuration information includes timeout processing information, and after the step of converting each service module to be called into a corresponding flow activity node according to the call type information of each service module, the method further includes: and generating a timing task according to the overtime processing information, and adding the timing task to the flow activity node.
Optionally, the step of concatenating the obtained flow activity nodes according to the connection relationship to obtain a final executable XML file includes: dividing each obtained process activity node into a plurality of groups of process activity node pairs to be connected according to the connection relation, wherein each group of process activity node pairs comprises a source node and a target node; and connecting the source node in each group of process active node pairs to the target node through a preset function.
Optionally, the preset function is a SourceRef function and a TargetRef function.
An aspect of the embodiments of the present application further provides a system scheduling workflow generating apparatus, where the system scheduling workflow generating apparatus includes: the system comprises a providing module, a connecting module and a processing module, wherein the providing module is used for providing a configuration interface for a user to configure each service module required to be called for realizing financial service, parameters of each service module and the connection relation among the service modules; the generating module is used for generating a configuration file for realizing financial services according to the configuration operation after the user finishes the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial services, parameter configuration information of each service module and a connection relation between each service module; the conversion module is used for converting the configuration file into an XML file which can be executed by a workflow engine, wherein the parameter configuration information comprises the calling type information of each business module, and the conversion module is also used for converting each business module to be called into a corresponding process activity node according to the calling type information of each business module, wherein the process activity node is an executable XML fragment; adding the parameter configuration information of each service module except the calling type information into the process activity node; and connecting the obtained flow activity nodes in series according to the connection relation to obtain a final executable XML file.
An aspect of the embodiments of the present application further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the steps of the method for generating a system scheduling workflow described above when executing the computer program.
An aspect of the embodiments of the present application further provides a computer-readable storage medium, in which a computer program is stored, where the computer program is executable by at least one processor, so as to cause the at least one processor to execute the steps of the system scheduling workflow generation method described above.
The method, the device, the equipment and the computer-readable storage medium for generating the system scheduling workflow provided by the embodiment of the application can convert the acquired configuration file into an XML file which can be executed by a workflow engine by acquiring the configuration file for realizing the financial business. Compared with the traditional mode needing customized code development, the method and the device do not need developers to develop codes, save development time needed by realizing business targets, reduce cost and have high flexibility.
Drawings
Fig. 1 schematically shows a flowchart of a system scheduling workflow generation method according to a first embodiment of the present application;
FIG. 2 is a flow diagram schematically illustrating a detailed step of the present invention in converting the configuration file into an XML file executable by the workflow engine;
FIG. 3 is a detailed flowchart schematically illustrating the steps of concatenating the obtained flow activity nodes according to the connection relationship to obtain a final executable XML file;
fig. 4 schematically shows a block diagram of a system scheduling workflow generation apparatus according to a second embodiment of the present application; and
fig. 5 schematically shows a hardware architecture diagram of a computer device suitable for implementing the system scheduling workflow generation method according to a third embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more clearly understood, the embodiments of the present application are described in further detail below with reference to the accompanying drawings and the embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the embodiments of the application and are not intended to limit the embodiments of the application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the embodiments in the present application.
It should be noted that the descriptions relating to "first", "second", etc. in the embodiments of the present application are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope claimed by the embodiments of the present application.
Example one
Fig. 1 schematically shows a flowchart of a method for generating a system scheduling workflow according to a first embodiment of the present application. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. The following description is made by way of example with the computer device 2 as the execution subject.
As shown in fig. 1, the method for generating a system scheduling workflow may include steps S100 to S102, where:
step S100, providing a configuration interface for a user to configure each service module required to be called for realizing the financial service, parameters of each service module and a connection relation among the service modules.
Step S102, after the user finishes the configuration operation, generating a configuration file for realizing the financial service according to the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial service, parameter configuration information of each service module and a connection relation between each service module.
The financial service in this embodiment may be a monitoring, approval, operation and other services inside the enterprise, and may be, for example, a loan approval service, a credit card application service, a loan payment service and the like. The implementation of each financial service requires processing according to a specific flow through a plurality of service modules in the internal management process of the financial service to implement the financial service. Wherein each service module (or service system) can implement a service function.
For example, when a loan payment service is implemented, the loan payment service can be completed generally through the following process steps by the following service modules: 1) the credit system is required to be called to check the credit of the borrower; 2) if the credit system successfully checks the credit of the borrower, the loan system is required to transfer and deposit money; 3) after the deposit system deposits money, the deposit system is required to call back the deposit result; 4) when the loan result of the loan system is successful, the loan amount system needs to be called again to deduct the credit line of the borrower; 5) after the deduction of the amount is finished, an order system is required to be called to record the order released by the borrower so as to update the released order; 6) and finally, calling a short message system to send a short message to inform the borrower of completing loan payment.
In order to implement the financial service, a configuration interface may be provided on the computer device 2, and a user (which may be a non-developer, such as a product manager) may configure, through the configuration interface, each service module that needs to be invoked to implement the financial service, configure parameters of each service module, and configure a connection relationship between each service module. After the user completes the configuration operation, a configuration file for implementing the financial service is generated and stored so that the configuration file can be acquired by the computer device 2. Correspondingly, the configuration file comprises all service modules required to be called for realizing the financial service, parameter configuration information of all the service modules and connection relations among all the service modules. The parameter configuration information may include call type information of the service module, logic judgment information, interface call address information, interface call mode information, and access parameter configuration information of the service module.
The service calling type information is information for representing whether a service interface provided for the service module belongs to synchronous interface calling or asynchronous interface calling.
The logic judgment information is information for setting different flow branches of different return results of the service module, and specifically, the logic judgment information is generally an IF logic judgment statement, for example, IF a return value included in the return result of the service module a is set to be 1, the call flow is ended, and IF a return value included in the return result of the service module a is set to be 0, the call flow of the service module B is removed. For another example, IF the IF logic judgment statement sets that no result is returned by the service module a within 10 hours, the call flow is ended, and IF the result is returned by the service module a within 10 hours, the flow of the service module C is called.
The interface calling address information is an address to which the service interface provided by the service module is to be called, for example, an identification code ID of the external system module.
The interface calling mode information is used for calling whether a service interface provided by the service calling module belongs to http request mode calling or cloud transmission mode calling.
The configuration information of the access parameters of the service module is the configuration information of the access parameters and the access parameters of the service module, and comprises field type conversion, field format conversion, parameter assignment and the like of the access parameters and the access parameters.
Step S104, converting the configuration file into an XML file which can be executed by the workflow engine.
The computer device 2 may obtain the configuration file, that is, may convert the configuration file into an Extensible Markup Language (XML) file executable by a workflow engine, where XML may be used to mark data and define data types, and is a source Language allowing a user to define its own Markup Language.
The workflow engine can be a jbpm workflow engine, an Activiti workflow engine and the like. The jBpm is a flexible and extensible workflow engine system, and the business process input by the server during the operation of the jBpm is expressed by using a simple and powerful language and packaged in a process file. jBmp combines the convenience of workflow application development with outstanding Enterprise Application Integration (EAI) capabilities. jBmp includes a Web application and a scheduler. jBmp is a set of J2SE components that can be deployed as a J2EE application cluster. Activiti is a lightweight, embeddable BPM engine, and is also designed for use in an extensible cloud architecture.
Since the call conversion of each service module is performed according to the call type information of each service module included in the parameter configuration information, the call type information includes a synchronous interface call and an asynchronous interface call. In an exemplary embodiment, referring to fig. 2, the step S104 may include the steps of:
step S200, converting each service module to be called into a corresponding flow activity node according to the calling type information of each service module, wherein the flow activity node is an executable XML fragment.
Each service module has corresponding calling type information, and the calling type information of different service modules can be the same or different, for example, the calling type information of the service module a is called by a synchronous interface, the calling type information of the service module B is called by a synchronous interface, and the calling type information of the service module C is called by an asynchronous interface.
After the calling type information of each service module is obtained, the calling process of the service module can be converted into a corresponding flow active node (Task). For example, the call to the service module a is converted to Task1, the call to the service module B is converted to Task2, and the call to the service module C is converted to Task 3. It should be noted that, in order to distinguish different process activity nodes, different process activity nodes have different node Identifications (IDs). The converted flow active nodes conform to the BPMN standard. The BPMN standard develops a standard called Business Process modeling notation (BPMN-Business Process modeling notation) for bpmi (the Business Process management initiative).
The process activity nodes are different due to different call type conversions. In an exemplary embodiment, the step S200 may include the steps of: if the calling type of the service module required to be called currently is synchronous interface calling, converting the service module required to be called currently into an atomicity flow active node (serviceTask 0); if the calling type of the service module required to be called currently is asynchronous interface calling, the service module required to be called currently is converted into three atomicity flow activity nodes, namely a call-out flow activity node (serviceTask1), a waiting call-back flow activity node (receiveTask), and a call-back result processing flow activity node (serviceTask 2).
In this embodiment, the processing of the call-out flow active node (serviceTask1) is consistent with the processing of the flow active node (serviceTask0) corresponding to the synchronous interface call, if the call-out flow active node (serviceTask1) successfully calls the service module, the call-back flow active node (receiveTask) is in a waiting state to wait for being called up, and after waiting for the call-back flow active node (receiveTask) to receive the interface call-back information, and after receiving the interface call-back information, the call-back parameter is transmitted to the call-back result processing flow active node (serviceTask2) for processing, and after the call-back result processing flow active node (serviceTask2) finishes processing the call-back result, the processed result is subjected to flow load and is transmitted to the next flow active node.
Step S202, adding the parameter configuration information of each service module except the calling type information to the process activity node.
After converting each service module to be called into a corresponding process activity node, the computer device 2 needs to add parameter configuration information of the parameter configuration information of each service module except the calling type information to the process activity node, so that when the workflow engine executes the process activity node, the workflow engine can perform corresponding conversion on the input and output parameters of the service module according to the parameter configuration information, so as to convert the parameters into parameters meeting the system specification.
Since a scheduling exception may occur during the process of calling the service module, in order to handle the scheduling exception, in an exemplary embodiment, after the step S200, the following step may be further included: and adding transaction rollback operation which needs to be executed when calling each service module fails in the process activity node.
By adding transaction rollback operation in the flow active node, the workflow engine can capture the message of call failure/exception when executing the flow active node, and call back according to the provided failure rollback interface, and the flow active node itself also performs transaction rollback to the state before executing the flow active node.
When the parameter configuration information includes the logic judgment information, different return results of the service module may take different flow branches. In order to take different flow branches according to different return results after the calling of the service module, in an exemplary embodiment, after the step S200, the following steps may be further included: and generating a branch judgment condition according to the logic judgment information, and adding the branch judgment condition to the flow activity node.
By adding the branch judgment condition (explicaivegateway) in the flow active node, the workflow engine can decide which flow branch to execute later according to different return results when executing the flow active node, so that the return results can be transmitted to the next flow active node by flow bearing.
When the parameter configuration information includes the timeout processing information, the service module can be scheduled to be configured according to the timeout time. The timeout processing information includes specific time, for example, 5 days, for the service module to process timeout, and the service module scheduled after the service module processes timeout, for example, after the service module a processes timeout, the service module B is invoked. Therefore, in order to implement the configuration of the service module schedule according to the timeout time, in an exemplary embodiment, after the step S200, the following step may be further included: and generating a timing task according to the overtime processing information, and adding the timing task to the flow activity node.
By adding the timing task in the flow node, the workflow engine can judge whether the processing of the business module is overtime according to the timing task when executing the flow activity node, and execute the next flow activity node after the overtime.
And step S204, the obtained flow activity nodes are connected in series according to the connection relation to obtain a final executable XML file.
Because each flow activity node is an XML fragment, the complete XML file can be obtained by splicing the XML fragments according to the connection relation. And the connection relation is the calling sequence of each service module.
Computer device 2 may concatenate the various process activity nodes in a variety of ways. In an exemplary embodiment, referring to fig. 3, the step S204 includes:
and S300, dividing the obtained process activity nodes into a plurality of groups of process activity node pairs to be connected according to the connection relation, wherein each group of process activity node pairs comprises a source node and a target node.
And S302, connecting the source node in each group of process active node pairs to the target node through a preset function.
It should be noted that, each of the process activity nodes except the start activity node and the end activity node exists in two sets of process activity node pairs to be connected, and one set of the process activity node pairs to be connected serves as a source node and the other set of the process activity node pairs to be connected serves as a target node. Therefore, the source node in each set of process active node pairs can be connected to the target node through a preset function. In an exemplary embodiment, the source node of each set of flow active node pairs may be connected to the target node by a SourceRef function and a TargetRef function.
For example, if a first process activity node (serviceTask1), a second process activity node (serviceTask2), and a third process activity node (receiveTask1) need to be connected in series, the following functions may be implemented:
sourceRef＝“serviceTask1”targetRef“serviceTask2”
sourceRef＝“serviceTask2”targetRef“receiveTask1”
the function implementation process is to connect the first process active node and the second process active node in series. And then, the second process activity node and the third process activity node are connected in series, so that a complete XML file can be obtained.
In an exemplary embodiment, after the step S102, the method further includes:
and executing the XML file to realize the financial service.
The computer device 2 converts the configuration file into an XML file executable by the workflow engine, that is, the XML file can be executed by the workflow engine to implement the financial service.
In an exemplary embodiment, the workflow engine may record the time taken by the process of calling each business module and record the parameters in the calling process during the process of executing the XML file, so that the system can monitor the calling process.
According to the embodiment of the application, the configuration file for realizing the financial business can be obtained, and then the obtained configuration file can be converted into the XML file which can be executed by the workflow engine. Compared with the traditional mode needing customized code development, the method and the device do not need developers to develop codes, save development time needed by realizing business targets, reduce cost and have high flexibility.
Example two
Fig. 4 schematically shows a block diagram of a system scheduling workflow generation apparatus according to the second embodiment of the present application, which may be divided into one or more program modules, and the one or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiments of the present application. The program modules referred to in the embodiments of the present application refer to a series of computer program instruction segments that can perform specific functions, and the following description will specifically describe the functions of the program modules in the embodiments.
As shown in fig. 4, the system scheduling workflow generating apparatus 400 may include a providing module 410, a generating module 420, and a converting module 430, wherein:
a providing module 410, configured to provide a configuration interface, so that a user can configure each service module that needs to be invoked for implementing a financial service, parameters of each service module, and a connection relationship between each service module.
A generating module 420, configured to generate a configuration file for implementing the financial service according to the configuration operation after the user completes the configuration operation, where the configuration file includes each service module that needs to be called to implement the financial service, parameter configuration information of each service module, and a connection relationship between the service modules
A conversion module 430, configured to convert the configuration file into an XML file executable by a workflow engine, where the parameter configuration information includes call type information of each service module, and the conversion module is further configured to convert each service module to be called into a corresponding flow activity node according to the call type information of each service module, where the flow activity node is an executable XML fragment; adding the parameter configuration information of each service module except the calling type information into the process activity node; and connecting the obtained flow activity nodes in series according to the connection relation to obtain a final executable XML file.
In an exemplary embodiment, when the call type information includes a synchronous interface call and an asynchronous interface call, the conversion module 430 is further configured to: if the calling type of the service module needing to be called currently is synchronous interface calling, converting the service module needing to be called currently into an atomic flow active node; if the calling type of the service module needing to be called currently is asynchronous interface calling, the service module needing to be called currently is converted into three atomic flow activity nodes, namely a calling flow activity node, a waiting callback flow activity node and a callback result processing flow activity node.
In an exemplary embodiment, the conversion module 430 is further configured to: and adding transaction rollback operation which needs to be executed when calling each service module fails in the process activity node.
In an exemplary embodiment, the conversion module 430 is further configured to: and generating a branch judgment condition according to the logic judgment information, and adding the branch judgment condition to the flow activity node.
In an exemplary embodiment, when the parameter configuration information includes timeout processing information, the converting module 430 is further configured to: and generating a timing task according to the overtime processing information, and adding the timing task to the flow activity node.
In an exemplary embodiment, the conversion module 420 is further configured to: dividing each obtained process activity node into a plurality of groups of process activity node pairs to be connected according to the connection relation, wherein each group of process activity node pairs comprises a source node and a target node; and connecting the source node in each group of process active node pairs to the target node through a preset function.
In an exemplary embodiment, the preset functions are a SourceRef function and a TargetRef function.
In an exemplary embodiment, the system scheduling workflow generating apparatus 400 further includes:
and the execution module is used for executing the XML file so as to realize the financial service.
EXAMPLE III
Fig. 5 schematically shows a hardware architecture diagram of a computer device 2 suitable for implementing the system scheduling workflow generation method according to the third embodiment of the present application. In the present embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a command set in advance or stored. For example, the server may be a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers) with a gateway function. As shown in fig. 5, the computer device 6 includes at least, but is not limited to: memory 510, processor 520, and network interface 530 may be communicatively linked to each other by a system bus. Wherein:
the memory 510 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 510 may be an internal storage module of the computer device 2, such as a hard disk or a memory of the computer device 2. In other embodiments, the memory 510 may also be an external storage device of the computer device 2, such as a plug-in hard disk provided on the computer device 2, a Smart Memory Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. Of course, memory 510 may also include both internal and external memory modules of computer device 2. In this embodiment, the memory 510 is generally used for storing an operating system installed in the computer device 2 and various types of application software, such as program codes of a system scheduling workflow generation method. In addition, the memory 510 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 520 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 520 is generally used for controlling the overall operation of the computer device 2, such as performing control and processing related to data interaction or communication with the computer device 2. In this embodiment, processor 520 is configured to execute program codes stored in memory 510 or process data.
It should be noted that FIG. 5 only shows a computer device having components 510 and 530, but it should be understood that not all of the shown components are required and that more or fewer components may be implemented instead.
In this embodiment, the method for generating the system scheduling workflow stored in the memory 510 may also be divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 520) to implement the embodiments of the present application.
Example four
The present embodiments also provide a computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the steps of:
acquiring a configuration file for realizing financial services, wherein the configuration file comprises each service module required to be called for realizing the financial services, parameter configuration information of each service module and a connection relation between each service module; and
and converting the configuration file into an XML file executable by a workflow engine.
In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the computer readable storage medium may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the computer device. Of course, the computer-readable storage medium may also include both internal and external storage devices of the computer device. In this embodiment, the computer-readable storage medium is generally used for storing an operating system and various types of application software installed in a computer device, for example, the program code of the system scheduling workflow generation method in the embodiment, and the like. Further, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are to be output.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different from that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications that can be made by the use of the equivalent structures or equivalent processes in the specification and drawings of the present application or that can be directly or indirectly applied to other related technologies are also included in the scope of the present application.
Claims (10)
1. A system scheduling workflow generation method, the method comprising:
providing a configuration interface for a user to configure each service module required to be called for realizing financial services, parameters of each service module and a connection relation between each service module;
after the user finishes configuration operation, generating a configuration file for realizing financial service according to the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial service, parameter configuration information of each service module and a connection relation between each service module; and
converting the configuration file into an XML file executable by a workflow engine, wherein the parameter configuration information comprises the calling type information of each service module, and the converting the configuration file into the XML file executable by the workflow engine comprises the following steps:
converting each service module to be called into a corresponding flow activity node according to the calling type information of each service module, wherein the flow activity node is an executable XML fragment;
adding the parameter configuration information of each service module except the calling type information into the process activity node;
and connecting the obtained flow activity nodes in series according to the connection relation to obtain a final executable XML file.
2. The method according to claim 1, wherein the call type information includes a synchronous interface call and an asynchronous interface call, and the converting each service module to be called into a corresponding flow activity node according to the call type information of each service module includes:
if the calling type of the service module needing to be called currently is synchronous interface calling, converting the service module needing to be called currently into an atomic flow active node;
if the calling type of the service module needing to be called currently is asynchronous interface calling, the service module needing to be called currently is converted into three atomic flow activity nodes, namely a calling flow activity node, a waiting callback flow activity node and a callback result processing flow activity node.
3. The method for generating a system scheduling workflow according to claim 1, wherein after the step of converting each service module to be called into a corresponding process activity node according to the call type information of each service module, the method further comprises:
and adding transaction rollback operation which needs to be executed when calling each service module fails in the process activity node.
4. The method according to claim 1, wherein the parameter configuration information includes logic judgment information, and after the step of converting each service module to be called into a corresponding flow activity node according to the call type information of each service module, the method further includes:
and generating a branch judgment condition according to the logic judgment information, and adding the branch judgment condition to the flow activity node.
5. The method according to claim 1, wherein the parameter configuration information includes timeout processing information, and after the step of converting each service module to be called into a corresponding flow activity node according to the call type information of each service module, the method further includes:
and generating a timing task according to the overtime processing information, and adding the timing task to the flow activity node.
6. The method for generating a system scheduling workflow according to any one of claims 1 to 5, wherein the step of concatenating the obtained flow activity nodes according to the connection relationship to obtain a final executable XML file comprises:
dividing each obtained process activity node into a plurality of groups of process activity node pairs to be connected according to the connection relation, wherein each group of process activity node pairs comprises a source node and a target node;
and connecting the source node in each group of process active node pairs to the target node through a preset function.
7. The method according to claim 6, wherein the preset functions are SourceRef function and TargetRef function.
8. A system scheduling workflow generation apparatus, comprising:
the system comprises a providing module, a connecting module and a processing module, wherein the providing module is used for providing a configuration interface for a user to configure each service module required to be called for realizing financial service, parameters of each service module and the connection relation among the service modules;
the generating module is used for generating a configuration file for realizing financial services according to the configuration operation after the user finishes the configuration operation, wherein the configuration file comprises each service module required to be called for realizing the financial services, parameter configuration information of each service module and a connection relation between each service module; and
the conversion module is used for converting the configuration file into an XML file which can be executed by a workflow engine, wherein the parameter configuration information comprises the calling type information of each business module, and the conversion module is also used for converting each business module to be called into a corresponding flow activity node according to the calling type information of each business module, wherein the flow activity node is an executable XML fragment; adding the parameter configuration information of each service module except the calling type information into the process activity node; and connecting the obtained flow activity nodes in series according to the connection relation to obtain a final executable XML file.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program is configured to implement the steps of the system scheduling workflow generation method of any one of claims 1 to 7.
10. A computer readable storage medium having stored therein a computer program executable by at least one processor to cause the at least one processor to perform the steps of the system scheduling workflow generation method of any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010027930.1A CN111208992A (en) | 2020-01-10 | 2020-01-10 | System scheduling workflow generation method and system |
| PCT/CN2021/070904 WO2021139778A1 (en) | 2020-01-10 | 2021-01-08 | System scheduling workflow generation method, system, apparatus, and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010027930.1A CN111208992A (en) | 2020-01-10 | 2020-01-10 | System scheduling workflow generation method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111208992A true CN111208992A (en) | 2020-05-29 |
Family
ID=70786065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010027930.1A Withdrawn CN111208992A (en) | 2020-01-10 | 2020-01-10 | System scheduling workflow generation method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111208992A (en) |
| WO (1) | WO2021139778A1 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708545A (en) * | 2020-06-17 | 2020-09-25 | 北京同邦卓益科技有限公司 | Business process deployment method and device, electronic equipment and storage medium |
| CN112035367A (en) * | 2020-09-02 | 2020-12-04 | 中国银行股份有限公司 | Method and system for verifying correctness of workflow of big data platform |
| CN112148353A (en) * | 2020-09-22 | 2020-12-29 | 京东数字科技控股股份有限公司 | Data processing method and device |
| WO2021139778A1 (en) * | 2020-01-10 | 2021-07-15 | 深圳壹账通智能科技有限公司 | System scheduling workflow generation method, system, apparatus, and computer readable storage medium |
| CN113239670A (en) * | 2021-05-11 | 2021-08-10 | 鸬鹚科技(深圳)有限公司 | Method and device for uploading service template, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102314349A (en) * | 2011-09-16 | 2012-01-11 | 武汉中地数码科技有限公司 | Spatial information functional plug-in workflow construction method |
| CN103617066A (en) * | 2013-12-16 | 2014-03-05 | 中国农业银行股份有限公司 | Workflow engine and implementation method thereof |
| CN109636301A (en) * | 2018-10-16 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Workflow configuration method, system, terminal and the readable storage medium storing program for executing of financial business |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1625499A2 (en) * | 2003-05-16 | 2006-02-15 | Sap Ag | Business process management for a message-based exchange infrastructure |
| CN108255467A (en) * | 2016-12-27 | 2018-07-06 | 北京京东尚科信息技术有限公司 | The method, apparatus and system of service are performed according to workflow sequence |
| CN110428216A (en) * | 2019-07-03 | 2019-11-08 | 平安科技（深圳）有限公司 | Operation flow management-control method, device, computer equipment and storage medium |
| CN111208992A (en) * | 2020-01-10 | 2020-05-29 | 深圳壹账通智能科技有限公司 | System scheduling workflow generation method and system |
-
2020
- 2020-01-10 CN CN202010027930.1A patent/CN111208992A/en not_active Withdrawn
-
2021
- 2021-01-08 WO PCT/CN2021/070904 patent/WO2021139778A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102314349A (en) * | 2011-09-16 | 2012-01-11 | 武汉中地数码科技有限公司 | Spatial information functional plug-in workflow construction method |
| CN103617066A (en) * | 2013-12-16 | 2014-03-05 | 中国农业银行股份有限公司 | Workflow engine and implementation method thereof |
| CN109636301A (en) * | 2018-10-16 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Workflow configuration method, system, terminal and the readable storage medium storing program for executing of financial business |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021139778A1 (en) * | 2020-01-10 | 2021-07-15 | 深圳壹账通智能科技有限公司 | System scheduling workflow generation method, system, apparatus, and computer readable storage medium |
| CN111708545A (en) * | 2020-06-17 | 2020-09-25 | 北京同邦卓益科技有限公司 | Business process deployment method and device, electronic equipment and storage medium |
| CN111708545B (en) * | 2020-06-17 | 2023-09-22 | 北京同邦卓益科技有限公司 | Service flow deployment method and device, electronic equipment and storage medium |
| CN112035367A (en) * | 2020-09-02 | 2020-12-04 | 中国银行股份有限公司 | Method and system for verifying correctness of workflow of big data platform |
| CN112035367B (en) * | 2020-09-02 | 2023-08-18 | 中国银行股份有限公司 | Method and system for checking workflow correctness of big data platform |
| CN112148353A (en) * | 2020-09-22 | 2020-12-29 | 京东数字科技控股股份有限公司 | Data processing method and device |
| CN113239670A (en) * | 2021-05-11 | 2021-08-10 | 鸬鹚科技(深圳)有限公司 | Method and device for uploading service template, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021139778A1 (en) | 2021-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111208992A (en) | System scheduling workflow generation method and system | |
| CN102456185B (en) | Distributed workflow processing method and distributed workflow engine system | |
| CN108733476A (en) | A kind of method and apparatus executing multitask | |
| US8538793B2 (en) | System and method for managing real-time batch workflows | |
| CN109684057A (en) | Task processing method, device and storage medium | |
| CN110471746B (en) | Distributed transaction callback method, device and system | |
| US20100121904A1 (en) | Resource reservations in a multiprocessor computing environment | |
| CN104077362A (en) | Online mass data processing system and method | |
| CN110163572B (en) | Chain code function processing method, device and equipment | |
| CN110611707A (en) | Task scheduling method and device | |
| CN115860451A (en) | Flow operation method and device, electronic equipment and storage medium | |
| CN115544044A (en) | Data consistency keeping method, device, equipment and storage medium | |
| CN111897799A (en) | Hydrological model service system based on process engine | |
| CN116069300A (en) | Workflow control code generation method and device, electronic equipment and storage medium | |
| CN114816694A (en) | Multi-process cooperative RPA task scheduling method and device | |
| US20100122261A1 (en) | Application level placement scheduler in a multiprocessor computing environment | |
| CN115801882A (en) | Information interaction method and device between old line system and micro-service system | |
| CN111736930B (en) | Program front-back end interface calling method and device, computer equipment and storage medium | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
| CN114237634A (en) | Application release risk identification method, device, equipment, medium and program product | |
| CN115048158A (en) | Process arranging and calling method, system and computer equipment thereof | |
| US20100122254A1 (en) | Batch and application scheduler interface layer in a multiprocessor computing environment | |
| CN110018906B (en) | Scheduling method, server and scheduling system | |
| CN117112149B (en) | Mining area mine business process communication method, device, medium and equipment | |
| CN117807030A (en) | Batch data processing method, device and equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200529 |
|
| WW01 | Invention patent application withdrawn after publication |