topic Re: multiple activiti engine with one history & idenitiy Schemas in Alfresco Archive

multiple activiti engine with one history & idenitiy Schemas

vinothkumar_j2e — Fri, 07 Jun 2013 18:57:21 GMT

hello Folks,how i can implement 4 engines i.e 4 engine schemas with one history schema & one identity schemas.Each engine will be deployed in four different weblogic domain . how can we achieve this configuration or is it feasible to have such a configuration ? what are the work around to maint

Re: multiple activiti engine with one history & idenitiy Schemas

trademak — Mon, 10 Jun 2013 14:15:51 GMT

No, you have to include the same schema for every instance. But the identity schema might not be necessary. The history level can of course be set on each process engine configuration, but should contain the same level as well across these instances.

Best regards,

Re: multiple activiti engine with one history & idenitiy Schemas

vinothkumar_j2e — Tue, 11 Jun 2013 16:41:56 GMT

Thanks . History schema is fine , we can use 4 different schemas so as engine schema. How to maintain one identity schema for all 4 (engine + history ) schemas ?

Re: multiple activiti engine with one history & idenitiy Schemas

trademak — Tue, 11 Jun 2013 18:50:03 GMT

No I meant that you can choose to not use the identity schema at all and pick your own identity solution like a LDAP or your own database tables.

Best regards,

Re: multiple activiti engine with one history & idenitiy Schemas

vinothkumar_j2e — Wed, 12 Jun 2013 13:52:02 GMT

Thanks. Lets say we are going to integrate with Active Directory with BPM. How will i get tasklist for a given user (eg. taskService.createTaskQuery().orderByTaskAssignee().list() ) , if the we are implementing own identity solution. How Activiti BPM will be able to look activity Directory for the given user and get roles and fetch the work list from the activiti engine ?

Re: multiple activiti engine with one history & idenitiy Schemas

jbarrez — Mon, 17 Jun 2013 09:40:50 GMT

The tasks will be assigned to some user, using only its id. So the assignee is effectively the id of a user in your AD.
Whenever groups are needed for a query (eg using taskCandidateUset() in the taskquery), the AD will be consulted for the groups of that user.

Re: multiple activiti engine with one history & idenitiy Schemas

vinothkumar_j2e — Mon, 17 Jun 2013 13:21:48 GMT

Thanks