Activiti Engine Architecture

skosov — Fri, 05 Dec 2014 14:25:22 GMT

Dear Colleagues,I have got a task to implement BPM in a (relatively) big company. I am thinking to use Activiti as a BMP platform but I am hitting some problems which are due to Activiti limitation or lack of my understanding it. I am asking you to help me with your opinions. Let consider a task wh

Re: Activiti Engine Architecture

jbarrez — Fri, 05 Dec 2014 15:52:32 GMT

Sure: point another Activiti engine to the same database as the one in AE and you can access all the data. Use that engine in your other user interface.

Re: Activiti Engine Architecture

pmsevestre — Sat, 06 Dec 2014 16:01:27 GMT

I´ve faced more or less the same challenge you´ve tasked with and our team have come up with the following approach:

1. We developed our own user front-end (very imaginatively named "userfront");
2. We use standard activiti-explorer for admin tasks only (user/group assignment, process deployment, etc).
3. Forms are developed using plain html and/or template languages like velocity, supported by javascript were necessary. Those forms are packed with the process themselves and pulled from there by the front-end.
4. All process-specific data used to support the forms (eg: lookups) use ajax and are routed by the userfront to an ESB (WSO2 ESB in our case)
5. No process-specific jars are deployed in the userfront, ever.
6. Process-specific logic is always coded in groovy (our choice), but we try to limit this code to what we call "glue-logic", meaning code that is mainly used to prepare calls to external web services (SOAP and/or REST-style ones) and/or handle its results. In order to reduce configuration isses, we allways call external services through the ESB
7. Groovy scripts are packed together with the process themselves. We´ve developed a custom deployer and behaviour that extracts the scripts on demand and execute them when the process reaches a "script activity". The custom behaviour was necessary in order to execute an external script instead of the standard behaviour of executing an embedded script. This makes much easier to create standalone projects for each process where the developer can start a standalone engine instance and create scripts using standard Groovy IDE integration, including the hability to set breakpoints, inspect variables, etc
8. Individual process development teams use a maven archetype to quickly setup a new project, which helps a lot in terms of reducing the required time for onboarding new developers.

Re: Activiti Engine Architecture

jbarrez — Mon, 08 Dec 2014 13:21:34 GMT

Thanks for sharing this. Really cool setup you have!

topic Re: Activiti Engine Architecture in Alfresco Archive

Activiti Engine Architecture

Re: Activiti Engine Architecture

Re: Activiti Engine Architecture

Re: Activiti Engine Architecture