CN105760180A

CN105760180A - Workflow engine expansion development method

Info

Publication number: CN105760180A
Application number: CN201610167716.XA
Authority: CN
Inventors: 毕孝田
Original assignee: Inspur Communication Information System Co Ltd
Current assignee: Inspur Communication Information System Co Ltd
Priority date: 2016-03-23
Filing date: 2016-03-23
Publication date: 2016-07-13
Anticipated expiration: 2036-03-23
Also published as: CN105760180B

Abstract

The invention provides an expansion development method of a workflow engine, which belongs to the field of comprehensive resource management of mobile operators and can quickly develop a desired business process. The method supports the standardization and the componentization of each part of the business process development under the B/S architecture, realizes the dynamic customization of parts such as business process link forms, WEB services, processing roles, general functions and the like, and simplifies the development and the maintenance of the actual process.

Description

Workflow engine expansion development method

Technical Field

The invention relates to the field of comprehensive resource management of mobile operators, in particular to an expansion development method of a workflow engine.

Background

In the field of system operation and maintenance of various industries, the application range of a workflow engine is very wide, and a lot of experience is accumulated in the process of secondary development of various software companies, but the problems of few defects of seamless combination with a BS page, high requirement on deployment conditions, complex configuration, repeated development of functions and the like are really achieved.

Disclosure of Invention

In order to solve the problem, the invention provides an expansion development method of a workflow engine, the method of the invention has simple configuration method and is based on component secondary development, and all programs are based on java + jsp and are seamlessly combined with a BS system; the deployment is simple, and the door-entering threshold of developers is low.

The method comprises the steps of analyzing a flow definition diagram on the basis of a flow engine developed according to an XPDL standard or a BPEL standard through a standardized interface, abstracting elements (forms, role personnel, Web services and general services) of relevant dimensions of operation of business nodes into components, designing a unified framework to seamlessly integrate and connect all parts, standardizing the development process of the business flow, and solving the problem of repeated function development in the business flow development based on a workflow engine

The technical scheme provided by the invention is as follows:

an expansion development method of a workflow engine is characterized by comprising

1) And various elements of the process definition file: analyzing and storing a start node, an end node, a service node and a line, and cleaning various basic elements by reading a flow chart definition file of an analysis workflow engine to support an upper-layer component for use;

2) the method comprises the steps of customizing and developing a flow form and performing associated binding with flow artificial nodes, wherein the form which is the most main in business flow circulation is configured into a reusable component, and flexible binding with flow links is supported;

3) the role definition configuration and the associated binding with the flow artificial nodes are realized, the role processing personnel of each link of the flow is configured in a componentization mode, and the flexible binding with the flow link is supported;

4) the method comprises the following steps of (1) defining and developing WEB services and associating and binding with process artificial nodes, and supporting flexible binding with process links by means of component configuration of interactive interfaces of each process link and other systems;

5) and (4) binding the general functions and the association of the flow artificial nodes.

Wherein,

analyzing a flow chart based on an XPDL or BPEL standard, extracting basic elements (a start node, an end node, a service node and a line) related to an architecture, and storing the basic elements into a corresponding table.

Secondly, a form library is created aiming at the forms of the service nodes, the configuration of the forms is maintained, and flexible binding with the process service nodes is supported.

Creating role library for the service node, maintaining dynamic configuration of role and personnel, and supporting flexible binding with the flow service node.

And fourthly, establishing a WEB service library aiming at the personnel of the business nodes, maintaining WEB service interface configuration between modules and between systems, including address, method, parameter input and parameter output configuration management, and supporting flexible binding with the process business nodes.

And fifthly, configuring and enabling or not enabling corresponding general functions for each service node.

Integrating the above elements via a uniform structure, and realizing the customized development business process rapidly only by developing a fixed standardized method and developing a corresponding foreground form page.

The invention has the advantages that

1) The standardization level and the development efficiency in the workflow engine-based business process development are improved:

2) the problem of repeated development of the business process function is solved.

Drawings

FIG. 1 is a technical architecture diagram of the present invention;

FIG. 2 is a table of various types of elements of a process definition file;

FIG. 3 is a table of form configurations;

FIG. 4 is a table of node binding service form associations;

FIG. 5 is a role management table;

FIG. 6 is a table of node binding role associations;

FIG. 7 is a resource service interface master table;

FIG. 8 is a node bound resource service association table.

Detailed Description

The invention is explained in more detail below:

the method comprises the steps of analyzing basic elements (a start node, an end node, a service node and a line) related to the architecture based on a flow diagram of an XPDL or BPEL standard, and storing the basic elements into a corresponding table.

And secondly, developing a form and maintaining the form in a form library aiming at each service node, and then binding the form with the process service node.

And developing roles and maintaining the roles in a role library aiming at each service node, configuring the association between the roles and personnel, and then binding the roles and the process service nodes.

Developing WEB service and configuring it to WEB service library for each service node, then binding WEB service and flow service node.

Sixthly, developing a standardized method for realizing fixation, embedding the standardized method into the whole framework, and issuing the standardized method to a corresponding server for access.

Claims

1. An expansion development method of a workflow engine is characterized by comprising

2. The method of claim 1, wherein parsing the flow chart based on XPDL or BPEL standard extracts the basic elements related to the architecture and stores them in the corresponding table.

3. The method of claim 1, wherein a list library is created for the list of business nodes, and wherein the configuration of the list is maintained to support flexible binding with the process business nodes.

4. The method of claim 1, wherein a role library is created for personnel of a business node, dynamic configuration of roles and personnel is maintained, and flexible binding with process business nodes is supported.

5. The method of claim 1, wherein a WEB services library is created for the personnel of the business nodes, and the configuration of WEB service interfaces between modules and between systems is maintained, including the configurable management of addresses, methods, entries and exits, and flexible binding with the process business nodes is supported.

6. The method of claim 1, wherein for each service node, enabling or not enabling the corresponding generic function is configured.