(this post was originally part of the 7.0.0-alpha6 release blog post but later extracted into an own post). In 7.0.0-alpha6 we introduced the concept of activity instances and the activity instance tree to the core process engine. This post explains the motivation and gives some insight into the internal implementation. Why do we need an Activity Instance Tree? The activity instance tree contains a node for each activity that is currently active in the process instance.
Two weeks after the last alpha release we bring you the freshly baked* alpha5 version of the camunda BPM platform. The highlights of this crispy new release are: Failed jobs plugin in cockpit, Process Instance table in cockpit, Refined client-side plugin infrastructure, New incident infrastructure in process engine, Additions to the REST API, Complete support for websphere application server 8.5 (enterprise customers only) 50 JIRA issues were closed, see the complete release notes.
If you want to do BPM / Workflow and BPMN 2.0 in PHP then we have good news for you: as part of our camunda BPM polyglot initiative we started a new incubation project which aims at providing a PHP SDK for camunda BPM. This SDK will facilitate the development of PHP-based applications that use the camunda BPM middleware services. The project will provide a client library which authenticates against the REST Api and provide PHP developers with a native API for interacting with the process engine: While the camunda BPM project stays focused on Java as primary programming language, we believe that it is important to support developers that use other programming languages and give them access to the BPMN 2.0 process engine technology, without having to rewrite that technology in every programming language.
camunda Cockpit with a plugin. Yeaaah. As we have seen in the past, it is impossible for camunda Cockpit ---our process monitoring tool--- to satisfy all needs, out of the box. That is why we have long thought about providing it with an appopriate extension mechanism that empoweres users to fit the tool to their very own monitoring needs. With the latest relase of camunda BPM a first version of a plugin system for camunda Cockpit is finally here.
Release early and release often. Today we bring you the next release of camunda BPM (7.0.0-alpha4). The Highlights are: First cut of new plugin API for camunda cockpit. Added message correlation to REST API. Support for shared process engine in IBM Websphere distribution (enterprise customers only). Read the full release notes in Jira. Message correlation in REST API With the previous release we added a message correlation method to the Java API.
If we go on tour together with Oracle I think we have to have camunda BPM running on the Oracle WebLogic application server 12c (WLS in short). And one of our enterprise customers asked - so I invested a Sunday and got it running (okay - to be honest - I needed quite some help from our Java EE server guru Christian). In this blog post I give a step by step description how run camunda BPM on WLS.
High Noon in BPM City: not a soul walks the dusty main road and the sun glares mercilessly onto El Camundo and his opponent – the Oracle of the Desert. The wireless mouse still rests in his holster, his hand hovers above it – only the slightest quiver reveals Camundo's tension. Pearly beads of sweat are glistening on Oracle's face. Who will be the first to shoot off his token? This is close to what you can expect from our Shootout Roadshow, that we will run together with Oracle and Opitz Consulting (the latter as a neutral presenter).
camunda BPM 7.0.0-alpha3 is out now! It packs a bunch of new features such as support for Spring Process Applications and correlation via the engine's Java API. First things first: Get it here! Spring Process Applications Use process engines, container-managed or embedded, from within your Spring application context (on Tomcat, Glassfish). See below an example from our getting started guide: Message correlation BPMN offers two incoming message constructs that are supported by the engine: Message start events and intermediate catching message events.
Last week we had our first two camunda.org community kick-off events. On Wednesday we were at the Deutsche WertpapierService Bank AG in Frankfurt followed by an evening on Thursday at LVM Versicherung in Münster. Both companies successfully work with camunda BPM and have spoken of their experiences with the platform. We also got a chance to present the camunda project to groups of about 20 BPM enthusiasts and had open discussions about aims, preferences, likes and wishes.