This document explains the installation procedure for Camunda Cycle. You can download a prepackaged distribution which includes Camunda Cycle and a Tomcat server. For information on how to configure the prepackaged distribution, refer to the section on Configuring the pre-packaged distribution. You can also install Camunda Cycle on a vanilla Tomcat server. This procedure is explained in the section Install Camunda Cycle on vanilla Tomcat 7.
This installation guide also details how to configure the Cycle installation, including the setup of the email service, password encryption and the installation of custom connectors.
Note
We do not recommend to install Camunda Cycle together with the other platform components (webapps, engine, REST API) on the same runtime environment. A combined installation of designtime and runtime components on a single environment is not supported.
You can download a prepackaged distribution of Camunda Cycle.
This distribution includes Camunda Cycle deployed in an Apache Tomcat as well as the SQL scripts.
Find Camunda Cycle on our server:
Choose the correct version named $CYCLE_VERSION/camunda-cycle-tomcat-$CYCLE_VERSION.war
Find scripts to create the database schema on our server:
Choose the correct version named $CYCLE_VERSION/camunda-cycle-sql-scripts-$CYCLE_VERSION.jar
Unless you are using the pre-packaged distribution and do not want to exchange the packaged H2 database, you have to first create a database schema for Camunda Cycle. The Camunda Cycle distribution ships with a set of SQL create scripts that can be executed by a database administrator.
The database creation scripts reside in the sql/create
folder:
camunda-cycle-distro-$CYCLE_VERSION.zip/sql/create/*_cycle.sql
There is an individual SQL script for each supported database. Select the script appropriate for your database and run it with your database administration tool (e.g., SqlDeveloper for Oracle).
We recommend to create a separate database or database schema for Camunda Cycle.
$CYCLE_VERSION/camunda-cycle-sql-scripts-$CYCLE_VERSION.jar
.
The distribution comes with a preconfigured H2 database used by Cycle.
The H2 JDBC driver is located at camunda-cycle-distro-$CYCLE_VERSION.zip/server/apache-tomcat-VERSION/lib/h2-VERSION.jar
.
To exchange the preconfigured H2 database with your own, e.g., Oracle, you have to do the following:
$TOMCAT_HOME/lib
.$TOMCAT_HOME/webapps/cycle/META-INF/context.xml
and edit the properties of the jdbc/CycleDS
datasource definition.You can download the Camunda Cycle web application from our server.
Choose the correct version named $CYCLE_VERSION/camunda-cycle-tomcat-$CYCLE_VERSION.war
.
The Cycle datasource is configured in the Cycle web application in the file META-INF/context.xml
. It should be named jdbc/CycleDS
.
In order to use a custom datasource name, you have to edit the file WEB-INF/classes/META-INF/cycle-persistence.xml
in the Cycle web application file.
In order to use the org.apache.tomcat.jdbc.pool.DataSourceFactory
, you need to add the driver of the database you use to the $TOMCAT_HOME/lib
folder.
For example, if you plan to use the H2 database, you would have to add the h2-VERSION.jar.
$TOMCAT_HOME/lib
.
$TOMCAT_HOME/webapps
.
Optionally you may rename it or extract it to a folder to deploy it to a specific context like /cycle
.Note: This step is optional and can be skipped if you do not require Cycle to send a welcome email to newly created users.
$TOMCAT_HOME/lib
folder.
In order to use the Cycle email service, you have to configure a mail session in the META-INF/context.xml
file in the Cycle web application.
By default, Cycle looks up a mail session using the JNDI Name mail/Session
.
The name of the mail session to look up can be changed by editing the following file in the Cycle web application:
WEB-INF/classes/spring/configuration.xml
The file defines a Spring Bean named cycleConfiguration
. On this spring bean, set the JNDI name of the Mail Session to a custom name:
<bean id="cycleConfiguration" class="org.camunda.bpm.cycle.configuration.CycleConfiguration">
<!-- ... -->
<!-- Cycle email service configuration -->
<property name="emailFrom" value="cycle@localhost" />
<property name="mailSessionName" value="my/mail/Session" />
<!-- ... -->
</bean>
Connector passwords are encrypted before they are stored in the Cycle database using the PBEWithMD5AndDES algorithm implementation.
$USER_HOME/cycle.password
containing a self chosen plain ASCII password.
You can add own Connectors in form of JAR files to your Camunda Cycle installation. Just follow these steps to add a new Connector.
$TOMCAT_HOME/webapps/cycle/WEB-INF/lib
.$TOMCAT_HOME/webapps/cycle/WEB-INF/classes/spring/connector-configurations.xml
file and include a variation of the following snippet:After adding the JAR file and updating the Connector configuration file, you can start the server. The added Connector appears in the Add Connector dialog and can be used to create roundtrips.
We updated the database schema of camunda Cycle in the version 3.1.0. So please update your database schema using the migration scripts provided in the sql/upgrade
folder of the camunda cycle distribution:
camunda-cycle-distro-$CYCLE_VERSION.zip/sql/upgrade/*_cycle_3.0_to_3.1.sql
There is an individual SQL script for each supported database. Select the script appropriate for your database and run it with your database administration tool (e.g. SqlDeveloper for Oracle).