This document will guide you through the installation of Camunda BPM and its components on an Oracle WebLogic Application Server.
Enterprise Feature
Please note that this feature is only included in the enterprise edition of the Camunda BPM platform, it is not available in the community edition.Check the Camunda enterprise homepage for more information or get your free trial version.
Reading the Guide
Throughout this guide we will use a number of variables to denote common path names and constants.$WLS_DOMAIN_HOME
points to the Oracle WebLogic application server domain directory (typically something like /opt/oracle/WebLogic/domains/mydomain
). $PLATFORM_VERSION
denotes the version of the Camunda BPM platform you want to or have installed, e.g. 7.0.0
. $WLS_DISTRIBUTION
represents the downloaded Camunda BPM distribution for the Oracle WebLogic Application Server, e.g., camunda-ee-oracle-wls-$PLATFORM_VERSION.zip
.
The distribution is available at the Camunda enterprise release page. You will be asked to enter the credentials you received during the trial or subscription process.
The camunda BPM platform requires a set of resources that need to be configured at the application server level:
The camunda BPM platform uses one or multiple process engines. Use the Oracle WebLogic Server Administration Console for the configuration of the datasources. The JNDI name of the datasource must be equal to the name used in the datasource-Element of the process engine(s) configured in the bpm-platform.xml.
The default JNDI name is jdbc/ProcessEngine
The following screenshot shows the mandatory configuration of a datasource for camunda bpm:
In this section we explain how to add a datasource using the Oracle WebLogic Server Administration Console:
Note that you can configure multiple datasources used by different process engine instances. See the User Guide for details.
The Camunda BPM platform includes one module in the modules folder of the distribution:
camunda-ee-oracle-wls-$PLATFORM_VERSION.zip
|-- modules/
|-- camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
The camunda-oracle-weblogic-ear
is a Java EE application providing the Camunda BPM platform services. It contains an embedded JCA Resource Adapter, the camunda-oracle-weblogic-rar, which provides the jobexecutor service to the camunda BPM platform.
It must be installed to your Oracle Weblogic Application Server.
In this section, we explain how the camunda-oracle-weblogic-ear module can be installed using the Oracle WebLogic Server Administration Console.
The installation process is composed of two steps:
camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
EAR file.camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
EAR file.First the camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
RAR file must be installed:
camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
from the modules folder of the camunda BPM platform for Oracle WebLogic Application Server distribution and continue to the "Next" page.Fill in camunda-bpm-platform
as name for the enterprise application deployment. This setting is mandatory and MUST NOT be changed.
Continue to the "Next" page.
Example: Deployment order set to "90".
camunda-oracle-weblogic-rar.rar
entry. Click on the "Configuration" tab on the following page.Now you can start the camunda-bpm-platform application if it is not already running. If this initially fails, try to restart the server.
Example: Finished configuration of the JCA Work Manager used by the resource adapter.
The Camunda REST API WAR file resides under webapps/camunda-engine-rest-$PLATFORM_VERSION-wls.war
in the Oracle WebLogic Application Server distribution archive.
In this section we explain how to install the WAR file using the Oracle WebLogic Server Administration Console:
camunda-engine-rest-$PLATFORM_VERSION-wls.war
file from the distribution and upload it.After completing the wizard, the REST API should be successfully installed on the application server. The context root for the REST API is /engine-rest by default. In some situations, you also have to start the web application manually from the Domain Structure / YOUR_DOMAIN / Deployments page.
The web application archive that contains camunda Cockpit and Tasklist resides under webapps/camunda-webapp-ee-wls-$PLATFORM_VERSION.war
in the Oracle WebLogic Application Server distribution archive.
In this section we explain how to install the WAR file using the Oracle WebLogic Server Administration Console:
camunda-webapp-ee-wls-$PLATFORM_VERSION.war
file from the distribution and upload it.After completing the wizard, the Cockpit and Tasklist should be accessible on the default context path /camunda. In some situations, you also have to start the web application manually from the Domain Structure / YOUR_DOMAIN / Deployments page.
You can check if everything went well by accessing Cockpit, Tasklist and Admin via /camunda/app/cockpit
, /camunda/app/tasklist
and /camunda/app/admin
or under the context path you configured.
In order to setup LDAP for the Oracle WebLogic distribution, you have to perform the following steps:
Make sure the camunda-identity-ldap-$PLATFORM_VERSION.jar
is present in the $WLS_DOMAIN_HOME/lib
folder.
Edit the file bpm-platform.xml
located inside the Camunda BPM enterprise archive at camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear/camunda-oracle-weblogic-service.jar/META-INF/
and add the LDAP Identity Provider Plugin and the Administrator Authorization Plugin.
<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform xmlns="http://www.camunda.org/schema/1.0/BpmPlatform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.camunda.org/schema/1.0/BpmPlatform http://www.camunda.org/schema/1.0/BpmPlatform ">
...
<process-engine name="default"> ...
<properties>...</properties>
<plugins>
<plugin>
<class>org.camunda.bpm.identity.impl.ldap.plugin.LdapIdentityProviderPlugin</class>
<properties>
<property name="serverUrl">ldap://localhost:4334/</property>
<property name="managerDn">uid=jonny,ou=office-berlin,o=camunda,c=org</property>
<property name="managerPassword">s3cr3t</property>
<property name="baseDn">o=camunda,c=org</property>
<property name="userSearchBase"></property>
<property name="userSearchFilter">(objectclass=person)</property>
<property name="userIdAttribute">uid</property>
<property name="userFirstnameAttribute">cn</property>
<property name="userLastnameAttribute">sn</property>
<property name="userEmailAttribute">mail</property>
<property name="userPasswordAttribute">userpassword</property>
<property name="groupSearchBase"></property>
<property name="groupSearchFilter">(objectclass=groupOfNames)</property>
<property name="groupIdAttribute">ou</property>
<property name="groupNameAttribute">cn</property>
<property name="groupMemberAttribute">member</property>
</properties>
</plugin>
<plugin>
<class>org.camunda.bpm.engine.impl.plugin.AdministratorAuthorizationPlugin</class>
<properties>
<property name="administratorUserName">admin</property>
</properties>
</plugin>
</plugins>
</process-engine>
</bpm-platform>
The administratorUserName
property should contain the user id of the LDAP user you want to grant administrator authorizations to. You can then use this user to log into the web application and grant authorizations to additional users.
See our user guide for complete documentation on the LDAP Identity Provider Plugin and the Administrator Authorization Plugin.
If you use LDAP as Indentity Provider, you should consider activating caching of
Users and Groups in the camunda webapplication. In order to activate this, add the following
configuration to the web.xml
file of camunda webapplication
(camunda-webapp-wls-$PLATFORM_VERSION.war/WEB-INF/web.xml
):
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<!-- ... -->
<listener>
<listener-class>org.camunda.bpm.engine.rest.hal.cache.HalRelationCacheBootstrap</listener-class>
</listener>
<context-param>
<param-name>org.camunda.bpm.engine.rest.hal.cache.config</param-name>
<param-value>
{
"cacheImplementation": "org.camunda.bpm.engine.rest.hal.cache.DefaultHalResourceCache",
"caches": {
"org.camunda.bpm.engine.rest.hal.user.HalUser": {
"capacity": 100,
"secondsToLive": 900
},
"org.camunda.bpm.engine.rest.hal.group.HalGroup": {
"capacity": 100,
"secondsToLive": 900
}
}
}
</param-value>
</context-param>
<!-- ... -->
</web-app>
The following steps describe how to upgrade the Camunda artifacts on an Oracle WebLogic application server in a shared process engine setting. For the entire migration procedure, refer to the migration guide. If not already done, make sure to download the Camunda BPM 7.2 Oracle WebLogic distribution.
The upgrade procedure takes the following steps:
In each of the following steps, the identifiers $*_VERSION
refer to the current version and the new versions of the artifacts.
Changing Platform Configuration
Depending on your chosen feature set for Camunda BPM, some of the (optional) migration steps may require to change the configuration of the BPM platform. The Camunda enterprise archive (EAR) contains a default platform configuration. If you want to change this configuration, you can replace it as described in the deployment descriptor reference.
First, uninstall the Camunda web applications, namely the Camunda REST API (artifact name like camunda-engine-rest
) and the Camunda applications Cockpit, Tasklist and Admin (artifact name like camunda-webapp
).
Uninstall the camunda EAR. Its name should be camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
. Then, uninstall the Camunda job executor adapter, called camunda-oracle-weblogic-$PLATFORM_VERSION.rar
.
After shutting down the server, replace the following libraries in $WLS_DOMAIN_HOME/lib
with their equivalents from $WLS_DISTRIBUTION/modules/lib
:
camunda-engine-$PLATFORM_VERSION.jar
camunda-bpmn-model-$PLATFORM_VERSION.jar
camunda-xml-model-$PLATFORM_VERSION.jar
mybatis-$MYBATIS_VERSION.jar
If present, also replace the following optional artifact:
camunda-identity-ldap-$PLATFORM_VERSION.jar
Add the following library from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
:
camunda-cmmn-model-$PLATFORM_VERSION.jar
There are artifacts for Camunda Connect, Camunda Spin, the Freemarker template language and Groovy scripting that may optionally be added to the shared library folder. Since all these artifacts add new functionality, the following steps are not required for migration.
Note: The default Camunda configuration file contained by the Camunda EAR automatically activates the newly introduced, optional Camunda dependencies, Camunda Spin and Connect. If you do not use a custom BPM platform configuration as described here and do not intend to do so, you must install the Camunda Spin and Connect core libraries to the shared libraries folder.
Not Using Connect/Spin
If you do not want to use Camunda Connect or Camunda Spin, you cannot use the default BPM platform configuration that is contained in the Camunda EAR. In this case, make sure to change the configuration location as described here. As a starting point, you can copy the default configuration from $WLS_DISTRIBUTION/modules/camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear/camunda-oracle-weblogic-service-$PLATFORM_VERSION.jar/META-INF/bpm-platform.xml
and remove the <plugin/>
entries for the classes ConnectProcessEnginePlugin
and SpinProcessEnginePlugin
.
If Camunda Connect is intended to be used, copy the following library from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
:
camunda-connect-core-$CONNECT_VERSION.jar
camunda-commons-logging-$COMMONS_VERSION.jar
camunda-commons-utils-$COMMONS_VERSION.jar
slf4j-api-$SLF4J_VERSION.jar
slf4j-jdk14-$SLF4J_VERSION.jar
If you use a custom BPM platform configuration file, Camunda Connect functionality has to be activated for a process engine by registering a process engine plugin (note that if you use the default configuration, this step is not necessary):
<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform ... ">
<process-engine name="default">
...
<plugins>
... existing plugins ...
<plugin>
<class>org.camunda.connect.plugin.impl.ConnectProcessEnginePlugin</class>
</plugin>
</plugins>
...
</process-engine>
</bpm-platform>
If Camunda Spin is intended to be used, copy the following library from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
:
camunda-spin-core-$CONNECT_VERSION.jar
camunda-commons-logging-$COMMONS_VERSION.jar
camunda-commons-utils-$COMMONS_VERSION.jar
slf4j-api-$SLF4J_VERSION.jar
slf4j-jdk14-$SLF4J_VERSION.jar
If you use a custom BPM platform configuration file, Camunda Spin functionality has to be activated for a process engine by registering a process engine plugin (note that if you use the default configuration, this step is not necessary):
<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform ... ">
<process-engine name="default">
...
<plugins>
... existing plugins ...
<plugin>
<class>org.camunda.spin.plugin.impl.SpinProcessEnginePlugin</class>
</plugin>
</plugins>
...
</process-engine>
</bpm-platform>
If Groovy is to be used as a scripting language, add the following artifacts to the folder $WLS_DOMAIN_HOME/lib
:
groovy-all-$GROOVY_VERSION.jar
If the Camunda integration for Freemarker is intended to be used, add the following artifacts to the folder $WLS_DOMAIN_HOME/lib
:
camunda-template-engines-freemarker-$TEMPLATE_VERSION.jar
freemarker-2.3.20.jar
camunda-commons-logging-$COMMONS_VERSION.jar
camunda-commons-utils-$COMMONS_VERSION.jar
slf4j-api-$SLF4J_VERSION.jar
As of 7.2, the default behavior of script variables has changed. Script variables are set in e.g. a BPMN Script Task that uses a language such as JavaScript or Groovy. In previous versions, the process engine automatically stored all script variables as process variables. Starting with 7.2, this behavior has changed and the process engine does not automatically store script variables any longer. You can re-enable the legacy behavior by setting the boolean property autoStoreScriptVariables
to true
for any process engine in the bpm-platform.xml
:
<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform ... ">
...
<process-engine name="default">
...
<properties>
... existing properties ...
<property name="autoStoreScriptVariables">true</property>
</properties>
...
</process-engine>
...
</bpm-platform>
As an alternative, process application developers can migrate script code by replacing all implicit declarations of process variables in their scripts with an explicit call to execution.setVariable('varName', 'value')
.
Install the Camunda EAR, i.e., the file $WLS_DISTRIBUTION/modules/camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
.
As of version 7.2, the Camunda job executor resource adapter (RAR) that you uninstalled in step 1 is part of the Camunda EAR and therefore does not need to be installed separately.
Deploy the web application $WLS_DISTRIBUTION/webapps/camunda-engine-rest-$PLATFORM_VERSION-wls.war
to your Oracle WebLogic instance.
Deploy the web application $WLS_DISTRIBUTION/webapps/camunda-webapp-ee-wls-$PLATFORM_VERSION.war
to your Oracle WebLogic instance.
LDAP Entity Caching
With 7.2, it is possible to enable entity caching for Hypertext Application Language (HAL) requests that the Camunda web applications make. This can be especially useful when you use Camunda in combination with LDAP. To activate caching, the Camunda webapp artifact has to be modified and the pre-built application cannot be used as is. See the REST Api Documentation for details.
The following steps describe how to upgrade the Camunda artifacts on an Oracle WebLogic application server in a shared process engine setting. For the entire migration procedure, refer to the migration guide. If not already done, make sure to download the Camunda BPM 7.3 Oracle WebLogic distribution.
The upgrade procedure takes the following steps:
In each of the following steps, the identifiers $*_VERSION
refer to the current version and the new versions of the artifacts.
First, uninstall the Camunda web applications, namely the Camunda REST API (artifact name like camunda-engine-rest
) and the Camunda applications Cockpit, Tasklist and Admin (artifact name like camunda-webapp
).
Uninstall the camunda EAR. Its name should be camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
.
After shutting down the server, replace the following libraries in $WLS_DOMAIN_HOME/lib
with their equivalents from $WLS_DISTRIBUTION/modules/lib
:
camunda-engine-$PLATFORM_VERSION.jar
camunda-bpmn-model-$PLATFORM_VERSION.jar
camunda-cmmn-model-$PLATFORM_VERSION.jar
camunda-xml-model-$PLATFORM_VERSION.jar
In addition to the core libraries, there may be optional artifacts in $WLS_DOMAIN_HOME/lib
for LDAP integration, Camunda Connect, and Camunda Spin. If you use any of these extensions, the following upgrade steps apply:
Copy the following libraries from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
if present:
camunda-identity-ldap-$PLATFORM_VERSION.jar
Copy the following libraries from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
if present:
camunda-connect-core-$CONNECT_VERSION.jar
Copy the following libraries from $WLS_DISTRIBUTION/modules/lib
to the folder $WLS_DOMAIN_HOME/lib
if present:
camunda-spin-core-$SPIN_VERSION.jar
If you have previously replaced the default BPM platform configuration by a custom configuration following any of the ways outlined in the deployment descriptor reference, it may be necessary to restore this configuration. This can be done by repeating the configuration replacement steps for the upgraded platform.
Install the Camunda EAR, i.e., the file $WLS_DISTRIBUTION/modules/camunda-oracle-weblogic-ear-$PLATFORM_VERSION.ear
.
Deploy the web application $WLS_DISTRIBUTION/webapps/camunda-engine-rest-$PLATFORM_VERSION-wls.war
to your Oracle WebLogic instance.
Deploy the web application $WLS_DISTRIBUTION/webapps/camunda-webapp-ee-wls-$PLATFORM_VERSION.war
to your Oracle WebLogic instance.
LDAP Entity Caching
Beginning with 7.2, it is possible to enable entity caching for Hypertext Application Language (HAL) requests that the Camunda web applications make. If you have previously used caching, you can enable this feature by modifying the Camunda webapp artifact. See the REST Api Documentation for details.