Update a WildFly / JBoss EAP Installation from 2.2 to 3.0
The following steps describe how to update the CIB seven 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 CIB seven distribution for WildFly, e.g.cibseven-bpm-wildfly-$PLATFORM_VERSION.ziporcibseven-bpm-wildfly-$PLATFORM_VERSION.tar.gz.$PLATFORM_VERSIONdenotes the version of CIB seven you want to install or already have installed, e.g.3.0.0.
If not already done, download accordingly:
- For WildFly / JBoss EAP 8 - the CIB seven WildFly distribution.
The update procedure takes the following steps:
- Update the CIB seven modules.
- Update optional CIB seven modules.
- Update CIB seven webclient.
Whenever the instructions are to replace a module, delete the previous version of the module first to avoid orphan jars.
1. Update the CIB seven modules
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the new versions from the folder $WILDFLY_DISTRIBUTION/modules/:
org/cibseven/bpm/cibseven-engineorg/cibseven/bpm/wildfly/cibseven-wildfly-subsystemorg/cibseven/bpm/model/cibseven-bpmn-modelorg/cibseven/bpm/model/cibseven-cmmn-modelorg/cibseven/bpm/model/cibseven-dmn-modelorg/cibseven/bpm/model/cibseven-xml-modelorg/cibseven/bpm/dmn/cibseven-engine-dmnorg/cibseven/bpm/dmn/cibseven-engine-feel-apiorg/cibseven/bpm/dmn/cibseven-engine-feel-juelorg/cibseven/bpm/dmn/cibseven-engine-feel-scalaorg/cibseven/bpm/juel/cibseven-juelorg/cibseven/template-engines/cibseven-template-engines-freemarkerorg/cibseven/commons/cibseven-commons-loggingorg/cibseven/commons/cibseven-commons-typed-valuesorg/cibseven/commons/cibseven-commons-utilsorg/cibseven/connect/cibseven-connect-coreorg/cibseven/connect/cibseven-connect-http-clientorg/cibseven/connect/cibseven-connect-soap-http-clientorg/camunda/feel/feel-engineorg/apache/httpcomponents/client5/httpclient5org/apache/httpcomponents/core5/httpcore5org/freemarker/freemarkerorg/mybatis/mybatiscom/ibm/icu/icu4j
In addition, replace all GraalVM modules as described in the next section. Their set has changed in this release.
GraalVM JavaScript modules
The set of modules has changed
CIB seven 3.0 ships GraalVM JavaScript 25.0.1 instead of the 21.3 line, see Java 25 and GraalJS 25. The runtime is split into considerably more modules than before, and the module descriptors of the existing ones have changed as well. Replacing only the modules that are already present leaves WildFly with an inconsistent module graph, and the server fails to boot with a ModuleLoadError.
Delete the whole folder $WILDFLY_HOME/modules/org/graalvm/ and copy $WILDFLY_DISTRIBUTION/modules/org/graalvm/ in its place.
The resulting module set is:
org/graalvm/js/js- contains only amodule.xml; it aggregates the modules beloworg/graalvm/js/js-language- new, holds the JavaScript language implementation that used to be injsorg/graalvm/js/js-scriptengineorg/graalvm/regex/regexorg/graalvm/polyglot/polyglot- neworg/graalvm/sdk/graal-sdk- contains only amodule.xmlafter this updateorg/graalvm/sdk/collections- neworg/graalvm/sdk/jniutils- neworg/graalvm/sdk/nativeimage- neworg/graalvm/sdk/word- neworg/graalvm/truffle/truffle-apiorg/graalvm/truffle/truffle-compiler- neworg/graalvm/truffle/truffle-runtime- neworg/graalvm/shadowed/icu4j- neworg/graalvm/shadowed/xz- new
Keep the module com/ibm/icu/icu4j as well. It carries the public ICU4J library (com.ibm.icu:icu4j, version 71.1) that scripts can use through Java interop, and it is not the same as the new org/graalvm/shadowed/icu4j, which is GraalVM’s internal shaded copy. See Java 25 and GraalJS 25.
2. Update optional CIB seven modules
In addition to the core modules, there may be optional artifacts in $WILDFLY_HOME/modules/ for LDAP integration, CIB seven Connect, CIB seven 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/cibseven/bpm/identity/cibseven-identity-ldap
CIB seven 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/cibseven/bpm/cibseven-engine-plugin-connect
CIB seven Spin
Replace the following modules from the folder $WILDFLY_HOME/modules/ with the new versions from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
org/cibseven/spin/cibseven-spin-coreorg/cibseven/spin/cibseven-spin-dataformat-json-jacksonorg/cibseven/spin/cibseven-spin-dataformat-xml-dom- Heads-up: in 2.2 this module was named
cibseven-spin-dataformat-xml-dom-jakarta. The old name stays as an alias, so existing deployments keep working, see Java EE variants and Tomcat 9, WildFly 26 and WildFly 28 distributions removed.
- Heads-up: in 2.2 this module was named
org/cibseven/bpm/cibseven-engine-plugin-spin
Additionally, replace the following dependent modules:
com/fasterxml/jackson/core/jackson-annotationscom/fasterxml/jackson/core/jackson-corecom/fasterxml/jackson/core/jackson-databindtools/jackson/core/jackson-core- new, Spin JSON uses Jackson 3 in 3.0tools/jackson/core/jackson-databind- new, Spin JSON uses Jackson 3 in 3.0com/jayway/jsonpath/json-pathnet/minidev/accessors-smartnet/minidev/json-smart
The slot of the Jackson modules has changed
In 2.2 these Jackson modules carried the slot of their Jackson version, for example 2.21.7. In 3.0 their slot is cibseven. A process application whose jboss-deployment-structure.xml names one of them with the old slot does not deploy and fails with WFLYSRV0179: Failed to load module, see Jackson 3.
GraalVM JavaScript
The GraalVM JavaScript modules are listed in step 1. Replace the complete folder org/graalvm/ and keep com/ibm/icu/icu4j, as described there.
Groovy
Replace the following module from the folder $WILDFLY_HOME/modules/ with the new version from the folder $WILDFLY_DISTRIBUTION/modules/, if present:
org/apache/groovy/groovy-all
3. Update CIB seven webclient
Update REST API
The following steps are required to update the CIB seven REST API on a JBoss/WildFly instance:
- Undeploy an existing web application with a name like
engine-restorcibseven-engine-rest. - Download the REST API web application archive from our Artifact Repository. Alternatively, switch to the private repository for the enterprise version (credentials from license required).
- Deploy the REST API web application archive to your JBoss/WildFly instance.
CIB seven webclient
The following steps are required to update the CIB seven webclient on a JBoss/WildFly instance:
- Un-deploy an existing web application with a name like
webappor ‘cibseven-webclient-web’. - Download the CIB seven webclient archive from our Artifact Repository. Alternatively, switch to the private repository for the enterprise version (credentials from license required).
- Deploy the webclient archive to your JBoss/WildFly instance.