The update procedure takes the following steps:
- Update the Camunda BPM Modules
- Update Optional Camunda BPM Modules
- Update Camunda Web Applications
Whenever the instructions are to replace a module, make sure to delete the previous version of the module first to avoid orphan jars.
1. Update the Camunda BPM Modules
Replace the following modules from the folder $APP_SERVER_HOME/modules/
with their new versions from the folder :
- org/camunda/bpm/camunda-engine
- org/camunda/bpm/$APP_SERVER/camunda-$APP_SERVER-subsystem
- org/camunda/bpm/model/camunda-cmmn-model
- org/camunda/bpm/model/camunda-dmn-model
- org/camunda/bpm/model/camunda-xml-model
- org/camunda/bpm/dmn/camunda-engine-dmn
- org/camunda/bpm/dmn/camunda-engine-feel-api
- org/camunda/bpm/dmn/camunda-engine-feel-juel
- org/camunda/commons/camunda-commons-logging
- org/camunda/commons/camunda-commons-typed-values
- org/camunda/commons/camunda-commons-utils
2. Update Optional Camunda BPM Modules
In addition to the core modules, there may be optional artifacts in $APP_SERVER_HOME/modules/
for LDAP integration, Camunda Connect, Camunda Spin, and Groovy scripting.If you use any of these extensions, the following update steps apply:
- org/camunda/bpm/identity/camunda-identity-ldap
Replace the following modules from the folder with their new versions from the folder $APP_SERVER_DISTRIBUTION/modules/
, if present:
- org/camunda/connect/camunda-connect-core
- org/camunda/connect/camunda-connect-http
- org/camunda/connect/camunda-connect-soap-http
Replace the following modules from the folder $APP_SERVER_HOME/modules/
with their new versions from the folder $APP_SERVER_DISTRIBUTION/modules/
, if present:
- org/camunda/spin/camunda-spin-core
- org/camunda/spin/camunda-spin-dataformat-json-jackson
- org/camunda/spin/camunda-spin-dataformat-xml-dom
org/camunda/bpm/camunda-engine-plugin-spin
Additionally, also replace the following dependent modules:- com/fasterxml/jackson/core/jackson-core
- com/fasterxml/jackson/core/jackson-databind
Replace the following module from the folder with its new version from the folder $APP_SERVER_DISTRIBUTION/modules/
if present:
- org/codehaus/groovy/groovy-all
3. Update Camunda Web Applications
The following steps are required to update the Camunda REST API on a JBoss/Wildfly instance:
- Undeploy an existing web application with a name like camunda-engine-rest
- Download the REST API web application archive from our . Alternatively, switch to the private repository forthe enterprise version (credentials from license required). Choose the correct version named $PLATFORM_VERSION/camunda-engine-rest-$PLATFORM_VERSION.war.
- Deploy the web application archive to your JBoss/Wildfly instance.
The following steps are required to update the Camunda web applications Cockpit, Tasklist, and Admin on a JBoss/Wildfly instance:
- Undeploy an existing web application with a name like camunda-webapp
- Download the Camunda web application archive from our Maven Nexus Server.Alternatively, switch to the private repository for the enterprise version (credentials from license required).Choose the correct version named $PLATFORM_VERSION/camunda-webapp-jboss.war.