Release early and release often. Today we bring youthe 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?
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.
I am happy to announce the official launch of the camunda BPM incubation space with the first large community contribution by plexiti. View it on github: https://github.com/camunda/camunda-bpm-incubation https://github.com/camunda/camunda-bpm-fluent-testing The goal of the camunda BPM incubation space is to promote the development of interesting new projects and ideas around BPM, BPMN and process engines. Due to the productization and stabilization focus in the camunda BPM core platform, we decided to separate out these experimental projects from the core platform.
I am happy to announce the release of camunda bpm platform 7.0.0-alpha2. This is the first camunda BPM release that contains a distribution for Glassfish Application Server. You can now download a complete open source BPM platform with fully compliant Java EE 6 integration! Download it now! Highlights: Glassfish 3.x Distribution with Java EE 6 process engine integration New Job Executor Service with JCA 1.6 Integration Job Executor manageability through JMX New space for documentation: http://docs.
After launching our open source platform camunda BPM on 18th March, we gave it a proper welcoming to the BPM community last week. 55 people showed up to the launch party held at camunda HQ, which coincided with our 5th birthday. It was a great night, during which the hard-working team around camunda BPM had the chance to demonstrate some of the platform's great features and advantages followed by good discussions with the guests afterwards.
Process management is not a bureaucratic evil but can be a key instrument for scalable business models. But to do so we need to get rid of our old ways of thinking. Need an example? The whole Zero Code BPM – Illusion, is one of many errors that have dominated process management in the past. On 18th March we released our BPM platform under an open source license as Business Process Management is impossible without IT (not everyone likes this, but it’s just the way it is).
Scott Francis has written an excellent post about the core message of our presentation at bpmNEXT. He called it the "Zero Code Hypothesis". Though Scott's summary is completely right in its essentials, I would like to put some details straight: We don't think that "Zero Code BPM" does not work at all - Zero Coding and our approach are both reasonable, depending on what you have and what you need.