Update a WildFly / JBoss EAP Installation from 7.23 to 7.24
The following steps describe how to update the Camunda artifacts on a WildFly/JBoss EAP in a shared process engine scenario. Throughout the procedure, refer to the update guide.
Reading this Guide
This guide uses a number of variables to denote common path names and constants:
- $WILDFLY_HOMEpoints to the JBoss EAP/WildFly application server main directory.
- $WILDFLY_DISTRIBUTIONrepresents the downloaded pre-packaged Camunda 7 distribution for WildFly, e.g.- camunda-bpm-wildfly-$PLATFORM_VERSION.zipor- camunda-bpm-wildfly-$PLATFORM_VERSION.tar.gz.
- $PLATFORM_VERSIONdenotes the version of Camunda 7 you want to install or already have installed, e.g.- 7.0.0.
If not already done, download accordingly:
- For WildFly / JBoss EAP 8 - the Camunda 7 WildFly distribution.
The update procedure takes the following steps:
- Update the Camunda 7 modules.
- Update optional Camunda 7 modules.
- Update Camunda web applications.
Whenever the instructions are to replace a module, delete the previous version of the module first to avoid orphan jars.
1. Update the Camunda 7 modules
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the new versions from the folder $WILDFLY_DISTRIBUTION/modules/:
- org/camunda/bpm/camunda-engine
- org/camunda/bpm/wildfly/camunda-wildfly-subsystem
- org/camunda/bpm/model/camunda-bpmn-model
- 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/bpm/dmn/camunda-engine-feel-scala
- org/camunda/bpm/juel/camunda-juel
- org/camunda/template-engines/camunda-template-engines-freemarker
- org/camunda/commons/camunda-commons-logging
- org/camunda/commons/camunda-commons-typed-values
- org/camunda/commons/camunda-commons-utils
- org/camunda/connect/camunda-connect-core
- org/camunda/connect/camunda-connect-http-client
- org/camunda/connect/camunda-connect-soap-http-client
- org/camunda/feel/feel-engine
- org/apache/httpcomponents/client5/httpclient5
- org/apache/httpcomponents/core5/httpcore5
- org/freemarker/freemarker
- org/mybatis/mybatis
- org/graalvm/js/js
- org/graalvm/js/js-scriptengine
- org/graalvm/regex/regex
- org/graalvm/sdk/graal-sdk
- org/graalvm/truffle/truffle-api
- com/ibm/icu/icu4j
Apache HTTP Client Migration
As part of the 7.23 to 7.24 migration, Camunda Connect has been upgraded from Apache HttpClient 4.x to 5.x. The old modules org/apache/httpcomponents/httpclient, org/apache/httpcomponents/httpcore, and commons-codec/commons-codec are no longer needed and should be removed. They are replaced by the new HttpClient 5.x modules listed above.
2. Update optional Camunda 7 modules
In addition to the core modules, there may be optional artifacts in $WILDFLY_HOME/modules/ for LDAP integration, Camunda Connect, Camunda Spin, Groovy and Graal scripting.
If you use any of these extensions, the following update steps apply:
LDAP integration
Replace the following module from the folder $WILDFLY_HOME/modules/ with its new version from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
- org/camunda/bpm/identity/camunda-identity-ldap
Camunda Connect plugin
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the new versions from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
- org/camunda/bpm/camunda-engine-plugin-connect
Camunda Spin
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the new versions from the folder $WILDFLY_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-jakarta- Heads-up: add this module only for WildFly / JBoss EAP 8.
 
- org/camunda/bpm/camunda-engine-plugin-spin
Additionally, replace the following dependent modules:
- com/fasterxml/jackson/core/jackson-annotations
- com/fasterxml/jackson/core/jackson-core
- com/fasterxml/jackson/core/jackson-databind
- com/jayway/jsonpath/json-path
- net/minidev/accessors-smart
- net/minidev/json-smart
GraalVM JavaScript
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the following
modules from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
- com/ibm/icu/icu4j
- org/graalvm/js/js
- org/graalvm/js/js-scriptengine
- org/graalvm/regex/regex
- org/graalvm/sdk/graal-sdk
- org/graalvm/truffle/truffle-api
Groovy
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the following
modules from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
- org/codehaus/groovy/groovy-all
- org/codehaus/groovy/groovy
- org/codehaus/groovy/groovy-jsr223
- org/codehaus/groovy/groovy-json
- org/codehaus/groovy/groovy-xml
- org/codehaus/groovy/groovy-templates
3. Update Camunda web applications
Update REST API
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 Maven Artifactory.
Alternatively, switch to the private repository for the enterprise version (credentials from license required).
- For WildFly / JBoss EAP 8, the name of the artifact is $PLATFORM_VERSION/camunda-engine-rest-jakarta-$PLATFORM_VERSION-wildfly.war.
 
- For WildFly / JBoss EAP 8, the name of the artifact is 
- Deploy the web application archive to your JBoss/WildFly instance.
Update Cockpit, Tasklist, and Admin
The following steps are required to update the Camunda web applications Cockpit, Tasklist, and Admin on a JBoss/WildFly instance:
- Un-deploy an existing web application with a name like camunda-webapp.
- Download the Camunda web application that contains the web applications from our Maven Artifactory.
Alternatively, switch to the private repository for the enterprise version (credentials from license required).
- For WildFly / JBoss EAP 8, the name of the artifact is $PLATFORM_VERSION/camunda-webapp-wildfly-$PLATFORM_VERSION.war.
 
- For WildFly / JBoss EAP 8, the name of the artifact is 
- Deploy the web application archive to your JBoss/WildFly instance.