Update a WildFly / JBoss EAP Installation from 2.0 to 2.1

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_HOME points to the JBoss EAP/WildFly application server main directory.
  • $WILDFLY_DISTRIBUTION represents the downloaded pre-packaged CIB seven distribution for WildFly, e.g. cibseven-bpm-wildfly-$PLATFORM_VERSION.zip or cibseven-bpm-wildfly-$PLATFORM_VERSION.tar.gz.
  • $PLATFORM_VERSION denotes the version of CIB seven you want to install or already have installed, e.g. 2.0.0.

If not already done, download accordingly:

The update procedure takes the following steps:

  1. Update the CIB seven modules.
  2. Update optional CIB seven modules.
  3. 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-engine
  • org/cibseven/bpm/wildfly/cibseven-wildfly-subsystem
  • org/cibseven/bpm/model/cibseven-bpmn-model
  • org/cibseven/bpm/model/cibseven-cmmn-model
  • org/cibseven/bpm/model/cibseven-dmn-model
  • org/cibseven/bpm/model/cibseven-xml-model
  • org/cibseven/bpm/dmn/cibseven-engine-dmn
  • org/cibseven/bpm/dmn/cibseven-engine-feel-api
  • org/cibseven/bpm/dmn/cibseven-engine-feel-juel
  • org/cibseven/bpm/dmn/cibseven-engine-feel-scala
  • org/cibseven/bpm/juel/cibseven-juel
  • org/cibseven/template-engines/cibseven-template-engines-freemarker
  • org/cibseven/commons/cibseven-commons-logging
  • org/cibseven/commons/cibseven-commons-typed-values
  • org/cibseven/commons/cibseven-commons-utils
  • org/cibseven/connect/cibseven-connect-core
  • org/cibseven/connect/cibseven-connect-http-client
  • org/cibseven/connect/cibseven-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, CIB seven 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 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-core
  • org/cibseven/spin/cibseven-spin-dataformat-json-jackson
  • org/cibseven/spin/cibseven-spin-dataformat-xml-dom-jakarta
    • Heads-up: add this module only for WildFly / JBoss EAP 8.
  • org/cibseven/bpm/cibseven-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 CIB seven webclient

Update REST API

The following steps are required to update the CIB seven REST API on a JBoss/WildFly instance:

  1. Undeploy an existing web application with a name like cibseven-engine-rest.
  2. 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).
  3. Deploy the 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:

  1. Un-deploy an existing web application with a name like cibseven-webclient.
  2. 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).
  3. Deploy the web application archive to your JBoss/WildFly instance.

On this Page: