The update procedure takes the following steps:

  • Update the optional Camunda BPM libraries
  • Update Camunda web applications
  • Configure Process Engines
    In each of the following steps, the identifiers refer to the current version and the new versions of the artifacts.

The pre-built Camunda 7.3 distribution ships with Tomcat 7.0.62, whereas 7.2 comes with Tomcat 7.0.50. Camunda 7.3 is supported on all Tomcat 6⁄7 versions such that a Tomcat update is not required when migrating from 7.2 to 7.3.

Should you want to update Tomcat along with Camunda, perform the following steps either before or after updating Camunda:

  • Copy all your Camunda-related libraries from $TOMCAT_HOME/lib to the new Tomcat server’s lib-directory.
  • Apply all modifications to Tomcat configuration files such as server.xml/bpm-platform.xml to the files located in the new Tomcat server’s directory.
  • Undeploy all process applications and copy them to the new Tomcat server’s directory for redeployment.
    See the Tomcat migration guide for any Tomcat-specific migration notes and procedures.

1. Update the Camunda BPM Core Libraries

  • camunda-engine-$PLATFORM_VERSION.jar
  • camunda-bpmn-model-$PLATFORM_VERSION.jar
  • camunda-cmmn-model-$PLATFORM_VERSION.jar
  • camunda-xml-model-$PLATFORM_VERSION.jar

    2. Update Optional Camunda BPM libraries

In addition to the core libraries, there may be optional artifacts in $TOMCAT_HOME/lib/ for LDAP integration, Camunda Connect, and Camunda Spin. If you use any of these extensions, the following update steps apply:

Copy the following libraries from $TOMCAT_DISTRIBUTION/lib to the folder if present:

  • camunda-identity-ldap-$PLATFORM_VERSION.jar

    Camunda Connect

Copy the following libraries from $TOMCAT_DISTRIBUTION/lib to the folder $TOMCAT_HOME/lib/ if present:

  • camunda-connect-core-$CONNECT_VERSION.jar
  • camunda-engine-plugin-connect-$PLATFORM_VERSION.jar
  • camunda-spin-dataformat-all-$SPIN_VERSION.jar
  • camunda-spin-core-$SPIN_VERSION.jar
  • camunda-engine-plugin-spin-$PLATFORM_VERSION.jar

    3. Update Web Applications

Update REST API

The following steps are required to update the camunda REST API on a Tomcat instance:

  • Undeploy an existing web application with a name like camunda-engine-rest
  • Download the REST API web application archive from our Or switch to the private repository for the enterprise version (User and password from license required). Choose the correct version named $PLATFORM_VERSION/camunda-engine-rest-$PLATFORM_VERSION-tomcat.war.
  • Deploy the web application archive to your Tomcat instance.

The following steps are required to update the camunda web applications Cockpit, Tasklist, and Admin on a Tomcat instance:

  • Undeploy an existing web application with a name like camunda-webapp
  • Download the Camunda web application archive from our Maven Nexus Server). Or switch to the private repository for the enterprise version (User and password from license required). Choose the correct version named $PLATFORM_VERSION/camunda-webapp-tomcat-$PLATFORM_VERSION.war.
  • Deploy the web application archive to your Tomcat instance.

LDAP Entity Caching

It is possible to enable entity caching for Hypertext Application Language (HAL) requests that the camunda web applications make. This can be especially useful when you use camunda in combination with LDAP. To activate caching, the camunda webapp artifact has to be modified and the pre-built application cannot be used as is. See the for details.

4. Configure Process Engines

Task Query Expressions