There are many ways to install and deploy Camunda BPM. Installing and deploying Camunda's independent web application is the simplest way. You only need to have tomcat.
This document will guide you to install and configure Camunda standalone web application to quickly experience camunda BPM. The Camunda web application combines Cockpit and Tasklist. The web application is self-contained and contains an embedded process engine that is configured inside the application. The process engine is configured using the Spring framework and will be automatically started when the application is deployed. The process engine must be configured to connect to the database. By default, the process engine will use the built-in organization user service, which can be replaced with LDAP.
The first step is to download the deployment package
As a community version user, you can download the Camunda standalone webapp that matches your application server here:
The second step, deploy to Tomcat
Once you download camunda-webapp-SERVER-standalone-VERSION. The War file must be deployed on the application server. The default context path of the Camunda web application is /Camunda.
If you install Camunda's standalone web application on Apache Tomcat and put it in the webapps folder, Tomcat will specify the file name of the war file as the context path. If you want the context path to be /camunda, please rename the war file to camunda.war.
Assuming your application is bound to localhost, running on port 8080, and the context path is /camunda, you can use the following url to access camunda's independent web application: http://localhost:8080/camunda/
The third step, configure the database
The Camunda standalone webapp uses the file-based H2 database and Apache Commons DBCP data source for configuration by default. The h2 database is for demonstration purposes only. If you want to use a standalone webapp in your product, we recommend using a different database.
If you want to configure other databases, edit the file named WEB-INF/applicationContext.xml in camunda-webapp-SERVER-standalone-VERSION.war. Edit the following sections with the appropriate configuration values for the database.
<bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy"> <property name="targetDataSource"> <bean class="org.apache.commons.dbcp.BasicDataSource"> <property name="driverClassName" value="org.h2.Driver" /> <property name="url" value="jdbc:h2:./camunda-h2-dbs/process-engine;MVCC=TRUE;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE" /> <property name="username" value="sa" /> <property name="password" value="" /> </bean> </property> </bean>
If you configure a different database, don't forget to add the corresponding database driver in the classpath of the web application.
Use the official H2 database first, and do not configure it in this step.
The fourth step, access and initialize the system
After Tomcat is started, visit: http://localhost:8080/camunda/, the initial account interface appears.
After successfully creating the admin/123456 account, jump to the login page:
http://127.0.0.1:8080/camunda/app/ After admin/default/#/login is
successfully logged in, enter the "Administrative Console", where you can manage users, groups, tenants, authorization management, and some common configurations of the system.
Click "TaskList" in the upper right corner to enter the "Process Portal", where you can initiate the process and approval process
Currently there is no process available, so the process cannot be initiated. The following chapters will talk about how to design the process.
Click "Cockpit" in the upper right corner to enter the "Process Monitoring Station", where you can monitor and manage the process.
to sum up
The above describes how to quickly run camunda BPM. Since there is no design process template, it cannot be used. The following article introduces how to use the process designer to draw a flowchart and publish it to BPM. Yuncheng BPM is developed based on camunda, and interested users can experience http://www.yunchengxc.com.