Update a Tomcat Installation from 2.0 to 2.1

The following steps describe how to update the CIB seven artifacts on a Tomcat server in a shared process engine setting.

Throughout the procedure, refer to the update guide. If not already done, download the CIB seven 2.1 Tomcat distribution.

The update procedure takes the following steps:

  1. Update the CIB seven core libraries.
  2. Update optional CIB seven libraries.
  3. Update web applications.

In each of the following steps, the identifier $*_VERSION refers to the current versions and the new versions of the artifacts.

1. Update the CIB seven core libraries

Replace the following libraries in the folder $TOMCAT_HOME/lib/ with the new versions from the folder $TOMCAT_DISTRIBUTION/lib/:

  • cibseven-engine-$PLATFORM_VERSION.jar
  • cibseven-bpmn-model-$PLATFORM_VERSION.jar
  • cibseven-cmmn-model-$PLATFORM_VERSION.jar
  • cibseven-dmn-model-$PLATFORM_VERSION.jar
  • cibseven-xml-model-$PLATFORM_VERSION.jar
  • cibseven-engine-dmn-$PLATFORM_VERSION.jar
  • cibseven-engine-feel-api-$PLATFORM_VERSION.jar
  • cibseven-engine-feel-juel-$PLATFORM_VERSION.jar
  • cibseven-engine-feel-scala-$PLATFORM_VERSION.jar
  • cibseven-juel-$PLATFORM_VERSION.jar
  • cibseven-commons-logging-$PLATFORM_VERSION.jar
  • cibseven-commons-typed-values-$PLATFORM_VERSION.jar
  • cibseven-commons-utils-$PLATFORM_VERSION.jar
  • cibseven-connect-connectors-all-$PLATFORM_VERSION.jar
  • cibseven-connect-core-$PLATFORM_VERSION.jar
  • cibseven-template-engines-freemarker-$PLATFORM_VERSION.jar
  • feel-engine-$FEEL_ENGINE_VERSION-scala-shaded.jar
  • freemarker-$FREEMARKER_VERSION.jar
  • mybatis-$MYBATIS_VERSION.jar

2. Update optional CIB seven libraries

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

LDAP integration

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

  • cibseven-identity-ldap-$PLATFORM_VERSION.jar

CIB seven Connect plugin

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

  • cibseven-engine-plugin-connect-$PLATFORM_VERSION.jar

CIB seven Spin

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

  • cibseven-spin-dataformat-all-$PLATFORM_VERSION.jar
  • cibseven-spin-core-$PLATFORM_VERSION.jar
  • cibseven-engine-plugin-spin-$PLATFORM_VERSION.jar

GraalVM JavaScript

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

  • graal-sdk-$GRAAL_VERSION.jar
  • icu4j-$ICU4J_VERSION.jar
  • js-$GRAAL_VERSION.jar
  • js-scriptengine-$GRAAL_VERSION.jar
  • regex-$GRAAL_VERSION.jar
  • truffle-api-$GRAAL_VERSION.jar

Groovy

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

  • groovy-$GROOVY_VERSION.jar
  • groovy-jsr223-$GROOVY_VERSION.jar
  • groovy-json-$GROOVY_VERSION.jar
  • groovy-xml-$GROOVY_VERSION.jar
  • groovy-templates-$GROOVY_VERSION.jar

3. Update CIB seven webclient

Update REST API

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

  1. Undeploy an existing web application with a name like cibseven-engine-rest.
  2. 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).
  3. Download the CIB seven webclient archive from our Artifact Repository. Alternatively, switch to the private repository for the enterprise version (credentials from license required).
  4. Deploy the webclient archive to your Tomcat instance.

CIB seven webclient

The following steps are required to update the CIB seven webclient on a Tomcat instance:

  1. Undeploy an existing web application with a name like camunda-webapp.
  2. Download the Camunda web application archive from our Artifact Repository. Alternatively, switch to the private repository for the enterprise version (credentials from license required).
  3. Deploy the web application archive to your Tomcat instance.

On this Page: