Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
123 lines (84 sloc) 5.94 KB
title menu
Update a JBoss/Wildfly Installation from 7.5 to 7.6
main
name identifier parent
JBoss AS/Wildfly
migration-guide-75-jboss
migration-guide-75

The following steps describe how to update the Camunda artifacts on a JBoss AS 7, Wildfly 8 and Wildfly 10 server in a shared process engine scenario. For the entire procedure, refer to the [update guide][update-guide]. If not already done, make sure to download the Camunda BPM 7.6 JBoss distribution, Camunda BPM 7.6 Wildfly 8 or Camunda BPM 7.6 Wildfly 10 distribution. In the following instructions $APP_SERVER should be replaced with either jboss or wildfly, depending on the used application server.

The update procedure takes the following steps:

  1. Update the Camunda BPM Modules
  2. Update Optional Camunda BPM Modules
  3. 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.

{{< note title="Updated Wildfly Version" class="info" >}} The pre-built Camunda 7.6 distribution ships with Wildfly 8, alternatively with Wildfly 10. In particular, Camunda 7.6 is supported on Wildfly 8.2 and 10.1 such that a Wildfly update is not required when migrating from 7.5 to 7.6.

See the Wildfly migration guide for any Wildfly-specific migration notes and procedures. {{< /note >}}

1. Update the Camunda BPM Modules

Replace the following modules from the folder $APP_SERVER_HOME/modules/ with their new versions from the folder $APP_SERVER_DISTRIBUTION/modules/:

  • org/camunda/bpm/camunda-engine
  • org/camunda/bpm/$APP_SERVER/camunda-$APP_SERVER-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/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:

LDAP Integration

Replace the following module from the folder $APP_SERVER_HOME/modules/ with its new version from the folder $APP_SERVER_DISTRIBUTION/modules/, if present:

  • org/camunda/bpm/identity/camunda-identity-ldap

Camunda Connect

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/connect/camunda-connect-core
  • org/camunda/connect/camunda-connect-http
  • org/camunda/connect/camunda-connect-soap-http
  • org/camunda/bpm/camunda-engine-plugin-connect

Camunda Spin

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-annotations
  • com/fasterxml/jackson/core/jackson-core
  • com/fasterxml/jackson/core/jackson-databind

Groovy Scripting

Replace the following module from the folder $APP_SERVER_HOME/modules/ with its new version from the folder $APP_SERVER_DISTRIBUTION/modules/ if present:

  • org/codehaus/groovy/groovy-all

3. Update Camunda Web Applications

Update REST API

The following steps are required to update the Camunda REST API on a JBoss/Wildfly instance:

  1. Undeploy an existing web application with a name like camunda-engine-rest
  2. Download the REST API web application archive from our [Maven Nexus Server][engine-rest]. Alternatively, switch to the private repository for the enterprise version (credentials from license required). Choose the correct version named $PLATFORM_VERSION/camunda-engine-rest-$PLATFORM_VERSION.war.
  3. 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:

  1. Undeploy an existing web application with a name like camunda-webapp
  2. Download the Camunda web application archive from our [Maven Nexus Server][webapp-jboss]. 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.
  3. Deploy the web application archive to your JBoss/Wildfly instance.

[jboss-threads-to-camunda-mapping-table]: {{< ref "/update/minor/75-to-76/jboss.md#jboss-threads-to-camunda-subsystem-mapping-table" >}} [update-guide]: {{< ref "/update/minor/75-to-76/_index.md" >}} [jboss-distro]: https://app.camunda.com/nexus/service/rest/repository/browse/public/org/camunda/bpm/jboss/camunda-bpm-jboss/ [wildfly-distro]: https://app.camunda.com/nexus/service/rest/repository/browse/public/org/camunda/bpm/wildfly/camunda-bpm-wildfly/ [engine-rest]: https://app.camunda.com/nexus/service/rest/repository/browse/public/org/camunda/bpm/camunda-engine-rest/ [webapp-jboss]: https://app.camunda.com/nexus/service/rest/repository/browse/public/org/camunda/bpm/webapp/camunda-webapp-jboss/ [jboss-container-integration]: {{< ref "/user-guide/runtime-container-integration/jboss.md" >}}

You can’t perform that action at this time.