[6]
The integration of Spring and JBPM need to use third party libraries: spring-modules - jbpm. jar. The Spring creates the JbpmConfiguration object and connects to database. We configure the JbpmConfiguration object in the configuration file of Spring. 3. 2 Design of service interface This system is designed according to service-oriented, in which service is as the center. The service of system is abstracted from the system business, implemented services, and define the service interface. Other levels of the system are designed around the service and are restricted by the service interface. All data accessing are obtained thou though service interface, to maximize the thinking of hierarchical realization. We design seven service interfaces in workflow management module: BaseManager, JbpmManager, JbpmFunctionManager, JbpmAdviceBefore, ChartManager, UserManager, and DepartmentManager. Their relationships are shown as fig. 2. Fig. 2 Relationship of service interfaces 3. 3 Database design of JBPM There are some built-in database tables in JBPM workflow engine to record the process of the system information, such as jbpm_action table, table jbpm_decisionconditions table, jbpm_delegation table etc. Moreover to meet the demand of complexity business, we design custom tables to record business logic data of users. Here are some workflow tables: process application table, examination opinions table, personal opinion table, personal signature table, appendix table and operation log table. 4 Implement of workflow management module The working of a workflow process includes: workflow definition, workflow deployment, workflow running and workflow termination.
Google Scholar
[7]
4. 1 workflow definition The workflow definition is a process definition of abstract object. Each process definition can have many different versions. For example for the same process, two versions of process definition are together stored in the jPDL database: before revision and after revision.
One of the characteristics of JBPM workflow engine is that the user can add their own engine execution logic according to need, such as response to certain events, execute a special code in the node, dynamically generate task instance. The extensions are usually represented in event response, node action and task allocation. These extensions directly implemented by JBPM workflow engine. 4. 2 Workflow deployment The definitions of processes in JBPM are defined by the jPDL XML. When the process is completed, GPD will automatically generate a process definition.
DOI: 10.1002/0471741442.ch12
Google Scholar
[6]
The API which needs to use JBPM, will deploy to the server. For example, to deploy reimbursement process", jPDL documents of process are delivered to the engine Purchase. xml. In addition, in order to view the process tracing legend, JBPM also supports deployment process through uploading zip package. When formal work, rather than the Purchase. xml file, the JBPM accesses the process definitions from the database. The file of process definition is only read once at initialization time, and then it will be saved in the database. After successful deployment, JBPM will return ID of the process definition, with which to manage this process. 4. 3 Workflow running Take "reimbursing process, as an example, the steps of a process execution are following. When needs a reimbursing business application, click the process application, then select the appropriate business processes and submit corresponding application information. The background of the Action control layer will package the collective business application information, call a service interface of JBPM, and request to establish the process instance. The service interface is a middle service layer, which can not directly request access to the database, but access the corresponding data access interface. The data access interface can directly manipulate the database, then this business information is stored in the database and a process instance will be generated. Finally result information will be returned to inform the user in the front page. Conclusions We use the JBPM workflow engine design and implementation of an OA system, which supports the standard HTTP accessing of multi client platform in local area network or internet. Application shows that, this system effectively solves the defects of the fixed traditional business process, supports business process reengineering, and greatly improves the flexibility of the system. The main work in the future is to analyze and evaluate of the business process, designing and implementing tools of monitoring and tracking. These tools can monitor the process execution state, track the entire life cycle to the process, scientifically evaluate to efficiency and cost of the process. Acknowledgement This work is supported by the Science and Technology Innovation Project of Guangdong Province under Grant 2012KJCX0097 Renference.
Google Scholar
[1]
Diimitrios Georgakopoulos, Mark Hornick, Amit Sheth. An overview of workflow management: From process modeling to workflow automation infrastructure[J]. Distributed and Parallel Databases vol. (2)119～153(1995).
DOI: 10.1007/bf01277643
Google Scholar
[2]
Clarence Ellis and Karim Keddara. ML-DEWS: Modeling Language to Support Dynamic Evolution within Workflow Systems[J]. Computer Supported Cooperative Work (CSCW) . 2000 (3-4).
DOI: 10.1023/a:1008799125984
Google Scholar
[3]
Paul A. Buhler and Jose M. Vidal. Towards Adaptive Workflow Enactment Using Multiagent Systems, Information Technology and Management Vol. (6)61-87(2005).
DOI: 10.1007/s10799-004-7775-2
Google Scholar
[4]
Huang Y, Zhang R and Fei Y. Research on campus OA system construction based on workflow technology[J]. Journal of Changsha Telecommunications and Technology Vocational College, （2011）.
Google Scholar
[5]
Information on http: /www. wfmc. org.
Google Scholar
[6]
Information on https: /www. jboss. org/jbpm.
Google Scholar
[7]
Gao Jie. Explain profound theories in simple language jBPM" [M] people, s Posts and Telecommunications Press(in Chinese)(2009).
Google Scholar
