BPMNData Extensions for the camunda BPM platform

This prototype implements a model-driven approach for building process choreographies from A to Z. The methodology has been developed by Kimon Batoulis, Sebastian Kruse, Thorben Lindhauer and Thomas Stoff during their Master studies at Hasso-Plattner-Institute Potsdam. This distribution of the execution platform is accompanied by an extended version of the camunda modeler. See the Downloads and Links section for binaries. Confer the Extensions documentation for technical details on the extensions we made in the platform.

Building engine & distro

Build the complete platform by running mvn clean install from the root folder.

A shortcut is to build only those artifacts that we have extended and resolve the rest from camunda's repository. Proceed as follows:

1. Build the process engine: cd /engine -> mvn clean install
2. Build the BPMNData endpoint: cd /bpmn-data-endpoint -> mvn clean install
3. Build the web applications: cd /webapps/camunda-webapp -> mvn clean install
4. Build the Tomcat distro: cd /distro/tomcat -> mvn clean install

The resulting Maven artifacts follow the camunda naming, but have different artifact ids: camunda-engine becomes bpmn-data-camunda-engine and so on.

Platform Configuration

1. Check the Tomcat distro: /server/apache-tomcat-{version}/lib should containt the bpmn-data-camunda-engine artifact. /server/apache-tomcat-{version}/webapps should contain bpmn-data-endpoint.war.
2. Check /server/apache-tomcat-{version}/conf/bpm-platform.xml: The default engine should have a proerty bpmnDataAware set to true. Furthermore, you can set the database connection properties for the data object persistence in the bpmnDataProperties element. Note that this prototype is restricted to MySQL databases. dataJobRetryTimeCycle allows to configure the timeout between two attempts to check the data input of a given activity. It follows the ISO 8601 standard. The default is set to 20 seconds. (In general, you can also configure multiple engines with these extensions. However, please note that you can currently only use the default engine for BPMNData message exchanges. See the BPMNData Endpoint docs for an explanation)
3. When running multiple instances on the same machine, you may also want to check /server/apache-tomcat-{version}/conf/server.xml and set different ports.

Enacting Choreographies

Confer the usage docs on how to deploy a developed process model.

Downloads

• BPMNData modeler update site
• BPMNData Tomcat distro
• BPMNData Demo Process Applications

Links

• BPMNData modeler sources
• BPMNData modeler usage
• BPMNData modeler screencast
• BPMNData project page