Activiti: Difference between revisions
| Line 31: | Line 31: | ||
* hangs because tomcat port is already in use | * hangs because tomcat port is already in use | ||
* change tomcat port in C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\conf\server.xml from 8080 to 8099 | * change tomcat port in C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\conf\server.xml from 8080 to 8099 | ||
* replace all occurences of 8080 to 8099 in C:\Uwes\java\Activiti\5. | * replace all occurences of 8080 to 8099 in C:\Uwes\java\Activiti\activiti-5.3\setup\build.xml | ||
* set CATALINA_HOME to C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\ | * set CATALINA_HOME to C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\ | ||
* import the example projects from C:\Uwes\java\Activiti\activiti-5.3\workspace into eclipse | * import the example projects from C:\Uwes\java\Activiti\activiti-5.3\workspace into eclipse | ||
Revision as of 23:01, 16 March 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.
Installation
- extract activiti-5.3.zip to C:\Uwes\java\Activiti\activiti-5.3
- than see user guide installation
Eclipse Plug-In
- as decribed in Documentation to local Helios eclipse version
Running 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.
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
see sheet Activiti
- Eplorer: work item list
- Probe: admin area
- Cycle: business it alignment
- Modeler: modeling tool
- Designer: eclipse plugin modeling tool, started and maintained by Tijs Rademakers, Tiese Barrell, Ron van Liempd and Yvo Swillens.
Initial Tests
Users Guide
- C:\Uwes\java\Activiti\activiti-5.3\setup demo.start
- hangs because tomcat port is already in use
- change tomcat port in C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\conf\server.xml from 8080 to 8099
- replace all occurences of 8080 to 8099 in C:\Uwes\java\Activiti\activiti-5.3\setup\build.xml
- set CATALINA_HOME to C:\Uwes\java\Activiti\activiti-5.3\apps\apache-tomcat-6.0.29\
- import the example projects from C:\Uwes\java\Activiti\activiti-5.3\workspace into eclipse
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.
Configuration
Resources
- C:\Uwes\Documents\Software_Development\Modeling\BusinessProcessModeling\BPM.vsd
- C:\Uwes\Documents\Software_Development\Modeling\BusinessProcessModeling\Activiti\ActivitiInAction.pdf