Hi, +1 for second approach, as it is compliant with the mediation philosophy and it shows WSO2 can quickstart activiti integration using soa principles and it let us use activiti as a pluggable engine. This will allow bps to upgrade to any upcoming activiti version if needed.
as for the futur, we could share this subject with activiti community to know how they think they could support multi-tenancy on their own. Bien à vous, Cyril Rognon On Wed, Feb 12, 2014 at 8:22 AM, Chathura Ekanayake <[email protected]>wrote: > > Hi all, > > I am integrating the Activiti engine with BPS to provide BPMN support. One > of the major issues we have to address in this effort is to provide > multi-tenancy support, which is not directly supported by Activiti. > > I think we have two approaches for this: > > (1) Modify the DB schemas used by Activiti to add a tenant ID field, so > that we can filter all operations based on this tenant ID. We have to > modify the Activiti code base to support this. > > (2) Maintain a tenant ID -> process ID mapping in the integration layer. > Then we can write wrappers for Java APIs exposed by Activiti to filter each > operation based on tenant ID. Most Activiti operations can be made tenant > aware using this method, but we may find some exceptions. > > I think it is better to tryout the second approach first as we do not have > to modify the Activiti codebase (so that we can always incorporate latest > Activiti versions without any changes). > > Any feedback on this would be very helpful. > > Thanks, > Chathura > > > > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
