Apache Camel is a well known Open Source framework solving a lot of integration problems and implementing the Enterprise Integration Patterns. So combining it with camunda BPM is a perfect match: solve workflow and BPM requirements with camunda and integration requirements with Camel. Together with Rafael Cordones we took the existing Activiti Camel Module as a basis and did a huge refactoring. For everybody knowing this module I compiled the changes at the end of this article.
Once a year the whole camunda team does a ShipIt-Day (inspired by Atlassian) - developing something awesome within 24 hours. This year, Kristin, Falko and me did "camunda share" - a web application in the cloud to share and discuss BPMN 2.0 process models. And we shipped it! It is live. Try it today: http://camunda.org/share/ Why camunda share? We often discuss with colleagues, partners or customers about process models.
Note: this blogpost only applies to camunda BPM version < 7.1.0. Starting from camunda BPM 7.2.0 we ship Groovy as part of the pre-packaged distribution. Recently at a customer we added a ScriptTask to a process and wanted to run a Groovy script. Pretty easy with camunda BPM - but in the JBoss environment you have to know how to correctly put Groovy on the classpath - as we correctly use the JSR 223 stuff to recognize existing Scripting Languages.
We are happy to announce the first major release of camunda BPM: 7.0.0-Final. The highlights of this release are camunda cockpit: new webapplication for visual process monitoring and operations improved process engine with more flexible and better performing history (audit database), support for activity instance execution model, better clustering support REST Api based on JAX-RS Sophisticated Runtime Container Integration Container managed Threading (JBoss Threads, JCA, CommonJ), Shared Process Egnine as container managed service on all containers including Apache Tomcat.
Today we are happy to announce the next alpha version of camunda BPM. Get it here. Highlights of this Release cockpit: instance filters added that allow you to filter for business key and variables called process definition tab added called process instances tab added admin: administrate users and groups added change group memberships added manage authorizations added assign access rights to cockpit and tasklist added (as part of manage authorizations) engine: ability to run process engine in a heterogenous cluster added unique constraint on business key removed (applied to new installations only) #noRetriesLeft to jobQuery added bpmn element throwing message event added bpmn element send task added exception types in error codes to declare business exceptions history performance improved configuration from camunda.
Yes, fellow BPM-enthusiasts it is time to head to Prague for the camunda BPM community event of the year! We are heading across the border and are hosting our first event in a non-German speaking country on Friday, October 18th at the fusion hotel in the great city of Prague. You will get the chance to learn more about camunda BPM from the people behind the platform (the whole team will be present!
Here comes the latest camunda BPM alpha release with the following highlights: New features in cockpit webapplication: Greatly improved layout Editing process variables Cancelling a process instance Increment retries for failed jobs Login based on Process Engine Identity Service We added a new application called camunda Admin which provides support for Managing users & groups based on the process engine engine identity service Creating an initial user for a process engine The REST API was enhanced Improved variable handling Added Jobs resource (contribution by Clint Manning, 1&1) Added User and Group Resources The Process Engine got smarter Started work on authorization service Braking change: the URL for cockpit is now http://localhost:8080/camunda/.
camunda BPM 7.0.0-alpha7 is out now! The highlights of this new release are: In Cockpit we worked on the visualization of Process Instances: Incidents of a running process instance will be shown in the corresponding rendered process diagram. The former introduced Activity Instance Tree will be visualized as a tree. Now it is possible to select a BPMN element in the rendered process diagram or to select a activity instance wihtin the activity instance tree.