From Activiti to camunda fox: The SaaS Scenario. Sven Jörges IHK-GfI

Transcription

1 From Activiti to camunda fox: The SaaS Scenario Sven Jörges IHK-GfI

2 IHK-GfI mbh IT center of the german Chambers of Industry and Commerce (Industrie- und Handelskammern, IHKs) and its Association (Deutscher Industrie- und Handelskammertag, DIHK) Since more than 40 years

3 Customers The 80 Chambers of Industry and Commerce (IHKs) and their Association (DIHK). More than employees of the IHKs each day throughout Germany.

4 Integration

5 EVA Fallmanagement: Requirements

6 Requirements BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 6

7 Requirements BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 7

8 Requirements BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 8

9 Requirements BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 9

10 Anforderungen BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 10

11 Anforderungen BPMN 2.0 SaaS Multi-Tenancy Performance and High Availability Support 11

12 Selection and PoC

13 BPMS: Selection and PoC BPM Suite 13

14 EVA Fallmanagement: Overview

15 Architecture (logical) 15

16 BPMN 2.0 Tool Process Definition Process Engine Process Data Database

17 Human Interaction & Service Orchestration egovernment Infrastructure EVA.Mobile BPMN 2.0 Tool Process Definition EVA Process Engine Process Data Database

18 Human Interaction & Service Orchestration egovernment Infrastructure EVA.Mobile BPMN 2.0 Tool Process Definition EVA Authentication / Authorisation Directory (LDAP) Process Engine Process Data Database

19 Human Interaction & Service Orchestration egovernment Infrastructure EVA.Mobile BPMN 2.0 Tool Process Definition EVA Documents Authentication / Authorisation Directory (LDAP) Authentication / Authorisation DMS Scan Client Documents Process History Process Engine Process Data Database

20 Human Interaction & Service Orchestration egovernment Infrastructure EVA.Mobile BPMN 2.0 Tool Process Definition EVA Documents Authentication / Authorisation Directory (LDAP) Authentication / Authorisation DMS Scan Client Documents Process History Process Engine Process Data Database Reports EVA Analytics

21 Architecture (technical) 21

22

23

24 Architecture (Process Engine) 24

25 Client: EVA 25

26 Client: EVA 26

27 Client: EVA Desk My Tasks Group Tasks Process Instances 27

28 Client: EVA 28

29 Client: EVA 29

30 First Obstacles

31 Multi-Tenancy Problem: No out-of-the-box support for tenants in Activiti 31

32 Multi-Tenancy Oracle DB IHK101 IHK106 IHK106_05 Process Engine 101 Process Engine 106 Glassfish Node 1 ENTW QS Tenant derivable from user name: 101joerges

33 Multi-Tenancy Solution 1: ALTER SESSION SET CURRENT_SCHEMA and custom JDBC data source 33

34 Multi-Tenancy Solution 1: ALTER SESSION SET CURRENT_SCHEMA and custom JDBC data source Bad performance! 34

35 Multi-Tenancy Solution 2: Use of database table prefixes in Activiti (ACT-565), since Activiti

36 activiti.cfg.xml: <! Tenant > Multi-Tenancy <bean id="processengineconfiguration101" class= > <property name="processenginename" value="101" /> <property name="datasource" ref="containerdatasource" /> <property name="databasetableprefix" value="act101." /> </bean> <! Tenant > <bean id="processengineconfiguration106" class= > <property name="processenginename" value="106" /> <property name="datasource" ref="containerdatasource" /> <property name="databasetableprefix" value="act106." /> </bean> 36

37 Multi-Tenancy ProcessEngineConfiguration config = ProcessEngineConfiguration.createProcessEngineConfigurationFromResource( "activiti.cfg.xml", "processengineconfiguration101"); ProcessEngine engine101 = config.buildprocessengine(); 37

38 Multi-Tenancy Solution 3: fox platform Process engines do not have to be managed manually. 38

39 Query API Problem: Activiti s on-board query API not suitable for our requirements 39

40 Query API: Example taskservice.createtaskquery().taskassignee("101joerges").taskpriority(50).orderbyduedate().asc().list() 40

41 Query API Disadvantage 1: Not all required queries could be constructed via the query API Example: All tasks with 101joerges being the owner or the assignee. 41

42 Query API Disadvantage 2: Aggregate selections are expensive because multiple queries are required Bad performance Pagination difficult 42

43 Query API Solution: Define custom MyBatis queries! (see Fox User Guide Performance Tuning with custom Queries ) Good performance (factor 10!) Pagination works Custom queries have to be maintained 43

44 fox platform

45 Reasons for Changing Process Applications JEE-style process deployment Processes are collected in WARs Services can be collected in dependent JARs 45

46 Reasons for Changing Platform Job Executor better configurability (job aquisition, multiple process engines) application server integration (e.g. thread pools) 46

47 Architecture (fox engine only) 47

48 Architecture (with fox platform) 48

49 Conclusion

50 Conclusion Activiti-based fox platform is a flexible BPM solution that is ready for enterprise scenarios 50

51 Conclusion Thanks to open source: React to specific requirements by just doing it yourself. 51

52 Conclusion Thanks to open source: React to specific requirements by just doing it yourself. Or by asking the community. 52

53 Conclusion Thanks to open source: React to specific requirements by just doing it yourself. Or by asking the community. Or camunda. 53

54 Next Steps Status of EVA Fallmanagement: Infrastructure is available First client (EVA) is realized Show cases under construction Goal: Productive for first customers in early

55 Thanks for your attention! Website: Twitter: Facebook: IHK Gesellschaft für Informationsverarbeitung mbh Emil-Figge-Str Dortmund Fon: 0231 / Fax: 0231 / [email protected] 2011_V08