CN112070452A - Distributed workflow management system - Google Patents
Distributed workflow management system Download PDFInfo
- Publication number
- CN112070452A CN112070452A CN202010687815.7A CN202010687815A CN112070452A CN 112070452 A CN112070452 A CN 112070452A CN 202010687815 A CN202010687815 A CN 202010687815A CN 112070452 A CN112070452 A CN 112070452A
- Authority
- CN
- China
- Prior art keywords
- workflow
- subsystem
- distributed
- interface
- application
- 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.)
- Pending
Links
- 230000010354 integration Effects 0.000 claims abstract description 50
- 238000012544 monitoring process Methods 0.000 claims abstract description 10
- 238000002955 isolation Methods 0.000 claims description 5
- 238000013461 design Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 11
- 238000012545 processing Methods 0.000 abstract description 8
- 230000000007 visual effect Effects 0.000 abstract description 7
- 238000007726 management method Methods 0.000 description 55
- 238000000034 method Methods 0.000 description 19
- 230000008569 process Effects 0.000 description 14
- 238000003860 storage Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000005067 remediation Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the field of distributed technology, in particular to a distributed workflow management system, which comprises: the workflow control subsystem is used for configuring, managing and monitoring the workflow; a workflow application integration subsystem for providing an interface for integrating workflow applications into the distributed workflow management system, wherein the interface comprises a data integration interface and a workflow operation integration interface; and the workflow engine subsystem is used for executing and controlling the workflow created by the user. The independently deployed workflow control subsystem, the workflow application integration subsystem and the workflow engine subsystem form a distributed workflow system by utilizing a distributed database and a distributed message queue through a network, thereby improving the expandability and the parallel processing capability of the system, and providing the visual workflow definition function based on a workflow template, the parallel execution and monitoring of the workflow and the continuous integration capability of the workflow application.
Description
Technical Field
The invention relates to the field of distributed technology, in particular to a distributed workflow management system.
Background
A workflow is a type of business process that can be fully or partially automated, and documents, information, or tasks can be passed and executed between different executives according to a set of process rules. The workflow originates from the fields of production organizations (such as factories and enterprises) and Office Automation (OA), is mainly proposed for activities with fixed programs in daily life and work, and aims to decompose a task with a certain execution flow into a series of well-defined actions, execute the actions according to certain rules and processes and monitor the actions, so that the production efficiency is improved, the production cost is reduced, and the production, operation and management level and the enterprise competitiveness of an enterprise are improved.
However, the existing workflow technologies and products require a single working environment, are difficult to support complex distributed enterprise-level applications, and obviously have insufficient integration capability for various applications of existing enterprises, especially the workflow model has insufficient description capability and inflexible and rich definition of task attributes, so that a workflow management system supporting complex and distributed enterprise-level applications and application integration will be paid full attention and developed greatly.
Disclosure of Invention
The invention aims to provide a distributed workflow management system, wherein an independently deployed workflow management subsystem, a workflow application integration subsystem and a workflow engine subsystem form the distributed workflow system through a network and by utilizing a distributed database and a distributed message queue, and provide the capabilities of a workflow template for carrying out visual workflow definition function, workflow parallel execution and monitoring and workflow application continuous integration.
The invention provides a distributed workflow management system, comprising:
the workflow control subsystem is used for configuring, managing and monitoring the workflow;
a workflow application integration subsystem for providing an interface for integrating workflow applications into the distributed workflow management system, wherein the interface comprises a data integration interface and a workflow operation integration interface;
and the workflow engine subsystem is used for executing and controlling the workflow created by the user.
Optionally, the workflow management subsystem is further configured to provide design and management of a visualized workflow template.
Optionally, the data integration interface includes a basic data integration interface, which is used to keep the data of each subsystem of the system consistent.
Optionally, the workflow operation integration interface is configured to register a user-defined workflow application with the system, where the workflow application includes a plurality of workflow operations and interfaces corresponding to the workflow operations for invocation.
Optionally, the workflow engine subsystem is configured to execute and control a workflow created by a user, and includes:
acquiring an instruction of a user for creating a workflow;
calling a corresponding workflow application and an interface corresponding to the workflow application to create a workflow according to the instruction for creating the workflow;
controlling execution of the workflow.
Optionally, when the workflow engine subsystem acquires that the workflow instruction is a plurality of instructions, dynamically allocating a thread to each instruction and performing thread isolation.
Optionally, the workflow control subsystem, the workflow application integration subsystem and the workflow engine subsystem of the system are deployed independently and form a distributed system through a network.
Optionally, the system decouples and asynchronizes the workflow application through a distributed message queue.
Optionally, the system further includes a workflow client and a proxy gateway for workflow load balancing.
Optionally, the system uses a distributed database for data access.
Compared with the prior art, the distributed workflow management system provided by the invention at least has the following beneficial effects:
the distributed workflow management system provided by the invention comprises a workflow management subsystem, a workflow application integration subsystem and a workflow engine subsystem which are independently deployed, wherein the distributed workflow system is formed by utilizing a distributed database and a distributed message queue through a network, the expandability and the parallel processing capability of the system are improved, and the visual workflow definition function, the workflow parallel execution and monitoring and the continuous integration capability of workflow application based on a workflow template are provided.
Drawings
The invention will be described in more detail hereinafter on the basis of embodiments and with reference to the accompanying drawings.
Fig. 1 is a distributed workflow management system according to an embodiment of the present invention.
Fig. 2 is a logic architecture diagram of a distributed workflow management system according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of a basic structure of a computer device for deploying subsystems of the distributed workflow management system according to an embodiment of the present invention.
In the drawings, like parts are designated with like reference numerals, and the drawings are not drawn to scale.
Reference numerals:
300-a computer device; 310-a memory; 320-a processor; 330-network interface.
Detailed Description
The following detailed description of the embodiments of the present invention will be provided with reference to the accompanying drawings and examples, so that how to apply the technical means to solve the technical problems and achieve the corresponding technical effects can be fully understood and implemented. It should be noted that all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The embodiments and the features of the embodiments can be combined without conflict, and the technical solutions formed are all within the scope of the present invention.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a distributed workflow management system according to an embodiment of the present invention, where the distributed workflow management system 100 includes a workflow management subsystem 110, a workflow application integration subsystem 120, and a workflow engine subsystem 130, where:
and a workflow control subsystem 110 for configuring, managing and monitoring the workflow.
Specifically, the workflow management subsystem 110 is mainly directed to a person performing workflow management and a super manager having all rights of the subsystem, through the workflow management subsystem 110, the super manager can increase or decrease the workflow management person, assign user rights, manage the configuration of the subsystem (such as network configuration and database management), and the like, the workflow management person can configure, manage and monitor the workflow, including workflow classification management (such as procurement process, dispatching process, and the like), workflow service configuration, workflow remediation, workflow template configuration management, instruction management (including instantiation instruction management, execution instruction management, callback instruction management, event instruction management), and the like, wherein the configuration management of the workflow template adopts a visual template design component provided by the workflow management subsystem 110, the workflow management personnel can form different workflow templates and release the templates by dragging different visual components, convenience is provided for different business process modeling, meanwhile, the versions of the templates can be uniformly managed, the templates can be conveniently switched by the business personnel at any time, a user can preview the trend of the process according to the process templates, different workflow templates are formed and the templates are released to form a common template, then the business process can be uniformly managed, and meanwhile, the process flexibility is realized. In addition, the workflow control subsystem 110 also provides a flow monitoring function to help a user to timely intervene on an abnormal workflow instance; for a normally running workflow instance, the user may also modify, e.g., modify participants, add activities, etc.
Further, the workflow management subsystem 110 provides visualized flow template design and configuration management, and the visualization adopts HTML5 (hypertext markup language) and SVG (scalable vector graphics) technologies, and can obtain support of a wide range of operating systems and hardware; the system comprises a client, a server, a client, a server, a; the SVG technology can realize convenient graphic positioning and retrieval, and has rich expression effect, good reusability, accurate color description, cross-platform capability and the like.
A workflow application integration subsystem 120 for providing an interface for integrating workflow applications into the distributed workflow management system, wherein the interface comprises a data integration interface and a workflow operation integration interface.
Wherein the data integration interface comprises a basic data integration interface used for keeping the data of each subsystem of the system consistent.
The workflow operation integration interface is used for registering a user-defined workflow application to the system, wherein the workflow application comprises a plurality of workflow operations and interfaces corresponding to the workflow operations for calling.
Specifically, the data integration interface and the workflow operation integration interface are programs formulated by the workflow application integration subsystem 120, and the workflow application must comply with the standard of the interface to integrate the data and the developed workflow application program into the workflow management system 100, so that the system can use the data and call the program to implement the corresponding operation. The data integration interface includes a basic data integration interface standard for data integration of a basic user, an organization, a role, a post, and the like, and other optional integration standards such as a participant service, a reference item service, and the like, the basic data integration interface is a basis for integrating the workflow management system with a workflow application, and the workflow application needs to implement the standard of the integration interface in the form of Restful (representational state transfer), WebService (Web service), and Hassion (a remote method invocation framework), such as a data format standard, a data type standard, and the like, so as to achieve the consistency and synchronous update of data of each subsystem of the distributed workflow management system 100. The workflow operation integration interface is used for helping a user with workflow application development to register to the system 100 according to operations contained in the workflow application defined by the interface standard, and providing other workflow applications of the system 100 for calling in a Restful manner, so as to complete relevant operations, including basic passing, returning and other operations, and other optional returning, collaborative review, distribution, completion and other operations, thereby promoting the operation of workflow process instances. Through the unified workflow application integration interface standard provided by the workflow application integration subsystem 120, the workflow application can be quickly and continuously integrated and upgraded, the system maintenance cost is reduced, and the system expandability is improved.
A workflow engine subsystem 130 for executing and controlling user-created workflows, comprising:
acquiring an instruction of a user for creating a workflow;
calling a corresponding workflow application and an interface corresponding to the workflow application to create a workflow according to the instruction for creating the workflow;
controlling execution of the workflow.
Specifically, please refer to fig. 2, fig. 2 is a logic architecture diagram of the distributed workflow management system 100, wherein the workflow engine subsystem 130 is a core subsystem of the system 100, and is mainly configured to receive a workflow instruction that a user defines a workflow template through the workflow management subsystem 110 and creates based on the workflow template, then call a corresponding workflow application and an interface corresponding to the workflow application according to the workflow instruction to create a workflow, and execute the workflow, and the operation interface may include initiating a workflow and instantiating, sub-flow associating and instantiating, execution mode control (sequential execution, parallel execution, election execution, etc.), control of different types of participants, execution path rule determination, execution of tasks to be handled, and the like, and monitoring and statistical analysis of the flow execution. In addition, the workflow engine subsystem 130 provides a visualized webpage designed based on HTML5 and related front-end technologies (such as css, jquery, boottrap, Ajax/Json components, etc.), and a webpage client combining technologies such as Spring, SpringMVC, MyBatis, queue components, etc. at the back end, so that a workflow participant can conveniently perform workflow operations through the visualized webpage.
For example, for a purchase job, the job participants include a buyer, a finance person, an auditor, and a warehouse manager, the buyer can first obtain a flow template of the purchase workflow from the workflow management subsystem 110 through a web client of the workflow engine subsystem 130 (a user can also define the template by himself/herself to the workflow subsystem 110), and then initiate a corresponding workflow creation instruction, the workflow engine subsystem 130 invokes an operation interface program corresponding to the workflow application to create a workflow according to the workflow application configured by the instruction, and executes the workflow, thereby implementing changes of the tasks such as circulation, approval, return, completion, even flow, and participants of the buyer, the finance person, the auditor, and the warehouse manager. It should be noted that the workflow engine subsystem 130 may process a plurality of workflows simultaneously and in parallel, data and execution processes of the respective workflow operations are independent from each other, and a user may improve a speed of the client operation by using an asynchronous manner through interaction between the web client and the system.
Further, when the workflow engine subsystem acquires that the workflow instruction is a plurality of instructions, threads are dynamically allocated to each instruction and thread isolation is performed.
Specifically, when a plurality of users initiate workflow creation at the same time or one user initiates a plurality of workflow applications, the workflow engine subsystem 130 may obtain a plurality of workflow instructions, and in order to avoid a situation that "dirty data" occurs due to data confusion of each workflow operation, the workflow engine subsystem 130 dynamically allocates a thread to each instruction and performs thread isolation by using a multithread isolation technique, that is: when the workflow is started, a thread is created for the workflow, a starting identifier is set and is bound with the current workflow thread through a thread number, then the starting identifier is stored in a database, when other operations are executed in the workflow next time, the starting identifier bound with the thread is obtained from the database, so that the operation is guaranteed to be executed on the thread with the appointed starting identifier, the starting, the approval and the circulation of the same workflow can be guaranteed to be sequentially executed on the same thread, a plurality of workflows are executed on different threads, and data in respective threads are operated, so that 'dirty data' is effectively prevented from being generated.
Further, the workflow control subsystem 110, the workflow application integration subsystem 120, and the workflow engine subsystem 130 of the system 100 are deployed independently and form a distributed system through a network, so as to provide corresponding services for different types of users.
Specifically, the workflow management subsystem 110, the workflow application integration subsystem 120, and the workflow engine subsystem 130 of the system 100 can be deployed on different computer devices (including but not limited to servers, workstations, PC computers, etc.), and communicate through wired network (such as Ethernet) or wireless network (such as WIFI, ZIGBEE, 5G, etc.), each subsystem can be called through remote interface to form a distributed workflow system, provide corresponding different services for different user types, for example, a workflow manager can manage workflows and operations on flow templates through the workflow management subsystem 110, a general user can visually create and control workflows through the workflow engine subsystem 130, and a development user can perform development testing of applications according to interface standards and integration into the system through the workflow application integration subsystem 120.
Further, the system decouples and asynchronizes the workflow application through a distributed message queue.
The distributed message queue is a distributed message publishing-subscribing system, which contains data that can be recognized by both data consumers and data producers, and the data needs to be transferred between different systems (devices), and may be subscribed and consumed by a plurality of completely different clients. For an enterprise application system with a plurality of subsystems, a large amount of data interaction needs to be carried out among the subsystems, a traditional mode of directly calling a data interface to obtain data cannot meet a large amount of real-time data requests, a large-scale distributed system usually uses a distributed message queue as a middleware for data transmission, has better platform independence, can run on different operating systems, and can well support concurrency and asynchronization. For example, in this embodiment, when the workflow management subsystem 110 of the workflow management system 100 defines and issues a workflow template to the distributed message queue, the workflow engine subsystem 130 may obtain the template by subscribing to the message, so as to be used by the user; for another example, when executing a workflow application, the workflow engine subsystem 130 may decouple related operations of the workflow through the message queue, so that the operations are notified to each other through messages, and the operations of initiating, circulating, canceling, and the like of the workflow are completed. The distributed message queues are utilized to enable workflow applications to be decoupled and asynchronous between the systems 100, thereby improving system efficiency.
Further, as shown in fig. 1, the system 100 further includes a workflow client 140 and a proxy gateway for workflow load balancing.
Specifically, the workflow client 140 is a visual web page designed by HTML5, SVG and related front-end technologies (such as css, jquery, boottrap, Ajax/Json components, etc.), and data related to workflow and system configuration is stored in a Spring, SpringMVC, MyBatis and queue components, and databases such as MySql, REDIS, etc., which are combined with a back-end to perform business logic processing. By adopting the universal HTML5 and SVG technologies, the method can obtain the support of a wide operating system and hardware, so that the workflow client 140 can be conveniently transplanted. In addition, for a large number of workflow application requests from the workflow client 140, a large number of requests can be reversely proxied to the workflow management system 100 through an API (application program interface) of the proxy gateway for distributed processing to realize load balancing, so that the concurrent processing capability of the system 100 is improved, and the system can obtain the support, self-making and high availability in a distributed environment of different operating systems through a Docker mirroring technology.
Further, the system adopts a distributed database for data access.
The distributed database is a logically unified database formed by connecting a plurality of physically distributed data storage units by using a high-speed computer network, and the basic idea is to store data in an original centralized database to a plurality of data storage nodes connected through a network in a distributed manner so as to obtain larger storage capacity and higher concurrent access amount. Specifically, the distributed workflow management system 100 utilizes the distributed database technology, and can perform database partitioning and table sorting on the databases related to the workflow according to the workflow service to different subsystems, and evenly distribute the operations of data access, rollback, transaction and the like to different database nodes, thereby effectively dispersing the high concurrent pressure of the system and improving the throughput of the system. The database may be MySql, REDIS, Oracle, etc.
Referring to fig. 3, fig. 3 is a block diagram of a basic structure of a computer device for deploying subsystems of the distributed workflow management system 100 in this embodiment, where the computer device 300 may include a memory 310 and a processor 320, where the memory 310 stores a computer program corresponding to the subsystems of the system, and the processor 320 can implement functions of the corresponding subsystems when executing the computer program, so as to bring corresponding beneficial effects, and details are not described here to avoid repetition.
With continued reference to FIG. 3, the computer device 300 includes a memory 310, a processor 320, and a network interface 330 communicatively coupled to each other via a system bus. It is noted that only a computer device 300 having a component memory 310, a processor 320, and a network interface 330 is shown, but it is understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead. As will be understood by those skilled in the art, the computer device is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.
The computing device 300 may be a desktop computer, a notebook, a palm computer, a cloud server, a workstation, or other computing devices. The computer equipment can carry out man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch panel or voice control equipment and the like.
The memory 310 includes at least one type of 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 310 may be an internal storage unit of the computer device 300, such as a hard disk or a memory of the computer device 300. In other embodiments, the memory 310 may also be an external storage device of the computer device 300, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 300. Of course, the memory 310 may also include both internal and external storage devices of the computer device 300. In this embodiment, the memory 310 is generally used for storing an operating system, various application software and the like installed on the computer device 300. In addition, the memory 310 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 320 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 320 is generally operative to control overall operation of the computer device 300. In this embodiment, the processor 320 is configured to run program codes stored in the memory 310 or process data, for example, program codes of subsystems of the distributed workflow management system.
The network interface 330 may include a wireless network interface or a wired network interface, and the network interface 330 is generally used to establish a communication connection between the computer device 300 and other electronic devices, so as to realize the interaction of the subsystems of the distributed workflow management system.
In summary, the distributed workflow management system provided by the present invention includes an independently deployed workflow management subsystem, a workflow application integration subsystem, and a workflow engine subsystem, which form a distributed workflow system through a network and by using a distributed database and a distributed message queue, thereby improving the expandability and parallel processing capability of the system, and providing the visual workflow definition function based on a workflow template, the capability of workflow parallel execution and monitoring, and the capability of workflow application continuous integration.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the invention has been described with reference to a preferred embodiment, various modifications may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In particular, the technical features mentioned in the embodiments can be combined in any way as long as there is no structural conflict. It is intended that the invention not be limited to the particular embodiments disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.
Claims (10)
1. A distributed workflow management system, comprising:
the workflow control subsystem is used for configuring, managing and monitoring the workflow;
a workflow application integration subsystem for providing an interface for integrating workflow applications into the distributed workflow management system, wherein the interface comprises a data integration interface and a workflow operation integration interface;
and the workflow engine subsystem is used for executing and controlling the workflow created by the user.
2. The system of claim 1, wherein the workflow management subsystem is further configured to provide design and management of visualized workflow templates.
3. The system of claim 1, wherein the data integration interface comprises a base data integration interface for maintaining consistent subsystem data for the system.
4. The system of claim 3, wherein the workflow operation integration interface is configured to register a user-defined workflow application with the system, wherein the workflow application comprises a plurality of workflow operations and interfaces corresponding to the workflow operations for invocation.
5. The system of claim 4, wherein the workflow engine subsystem for executing and controlling user-created workflows comprises:
acquiring an instruction of a user for creating a workflow;
calling a corresponding workflow application and an interface corresponding to the workflow application to create a workflow according to the instruction for creating the workflow;
controlling execution of the workflow.
6. The system of claim 5, wherein when the workflow engine subsystem obtains that the workflow instruction is a plurality of instructions, dynamically assigning a thread to each instruction and performing thread isolation.
7. The system of claim 6, wherein the workflow management subsystem, the workflow application integration subsystem and the workflow engine subsystem of the system are deployed independently and form a distributed system through a network.
8. The system of claim 7, wherein the system decouples and asynchronizes the workflow application through a distributed message queue.
9. The system of claim 8, further comprising a workflow client and a proxy gateway for workflow load balancing.
10. The system of claim 9, wherein the system employs a distributed database for data access.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010687815.7A CN112070452A (en) | 2020-07-16 | 2020-07-16 | Distributed workflow management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010687815.7A CN112070452A (en) | 2020-07-16 | 2020-07-16 | Distributed workflow management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112070452A true CN112070452A (en) | 2020-12-11 |
Family
ID=73657413
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010687815.7A Pending CN112070452A (en) | 2020-07-16 | 2020-07-16 | Distributed workflow management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112070452A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112596865A (en) * | 2020-12-22 | 2021-04-02 | 航天信息股份有限公司企业服务分公司 | System for pushing to-do message based on workflow affair |
| CN112700219A (en) * | 2020-12-31 | 2021-04-23 | 宝付网络科技（上海）有限公司 | ACTIVITI-based process management platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101576978A (en) * | 2009-06-16 | 2009-11-11 | 北京环太中科软件股份有限公司 | Formulating method, implementing method and implementing system of distribution type workflow |
| CN101694709A (en) * | 2009-09-27 | 2010-04-14 | 华中科技大学 | Service-oriented distributed work flow management system |
| CN102456185A (en) * | 2010-10-29 | 2012-05-16 | 金蝶软件（中国）有限公司 | Distributed workflow processing method and distributed workflow engine system |
| CN102663569A (en) * | 2012-05-07 | 2012-09-12 | 广东优迈信息通信技术有限公司 | Visualized workflow engine system |
| CN107423952A (en) * | 2017-07-25 | 2017-12-01 | 苏州博纳讯动软件有限公司 | A kind of expansible DevOps continues delivery system and its method |
| CN109858817A (en) * | 2019-02-03 | 2019-06-07 | 北京奇艺世纪科技有限公司 | A kind of Workflow Management System and method |
-
2020
- 2020-07-16 CN CN202010687815.7A patent/CN112070452A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101576978A (en) * | 2009-06-16 | 2009-11-11 | 北京环太中科软件股份有限公司 | Formulating method, implementing method and implementing system of distribution type workflow |
| CN101694709A (en) * | 2009-09-27 | 2010-04-14 | 华中科技大学 | Service-oriented distributed work flow management system |
| CN102456185A (en) * | 2010-10-29 | 2012-05-16 | 金蝶软件（中国）有限公司 | Distributed workflow processing method and distributed workflow engine system |
| CN102663569A (en) * | 2012-05-07 | 2012-09-12 | 广东优迈信息通信技术有限公司 | Visualized workflow engine system |
| CN107423952A (en) * | 2017-07-25 | 2017-12-01 | 苏州博纳讯动软件有限公司 | A kind of expansible DevOps continues delivery system and its method |
| CN109858817A (en) * | 2019-02-03 | 2019-06-07 | 北京奇艺世纪科技有限公司 | A kind of Workflow Management System and method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112596865A (en) * | 2020-12-22 | 2021-04-02 | 航天信息股份有限公司企业服务分公司 | System for pushing to-do message based on workflow affair |
| CN112700219A (en) * | 2020-12-31 | 2021-04-23 | 宝付网络科技（上海）有限公司 | ACTIVITI-based process management platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102375731B (en) | Coding-free integrated application platform system | |
| US10146599B2 (en) | System and method for a generic actor system container application | |
| US20210146537A1 (en) | Scheduling robots for robotic process automation | |
| CN113010598B (en) | Dynamic self-adaptive distributed cooperative workflow system for remote sensing big data processing | |
| CN112070452A (en) | Distributed workflow management system | |
| CN112256406B (en) | Operation flow platformization scheduling method | |
| Wei et al. | Product platform architecture for cloud manufacturing | |
| CN113282795A (en) | Data structure chart generating and updating method and device, electronic equipment and storage medium | |
| US10210284B2 (en) | Method and system for managing data in a manufacturing execution system | |
| CN111144830A (en) | Enterprise-level computing resource management method, system and computer equipment | |
| CN114579469A (en) | Full link interface test method and device, electronic equipment and storage medium | |
| CN113626163A (en) | Lightweight distributed increment self-scheduling method, system, equipment and medium | |
| Liu et al. | Gird manufacturing: a new solution for cross-enterprise collaboration | |
| Chao et al. | Multi-agent-based cloud utilization for the IT office-aid asset distribution chain: An empirical case study | |
| Huang et al. | A survey of cloud workflow | |
| CN115617480A (en) | Task scheduling method, device and system and storage medium | |
| US10417051B2 (en) | Synchronizing shared resources in an order processing environment using a synchronization component | |
| CN111415129A (en) | Workflow platform and terminal equipment with same | |
| CN107018160B (en) | Manufacturing resource and clouding method based on layering | |
| CN114138758A (en) | Data cleaning and merging method and device based on multi-source system and readable medium | |
| Zhang et al. | Research on it operation and maintenance and management and maintenance methods in cloud computing environment | |
| US20200293977A1 (en) | System and method for concurrent processing of work items | |
| JP2021125264A (en) | Information processing device | |
| CN112667759A (en) | Space management method and system based on visual map and electronic equipment | |
| Gudenkauf et al. | Features of Event-Driven Message Queuing Architectures in Manufacturing: A Reference Model for Comparison |
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 |