Install the Standalone Webapplication (.war)

This document will guide you through the installation and configuration of the Camunda standalone web application. The Camunda web application combines Cockpit and Tasklist. The web application is self-contained and includes an embedded process engine, which is configured inside the application. The process engine is configured using the Spring Framework and will automatically start when the application is deployed. The process engine must be configured to connect to a database (see the database configuration section). By default the process engine will use a built-in identity service, which can be replaced with LDAP (see the LDAP configuration section).

Embedded vs. Shared Process Engine

Note: Since the Camunda standalone web application uses an embedded process engine it must not be installed to an application server from a Camunda distribution download. Application servers contained in Camunda distributions already provide a shared process engine


If you are an Enterprise Edition Customer, please use the enterprise download page.

As a Community Edition user you can download the Camunda standalone webapp matching your application server here:

Application Server Link
Apache Tomcat camunda-webapp-tomcat-standalone-7.17.0.war
WildFly camunda-webapp-jboss-standalone-7.17.0.war


Once you downloaded the camunda-webapp-SERVER-standalone-VERSION.war file you must deploy it to your application server.
Note: Make sure to use a vanilla distribution of your application server, not an application server downloaded from Camunda.
The exact deployment procedure for web applications depends on your application server. In case you aren’t sure how to install the application, please refer to your application server documentation.

The default context path for the Camunda web application is /camunda.
Note: If you install the Camunda standalone web application on Apache Tomcat by dropping it in the webapps folder, Tomcat will assign the filename of the war file as the context path. If you want the context path to be /camunda, rename the war file to camunda.war.

Given that your application is binding to localhost, is running on port 8080 and the context path is /camunda, you can then access the Camunda standalone web application by using the following url:


Database Configuration

The Camunda standalone webapp is initially configured using a file-based H2 database and a HikariCP datasource. The h2 database is only useful for demo purposes. If you want to use the standalone webapp in production we recommend using a different database.

In order to configure another database, edit the file named WEB-INF/applicationContext.xml inside the camunda-webapp-SERVER-standalone-VERSION.war. Edit the following section with the appropriate configuration values for your database.

<bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
  <property name="targetDataSource">
    <bean class="com.zaxxer.hikari.HikariDataSource">
      <property name="driverClassName" value="org.h2.Driver" />
      <property name="jdbcUrl" value="jdbc:h2:./camunda-h2-dbs/process-engine;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE" />
      <property name="username" value="sa" />
      <property name="password" value="" />

Note: If you configure a different database do not forget to add the corresponding database driver to the classpath of the web application.

As an alternative you can also configure a datasource inside your application server and look it up from the web application.

LDAP Configuration

Adjust the Process Engine Configuration

Initially the Camunda standalone webapp is configured to use a built-in database identity service. If you want to use LDAP instead you have to activate the Camunda LDAP identity service. The file WEB-INF/applicationContext.xml already contains a configuration example which is deactivated. In order to activate it, simply uncomment the lines shown below:

<bean id="processEngineConfiguration" class="org.camunda.bpm.engine.spring.SpringProcessEngineConfiguration">
  <!-- ... -->
  <property name="processEnginePlugins">
      <!-- Uncomment the following next two lines to activate LDAP -->
      <!--<ref bean="ldapIdentityProviderPlugin" />-->
      <!--<ref bean="administratorAuthorizationPlugin" />-->

To configure the LDAP service please adjust the values of the bean named ldapIdentityProviderPlugin as described in the user guide. Do not forget to configure the Administrator Authorization Plugin as well.

HAL Resource Caching

If you use LDAP as Indentity Provider, you should consider activating caching of Users and Groups in the Camunda webapplication. In order to activate this, add the following configuration to the web.xml file of Camunda webapplication:

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns=""

  <!-- ... -->


        "cacheImplementation": "",
        "caches": {
          "": {
            "capacity": 100,
            "secondsToLive": 900
          "": {
            "capacity": 100,
            "secondsToLive": 900

  <!-- ... -->


On this Page: