Activiti: Difference between revisions

Revision as of 20:59, 13 June 2011

Introduction

The Activiti has a clear origin in the jBPM project of JBoss. The former lead developers of jBPM, Tom Baeyens and Joram Barrez, created a vibrant community around this process engine and they created a process virtual machine sub-project that enabled jBPM to be used for multiple process languages. At that point in time Alfresco was using jBPM in their document management system for the implementation of foremost workflow related functionality. But they were looking for a process engine with a more liberal open source license. ventually Alfresco decided to create a liberal Apache licensed open source process engine themselves and contacted Tom and Joram. Activiti was born! The Activiti project started off at a very fast pace and succeeded to do a monthly release of the tool stack until the stable 5.0 release in December 2010.

Activiti vs. jBMP

My personal impression is that Activiti seems much more the logical continuation of jBPM, then jBPM5 is. This article concludes that the opportunities of both BPMS are nearly identical.

Installation

extract activiti-5.6.zip to C:\Uwes\java\Activiti\activiti-5.6
C:\Uwes\java\Activiti\activiti-5.4\setup\ant demo.start
set CATALINA_HOME=C:\Uwes\java\Activiti\activiti-5.6\apps\apache-tomcat-6.0.32
download eclipse 3.6.2 (helios) and extract to C:\Uwes\eclipse\v362_classic\

Eclipse Plug-In

as decribed in Official Documentation to local eclipse 3.6.2 classic

Ant targets

demo.start
deom.stop
tomcat.start
tomcat.stop
h2.start
h2.stop
db.drop
db.create

Using Activiti

C:\Uwes\java\activiti\5.0\setup\ant (default target is demo.start) starts h2-DB on port 9092 and tomcat on port 8099. Other targets are tomcat.start, tomcat.stop, h2.start, h2.stop, db.drop, db.create.

Deployment of a Business Archive (BAR) via Probe or Ant using the REST API.

Documentation

Local Documentation file:///C:/Uwes/java/Activiti/5.0/docs/userguide/index.html
Activite Home Documentation (http://www.activiti.org/userguide/index.html)

Architecture

As Activiti is 'just a jar', it can be embedded in any Java environment: with swing or on a Tomcat, JBoss, WebSphere, etc. Or you could very well choose to run Activiti as a typical, standalone BPM server.

Components

see sheet Activiti

Eplorer

work item list

Probe

admin area, provides us with a web view on the database tables of the Activiti engine.

Kickstart

Adhoc workflows

Modeler

web base modeling tool

Designer

eclipse plugin modeling tool, started and maintained by Tijs Rademakers, Tiese Barrell, Ron van Liempd and Yvo Swillens. Enhancement of Modeler process definition to be executable.

Cycle

business it alignment

Script Languages

Groovy (standard)

Standards

BPMN XML

API

createStandaloneInMemProcessEngineConfiguration()

ProcessEngine processEngine = ProcessEngineConfiguration.
                              createStandaloneInMemProcessEngineConfiguration().
                              buildProcessEngine();

start a H2 in memory database.

createStandaloneProcessEngineConfiguration()

ProcessEngine processEngine = ProcessEngineConfiguration.
                              createStandaloneProcessEngineConfiguration().
                              buildProcessEngine();

uses a connection to a running H2 database.

Initial Tests

Eclipse based Tutorial

http://activiti.org/designer/update/
just read but modeling via Modeler seams more reasonable

Pizza Tutorial

Blog

Didn't work because of missing class.

Eclipse Project 'ActivitiTest1'

start eclipse
File -> New -> Project -> Activiti Project
select /src/main/resources/diagrams
right mouse -> New -> Other -> Activiti diagram 'ActivitiTest1.Diagram1'
create ActivitiTest1TestCase1 in /src/test/java/
right mouse -> Run As -> JUnit

Configuration

Resources

C:\Uwes\Documents\Software_Development\Modeling\BusinessProcessModeling\BPM.vsd
C:\Uwes\Documents\Software_Development\Modeling\BusinessProcessModeling\Activiti\ActivitiInAction.pdf

@@ Line 27: / Line 27: @@
   C:\Uwes\java\activiti\5.0\setup\ant (default target is '''demo.start''') starts h2-DB on port 9092 and tomcat on port 8099. Other targets are '''tomcat.start''', '''tomcat.stop''', '''h2.start''', '''h2.stop''', '''db.drop''', '''db.create'''.
-Deployment of a Business Archive (BAR) via Probe or Ant.
+Deployment of a Business Archive (BAR) via Probe or Ant using the REST API.
 ==Documentation==