As chathura has mentioned, we should not modify the activiti code or database schemas. That way, we have the ability to switch to latest version of activiti engine at each release which enables us to obtain all the bug fixes available from the parent project.
Regards Nandika On Wed, Feb 12, 2014 at 12:52 PM, 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 > > -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
