Open source, powerful workflow engine: introduction to camunda

 Originality is not easy, please support! For children's shoes who are interested in Java technology, please pay attention to me. 

Introduction

Camunda is a Java-based framework supporting BPMN for workflow and process automation, CMMN for Case Management and DMN for Business Decision Management.

important concepts

• BPMN -Business Process Model and Notation (BPMN) is a standard for Workflow and Process Automation. Camunda supports the 2.0 version of BPMN.
• https://docs.camunda.org/get-started/bpmn20/
• CMMN-Case Management Model and Notation (CMMN) is a standard for Case Management. Camunda supports the 1.1 version of CMMN.
• https://docs.camunda.org/get-started/cmmn11/
• DMN -Decision Model and Notation (DMN) is a standard for Business Decision Management. Camunda supports the 1.1 version of DMN.
• https://docs.camunda.org/get-started/dmn11/

Workflow comparison

Key figures introduction

Tom Baeyens-created jbpm. After leaving JBoss, the next version of jBPM, jBPM5, completely abandoned the basic code of jBPM4, and started over based on Drools Flow. At present, the official website has launched the beta version of jBPM6; Tom Baeyens soon launched a new open source based on jBPM4 after joining Alfresco. Workflow system Activiti. At the end of 2012, Alfresco's Activity BPM team is undergoing a series of changes: Tom Baeyens will no longer lead the Activity project and decided to leave Alfresco. Camunda is one of Activity's largest contributors (except Alfresco) and one of its main executive consulting partners. Camunda said that Activity may be too constrained to Alfresco's need for document-centric workflows, while ignoring the more common BPM platform when Activity started, so the camunda BPM project was established from the Activiti branch.

Frame overview

Process engine architecture

Frame example

Camunda integrated container download :

• https://camunda.org/download/

Unzip tomcat, switch to the directory server\apache-tomcat-8.0.24\webapps, which contains the following subdirectories:

•Camunda- -Management function modules, including admin, cockpit, tasklist

•camunda-invoice – invoice approval demo

•engine-rest – workflow engine Rest API module

•Examples – other demo examples

Database creation:

Switch directory sql\create\Select the corresponding sql script to execute

tomcat configuration modification:

Switch to server\apache-tomcat-8.0.24\conf\ directory

bpm-platform.xml

camunda own configuration maintenance file.

The following global configuration attributes can be modified according to specific application scenarios

full

true

true

true

Tomcat configuration modification:

Switch to server\apache-tomcat-8.0.24\conf\directory

server.xml

tomcat container management configuration maintenance file.

auth="Container"

type="javax.sql.DataSource"

factory="org.apache.tomcat.jdbc. pool.DataSourceFactory"

uniqueResourceName="process-engine"

driverClassName="oracle.jdbc.driver.OracleDriver"

url="jdbc:oracle:thin:@127.0.0.1:1521: camunda"

defaultTransactionIsolation="READ_COMMITTED"

username="camunda"

password="123456"

maxActive="20"

minIdle="5"da1a7d##removeAbandoned="true"

removeAbandonedTimeout="60"

testOnBorrow="true"

validationQuery="select count(1) from dual"

logAbandoned="true"/>

application integration

add dependency package

compile &x27;org.camunda. bpm:camunda-engine:7.7.0&x27;

compile &x27;org.camunda.bpm:camunda-engine-spring:7.7.0&x27;

add spring bean

 


 
 
 
 
 
 9c2d0f#8b0f0f0# 9c2d0f#8b0#8b0f0f#0b0##
 





 

5588d#4eder1a0 design process file The template is placed in the resources directory or subdirectory of the application project.

User integration method

Camunda's own user system

Excellent: No need to change

Lack: poor flexibility, high operation and maintenance costs

Use ldap users Integration

Excellent: Can be docked with support ldap function

Lack: Rely on ldap function limitation

Extend the user system through plug-ins

Excellent: Customization can be achieved through extension Requirement

Lack: Familiar with camunda, high development cost

Only use workflow node circulation function

Excellent: Flexible application, can meet different business needs

Lack: camunda part Rich functions cannot be used, and there may be components in the redevelopment framework

Job Executor

Document address: https://docs.camunda.org/manual/7.7/user-guide/process-engine/the-job-executor /

Job activation configuration:

job Work structure:

homogeneous cluster deployment:

Heterogeneous cluster deployment:

Support heterogeneous cluster deployment, deploy node setting jobExecutorDeploymentAware=true

true

Appendix

• engine-rest api
• https://docs.camunda.org/manual/7.7/reference/rest/
• Web modeler
• http://bpmn.io/toolkit/bpmn-js/walkthrough/
• camunda get-started
• https://docs.camunda.org/get-started/
• Camunda Guid
• https://docs.camunda.org/manual/7.7/introduction/
• LDAP Identity Service
• https://docs.camunda.org/manual/7.7/user-guide/process-engine/identity-service/