CN115185496A - Service arrangement method based on Flowable workflow engine - Google Patents
Service arrangement method based on Flowable workflow engine Download PDFInfo
- Publication number
- CN115185496A CN115185496A CN202210872404.4A CN202210872404A CN115185496A CN 115185496 A CN115185496 A CN 115185496A CN 202210872404 A CN202210872404 A CN 202210872404A CN 115185496 A CN115185496 A CN 115185496A
- Authority
- CN
- China
- Prior art keywords
- component
- flowable
- workflow engine
- business
- flow
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- 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/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a service arrangement method based on a Flowable workflow engine, which is characterized in that a preset assembly splicing rule is adopted; configuring the assembly splicing rule in a Flowable workflow engine; arranging a business process and constructing a business process model in the Flowable workflow engine based on the component splicing rule; and storing and releasing the business process model. Various business logics can be arranged through the workflow engine, and the data isolated island condition of complex services and interfaces can be dealt with. The business logic can be abstracted into the components, the public capacity of the business can be multiplexed, the circulation process of the business is abstracted into the flow, and the business logic is arranged in a visual configuration mode through arranging various components, so that the development cost of an enterprise is greatly reduced, and the development difficulty is reduced.
Description
Technical Field
The present disclosure relates to the field of application development technologies, and in particular, to a method, an apparatus, and a system for orchestrating a service based on a Flowable workflow engine.
Background
With the increase of business complexity and scale of enterprises, developers of the enterprises can continuously carry out complicated development processes such as code development, project reconstruction and the like on newly added needs and pain points of the business.
In the prior art, the business arrangement technology mostly adopts micro-services or cloud functions for arrangement, and usually a large number of stateless logic arrangement components are applied for business arrangement and development. The typical scheme is that the service arrangement logic of an ivx code-free development platform is formed by logic applications such as [ trigger event ] + [ precondition ] + [ target object ] + [ execute action ] + [ action parameter ], although the logic application can be freely scheduled and used, the integration level of a distributed application system is low, and the following technical problems also exist:
1. the implementer needs to have certain professional ability, needs to know the BPMN2.0 protocol and the using mode of each component of the workflow engine, and can functionally understand the using purpose of each component and even the service process. Therefore, the technical requirement is difficult, and the limitation on personnel is high.
2. Meanwhile, the implementing personnel need to know the related business capability, so that a proper interface can be configured on the node, which also brings development difficulty and increases time, labor and material cost for business arrangement and development of enterprises.
Disclosure of Invention
In order to solve the above problems, the present application provides a method, an apparatus, and a system for orchestrating a service based on a Flowable workflow engine.
On one hand, the application provides a service arrangement method based on a Flowable workflow engine, which comprises the following steps:
presetting a component splicing rule;
configuring the assembly splicing rule in a Flowable workflow engine;
in the Flowable workflow engine, arranging a business process based on the assembly splicing rule, and constructing a business process model;
and storing and releasing the business process model.
As an optional embodiment of the present application, optionally, the component splicing rule includes:
ensuring that a starting component in the Flowable workflow engine meets the following rules: the flow takes a starting component as a starting node, and the starting component only has an output stream; wherein the starting component comprises at least one of an empty starting component, a timed starting component or a signal starting component;
ensuring that an ending component in the Flowable workflow engine meets the following rules: the flow must take the ending component as the ending node, and the ending component has only input stream; wherein the ending component comprises at least one of an empty ending component or a signal ending component.
As an optional embodiment of the present application, optionally, the component splicing rule further includes:
ensuring that the sequential flow in the Flowable workflow engine meets the following rules: in addition to sequential flow, all flows between components must be connected by sequential flow;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the exclusive gateway has only one input stream, and at least two or more output streams are required;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the gateway has only one output stream, and at least two or more input streams are required.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method includes:
presetting a flow building rule;
building a business process node through the Flowable workflow engine based on the process building rule;
and establishing and generating a flow model according to the established business flow nodes, and storing the flow model into a preset database.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
configuring the Flowable workflow engine in a workflow graphic console provided in an instruction set OS;
preparing a visual business arrangement flow through a visual configuration interface of the workflow graphic console;
and operating the functional components configured in the Flowable workflow engine based on the component splicing rule, and arranging a service flow.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
presetting a service calling component;
configuring a process variable in the service calling component, and configuring the service calling component on a designated node in the process model;
and the service calling component is used for receiving the request parameters, assembling the request parameters in the process variables and guiding the business process to flow from the current node to the next node according to the process variables.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
presetting a script task component;
configuring script logic in the script task component, and configuring the script task component on a designated node in the process model;
the script task component is used for executing script logic tasks of the service.
As an optional embodiment of the present application, optionally, storing and publishing the business process model includes:
presetting a gateway;
configuring the gateway on a designated node of the business process model, and storing the business process model to a database;
and accessing the business process model to the network through the gateway and publishing the business process model to the online.
In another aspect of the present application, an apparatus for implementing the method for orchestrating services based on a Flowable workflow engine is provided, including:
the component splicing module is used for presetting a component splicing rule;
the configuration module is used for configuring the assembly splicing rule in a Flowable workflow engine;
the service arrangement module is used for arranging the service flow and constructing a service flow model in the Flowable workflow engine based on the component splicing rule;
and the distribution module is used for storing and distributing the business process model.
In another aspect of the present application, a service orchestration system is further provided, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the service orchestration method based on the Flowable workflow engine when executing the executable instruction.
The invention has the technical effects that:
the method comprises the steps that assembly splicing rules are preset; configuring the assembly splicing rule in a Flowable workflow engine; arranging a business process and constructing a business process model in the Flowable workflow engine based on the component splicing rule; and storing and releasing the business process model. Various business logics can be arranged through a workflow engine, and complex services and data isolated island conditions of interfaces can be dealt with. The business logic can be abstracted into the components, the public capacity of the business can be multiplexed, the circulation process of the business is abstracted into the flow, and the business logic is arranged in a visual configuration mode through arranging various components, so that the development cost of an enterprise is greatly reduced, and the development difficulty is reduced.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic flow chart illustrating an implementation of the Flowable workflow engine-based business orchestration method according to the present invention;
FIG. 2 is a schematic diagram showing a design page for the process of the present invention;
FIG. 3 is a schematic diagram illustrating the creation of a service invocation component of the present invention;
FIG. 4 is a diagram illustrating creation of a script task component;
FIG. 5 is a schematic diagram illustrating the use of a business process model by a user in accordance with the present invention;
FIG. 6 illustrates a workflow architecture diagram for developing a business process model for the present invention.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
The above example is first explained in terms of:
and (2) BPMN: business Process Modeling Notation refers to Business Process Modeling and labeling, providing a set of markup languages understood by all Business users. A standardized protocol is established between the design of the business process and the realization of the process.
Flowable workflow engine: flowable is a lightweight business process engine written in Java. The Flowable flow engine can be used to deploy BPMN2.0 flow definitions (industry XML standard for defining flows).
And (3) service arrangement: the business arrangement uses various capabilities to complete a certain business, and the capabilities are orderly woven and aggregated into a specific execution chain. Business orchestration is applicable to almost all business-type systems.
Visualization configuration: the visual configuration refers to that business rules are formed in a configuration mode, new rules are formed by plugging and unplugging certain components, each rule corresponds to a business identity (for example, "placing an order for a virtual commodity" is a business identity), and when a new business identity is needed, capacity is aggregated and arranged actually, and finally the needed business rules are configured.
Example 1
According to the method and the system, various business logics are arranged through the Flowable workflow engine, and the data isolated island condition of complex service and interface is responded. The business logic can be abstracted into the components, the public capacity of the business can be multiplexed, the circulation process of the business is abstracted into the flow, and the business logic is arranged in a visual configuration mode through arranging various components, so that the development cost of an enterprise is greatly reduced, and the development difficulty is reduced.
In this embodiment, the Flowable workflow engine is preferably configured in a workflow visualization console provided in an instruction set OS, and during business arrangement, the visualization arrangement is performed through a visualization configuration interface of the workflow visualization console of the instruction set OS. In other embodiments, the Flowable workflow engine may also be configured in other systems or platforms, which will not be described in this embodiment.
As shown in fig. 1, one aspect of the present application is disclosed and proposed, which provides a service orchestration method based on a Flowable workflow engine, including the following steps:
s1, presetting a component splicing rule;
the method and the device are used for setting the flow nodes based on the Flowable workflow engine, and arranging the business flow model through the set flow nodes. In specific implementation, a business process needs to be built through a functional component configured in the Flowable workflow engine (configured by the engine or configured by the user). Therefore, when a business process is built in the Flowable workflow engine, components need to be spliced according to a component splicing rule, and different functional components are configured at designated nodes.
As shown in fig. 2, in a flow design page (a visual configuration interface of a workflow graphic console) of the Flowable workflow engine, configured functional components, such as a start component, events corresponding to different components, a task component, a gateway component, and the like, may be displayed on the page. And setting each process node according to a preset service process, and configuring different functional components at each process node so as to realize a service processing process and finally obtain a service process model.
According to the embodiment, the following assembly splicing rules are provided, so that designers can conveniently splice the assemblies according to the assembly splicing rules, and the construction of the flow nodes is realized.
As an optional embodiment of the present application, optionally, the component splicing rule includes:
ensuring that the starting component in the Flowable workflow engine meets the following rules: the flow takes a starting component as a starting node, and the starting component only has an output stream; wherein the starting component comprises at least one of a null starting component, a timed starting component or a signal starting component;
ensuring that a finishing component in the Flowable workflow engine meets the following rules: the flow must take the end component as the end node, and the end component has only input stream; wherein the ending component comprises at least one of an empty ending component or a signal ending component.
As an optional implementation of the present application, optionally, the component splicing rule further includes:
ensuring that the sequential flow in the Flowable workflow engine meets the following rules: in addition to sequential flow, all flows between components must be connected by sequential flow;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the exclusive gateway has only one input stream, and at least two or more output streams are required;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the gateway has only one output stream, at least two or more input streams.
The above rules for each component can be implemented by designers in the field according to a design manual and business logic, and the configuration of the number of each component and input/output is also set according to business requirements, which is not limited in this embodiment. In the above rule, the starting component may be an empty starting component, a timing starting component or a signal starting component, and is configured to receive a user starting operation to start a flow, and start execution of a business flow from a starting node. When the executed flow variables are different events, the corresponding components of the respective events, such as the signal start component corresponding to the signal start event, are triggered.
S2, configuring the assembly splicing rule in a Flowable workflow engine;
and (4) after the assembly splicing rule is set, configuring the assembly splicing rule in the Flowable workflow engine. And the components in the left component toolbar are dragged and dragged to place and arrange the page according to the splicing rule, and the components are spliced with one another through sequential streams to form a complete process model.
When the assembly arranged by the designer does not meet the assembly splicing rule, the assembly can be displayed and reminded through the visual configuration interface, and arrangement is facilitated. If the application is subsequently performed, after the user starts the application program, the execution condition of each step of the program is displayed in a graph, and whether each step is executed according to an expected sequence or not can be quickly confirmed. If the process has errors, the process related log can be inquired in a system & operation and maintenance-log center-service log in the instruction set OS, so that the user can be helped to quickly find out the reason and remove the fault.
S3, arranging a service flow and constructing a service flow model in the Flowable workflow engine based on the assembly splicing rule;
after the configuration of the assembly splicing rule is finished, in a flow design page (a visual configuration interface of a workflow graphic console) of the Flowable workflow engine, a design user can start to arrange a business flow according to a set business flow node and construct a business flow model.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, including:
presetting a flow building rule;
based on the flow establishing rule, establishing a service flow node through the Flowable workflow engine;
and establishing and generating a process model according to the established business process nodes, and storing the process model into a preset database.
As shown in fig. 2, in the Flowable workflow engine, different service flow nodes (including at least one packet start node and one end node) are built. The business process nodes are built according to the process building rules, and are specifically designed according to the created business workflow. And designing the workflow of the constructed business flow according to the corresponding workflow. Therefore, the flow building rule is only required to be in accordance with the workflow flow of each service. And establishing and generating a process model according to the established business process nodes, and storing the process model in a storage layer such as a DB (database). The process model includes a workflow design process corresponding to a business process, wherein the process model must include a start node and an end node. As shown in fig. 2, the business is executed from the start node, and after the business is approved by the administrative approval node, the business reaches the end node, and the business approval workflow is completed. After the service passes through the gateway, the health code condition judgment is carried out, and the health code condition judgment is a process variable on one node and is used for executing variable judgment. In specific implementation, the service flow at the node is circulated through the service calling component.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
configuring the Flowable workflow engine in a workflow graphic console provided in an instruction set OS;
preparing a visual business arrangement flow through a visual configuration interface of the workflow graphic console;
and operating the functional components configured in the Flowable workflow engine based on the component splicing rule, and arranging the business flow.
In this embodiment, the Flowable workflow engine is configured in a workflow graphical console provided inside an instruction set OS, and the instruction set OS is used to design a business process, so that the instruction set is called conveniently to program, the working time of designers is saved, and the development cost is reduced. The visual configuration interface is a self-contained visual page and is used for visually displaying an arrangement process and a flow design page. The instruction set OS has its own functions, which are not described in detail in this embodiment.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
presetting a service calling component;
configuring a process variable in the service calling component, and configuring the service calling component on a designated node in the process model;
and the service calling component is used for receiving the request parameters, assembling the request parameters in the process variables and guiding the business process to flow from the current node to the next node according to the process variables.
As shown in fig. 3, in this embodiment, a service invocation component is set, and the service invocation component is mainly used for performing flow processing on a service flow of a node according to a service execution parameter of a node flow variable.
And the service task component can select built-in services of an instruction set OS, APIX (application interface X) related services or third-party services when the services are executed. The embodiment mainly configures a manner of invoking the APIX, sets a flow variable into a request parameter, and invokes a service according to the configured APIX. And when the node flow is executed, receiving the returned request parameters, and automatically assembling the request parameters into the flow variables to serve as judgment conditions of subsequent node flow.
As an optional embodiment of the present application, optionally, in the Flowable workflow engine, based on the component splicing rule, arranging a business process, and constructing a business process model, the method further includes:
presetting a script task component;
configuring script logic in the script task component, and configuring the script task component on a designated node in the process model;
the script task component is used for executing script logic tasks of the service.
As shown in fig. 4, in this embodiment, a JS, a Python, and a Groovy script may be configured to execute a relevant script logic, so as to implement a subtask of service execution. When the business model is arranged, the number of script task components can be designed according to the number of subtasks of the business, and the script task components are arranged on the branches of the business flow. The script logic of each script task component is specifically set according to the execution logic of each service subtask, which is not limited in this embodiment.
Each designated node is a business process node designated according to the execution requirement of the business, and the different components need to be configured at the designated node. The designated node will be designated according to the service execution logic.
And S4, storing and releasing the business process model.
After the business process model is arranged and created, verification and online are needed, and the business process model needs to be published through network access. Network access requires configuring a network component in a process node, and the embodiment sets a gateway.
As an optional embodiment of the present application, optionally, storing and publishing the business process model includes:
presetting a gateway;
configuring the gateway on a designated node of the business process model, and storing the business process model to a database;
and accessing the business process model to the network through the gateway and publishing the business process model to the online.
As shown in fig. 2, the gateways include an exclusive gateway, a parallel gateway, and an inclusive gateway, and may be selected according to a service requirement or customization. And adding the gateway into the service flow for online data interaction.
And according to the service arrangement, obtaining a service arrangement system corresponding to the service, obtaining a service flow model by the arrangement of the service arrangement system, checking the service flow model, and then carrying out online processing on the service flow model, thus starting online processing on the service.
As shown in fig. 5, for business processes using published business process models. Firstly, triggering the flow in a self-defined mode, wherein the flow triggering mode can be triggered by a null starting component, a timing starting component or a signal starting component. Such as null start component (corresponding to null start event at choreography): the start of the work is triggered by the submission buttons of the form and the report.
After the user starts the application program, the execution condition of each step of the program is shown graphically, and whether each step is executed according to the expected sequence can be quickly confirmed. If the process is wrong, the process related log can be inquired in a system, operation and maintenance-log center-service log in the instruction set OS, so that the user can be helped to quickly find out the reason and remove the fault.
As shown in fig. 6, the present embodiment is a workflow architecture for developing a business process model, and includes a design layer, a logic layer, and a storage layer.
The designer can design the business process model through the design layer, and the corresponding functional components are matched in the business process model, so that the designer can conveniently construct the model and the variables.
The logic layer is mainly used for providing a flow design logic and flow logic parameters for a designer, and providing selectable logic rules such as flow building rules and the like for the designer through a configured rule engine. The designer may write logic rules by himself. The logic layer also provides a Flowable workflow engine for setting process variables and designing a workflow model.
And the storage layer is configured with a plurality of databases for data storage, such as storage and calling of the business process model.
The above-mentioned architecture is only a service design architecture, functional components of the architecture, and the like of the present embodiment, and may be specifically set by an architect, and the components thereof may refer to the architecture design shown in fig. 2, which is not described in detail in the present embodiment.
It should be noted that, although the configuration environment of the above Flowable workflow engine is described by taking the instruction set OS as an example, those skilled in the art will understand that the present disclosure should not be limited thereto. In fact, the user can set the configuration environment flexibly according to the actual application scenario, as long as the technical function of the present application can be realized according to the above technical method.
Example 2
Based on the implementation principle of embodiment 1, in this embodiment, in another aspect of the present application, an apparatus for implementing the method for orchestrating a service based on a Flowable workflow engine is provided, where the apparatus includes:
the component splicing module is used for presetting a component splicing rule;
the configuration module is used for configuring the assembly splicing rule in a Flowable workflow engine;
the service arrangement module is used for arranging the service flow and constructing a service flow model in the Flowable workflow engine based on the component splicing rule;
and the distribution module is used for storing and distributing the business process model.
The application principle and the function implementation principle of each module described above refer to the description of embodiment 1 specifically, and this embodiment is not described again.
It should be apparent to those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, and the program can be stored in a computer readable storage medium, and when executed, the program can include the processes of the embodiments of the control methods described above. The modules or steps of the invention described above can be implemented by a general purpose computing device, they can be centralized on a single computing device or distributed over a network of multiple computing devices, and they can alternatively be implemented by program code executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof can be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the control methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), a Random Access Memory (RAM), a flash memory (FlashMemory), a hard disk (hard disk drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.
Example 3
In a further aspect of the present application, a business orchestration system is further provided, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the service orchestration method based on the Flowable workflow engine when executing the executable instruction.
The disclosed embodiments provide a business orchestration system comprising a processor and a memory for storing processor executable instructions. Wherein the processor is configured to execute the executable instructions to implement any one of the above-mentioned service orchestration methods based on the Flowable workflow engine.
Here, it should be noted that the number of processors may be one or more. Meanwhile, in the service orchestration system according to the embodiment of the present disclosure, an input device and an output device may be further included. The processor, the memory, the input device, and the output device may be connected by a bus, or may be connected by other means, and are not limited specifically herein.
The memory, as a computer-readable storage medium, may be used to store software programs, computer-executable programs, and various modules, such as: the embodiment of the disclosure relates to a program or a module corresponding to a service arrangement method based on a Flowable workflow engine. The processor executes various functional applications and data processing of the business orchestration system by running software programs or modules stored in the memory.
The input device may be used to receive an input number or signal. Wherein the signal may be a key signal generated in connection with user settings and function control of the device/terminal/server. The output device may include a display device such as a display screen.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (10)
1. A service arrangement method based on a Flowable workflow engine is characterized by comprising the following steps:
presetting a component splicing rule;
configuring the assembly splicing rule in a Flowable workflow engine;
arranging a business process and constructing a business process model in the Flowable workflow engine based on the component splicing rule;
and storing and releasing the business process model.
2. The workflow engine-based business arrangement method according to claim 1, wherein the component splicing rule comprises:
ensuring that the starting component in the Flowable workflow engine meets the following rules: the flow takes a starting component as a starting node, and the starting component only has an output stream; wherein the starting component comprises at least one of an empty starting component, a timed starting component or a signal starting component;
ensuring that an ending component in the Flowable workflow engine meets the following rules: the flow must take the end component as the end node, and the end component has only input stream; wherein the end component comprises at least one of an empty end component or a signal end component.
3. The workflow engine-based business arrangement method according to claim 2, wherein the component splicing rule further comprises:
ensuring that the sequential flow in the Flowable workflow engine meets the following rules: in addition to sequential flow, all flows between components must be connected by sequential flow;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the exclusive gateway has only one input stream, and at least two or more output streams;
ensuring that an exclusive gateway in the Flowable workflow engine meets the following rules: the gateway has only one output stream, at least two or more input streams.
4. The method for orchestrating services based on a Flowable workflow engine according to claim 1, wherein in the Flowable workflow engine, based on the component splicing rule, a service flow is orchestrated, and a service flow model is constructed, including:
presetting a flow building rule;
building a business process node through the Flowable workflow engine based on the process building rule;
and establishing and generating a flow model according to the established business flow nodes, and storing the flow model into a preset database.
5. The method for orchestrating services based on a Flowable workflow engine according to claim 4, wherein in the Flowable workflow engine, based on the component splicing rule, orchestrating a service flow, and constructing a service flow model, further comprises:
configuring the Flowable workflow engine in a workflow graphic console provided in an instruction set OS;
preparing a visual business arrangement flow through a visual configuration interface of the workflow graphic console;
and operating the functional components configured in the Flowable workflow engine based on the component splicing rule, and arranging the business flow.
6. The method for orchestrating services based on a Flowable workflow engine according to claim 4, wherein in the Flowable workflow engine, based on the component splicing rule, a service flow is orchestrated, a service flow model is constructed, and further comprising:
presetting a service calling component;
configuring a process variable in the service calling component, and configuring the service calling component on a designated node in the process model;
and the service calling component is used for receiving the request parameters, assembling the request parameters in the process variable and guiding the business process to flow from the current node to the next node according to the process variable.
7. The method for orchestrating services based on a Flowable workflow engine according to claim 4, wherein in the Flowable workflow engine, based on the component splicing rule, a service flow is orchestrated, a service flow model is constructed, and further comprising:
presetting a script task component;
configuring script logic in the script task component, and configuring the script task component on a designated node in the process model;
the script task component is used for executing script logic tasks of the service.
8. The workflow engine-based business orchestration method according to claim 1, wherein storing and publishing the business process model comprises:
presetting a gateway;
configuring the gateway on a designated node of the business process model, and storing the business process model to a database;
and accessing the business process model to the network through the gateway and publishing the business process model to the online.
9. An apparatus for implementing a service orchestration method based on a Flowable workflow engine according to any one of claims 1-8,
the component splicing module is used for presetting a component splicing rule;
the configuration module is used for configuring the assembly splicing rule in a Flowable workflow engine;
the service arrangement module is used for arranging the service flow and constructing a service flow model in the Flowable workflow engine based on the component splicing rule;
and the distribution module is used for storing and distributing the business process model.
10. A business orchestration system comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the executable instructions to implement a Flowable workflow engine-based business orchestration method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210872404.4A CN115185496A (en) | 2022-07-20 | 2022-07-20 | Service arrangement method based on Flowable workflow engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210872404.4A CN115185496A (en) | 2022-07-20 | 2022-07-20 | Service arrangement method based on Flowable workflow engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115185496A true CN115185496A (en) | 2022-10-14 |
Family
ID=83521291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210872404.4A Pending CN115185496A (en) | 2022-07-20 | 2022-07-20 | Service arrangement method based on Flowable workflow engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115185496A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115509523A (en) * | 2022-11-24 | 2022-12-23 | 湖南创星科技股份有限公司 | API service rapid establishing method and system |
| CN116107549A (en) * | 2023-04-13 | 2023-05-12 | 成都新希望金融信息有限公司 | Logic arrangement and change service logic processing method, system and storage medium |
-
2022
- 2022-07-20 CN CN202210872404.4A patent/CN115185496A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115509523A (en) * | 2022-11-24 | 2022-12-23 | 湖南创星科技股份有限公司 | API service rapid establishing method and system |
| CN115509523B (en) * | 2022-11-24 | 2023-03-03 | 湖南创星科技股份有限公司 | API service rapid construction method and system |
| CN116107549A (en) * | 2023-04-13 | 2023-05-12 | 成都新希望金融信息有限公司 | Logic arrangement and change service logic processing method, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10999218B2 (en) | Reservation of resources and deployment of applications using an integrated development environment | |
| CN111078315B (en) | Microservice arranging and executing method and system, architecture, equipment and storage medium | |
| CN115185496A (en) | Service arrangement method based on Flowable workflow engine | |
| US20050144529A1 (en) | Method for defined derivation of software tests from use cases | |
| EP2926266A1 (en) | Cloud object | |
| CN114691308A (en) | Online task arranging method and online task arranging device | |
| US20120272190A1 (en) | Method and System for Graphically Enabled Service Oriented Architecture | |
| US9170786B1 (en) | Composable context menus | |
| Harzenetter et al. | Automated generation of management workflows for applications based on deployment models | |
| Sundas et al. | An introduction of CloudSim simulation tool for modelling and scheduling | |
| US20140082587A1 (en) | Method And System For Generating A Source Code For A Computer Program For Execution And Simulation Of A Process | |
| WO2017074469A1 (en) | Cloud lifecycle management | |
| CN114912897A (en) | Workflow execution method, workflow arrangement method and electronic equipment | |
| US20170011322A1 (en) | Business process managment | |
| CN109491705B (en) | Delivery method and device | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
| CN111158684B (en) | System creation method, device, electronic equipment and readable storage medium | |
| JP2023038909A (en) | Computer implemented method, computer program product, and system (constraints-based refactoring of monolith applications through attributed graph embeddings) | |
| CN114936152A (en) | Application testing method and device | |
| Straesser et al. | Kubernetes-in-the-Loop: Enriching Microservice Simulation Through Authentic Container Orchestration | |
| Erbel | Scientific Workflow Execution Using a Dynamic Runtime Model | |
| US9053239B2 (en) | Systems and methods for synchronizing software execution across data processing systems and platforms | |
| CN114492051A (en) | Digital workshop dynamic reconstruction method, device, equipment and storage medium | |
| CN114153444A (en) | Method and device for constructing combined service | |
| CN114036065A (en) | Method and device for building test environment, electronic equipment and 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 |