Hi BJ, Thanks for fronting some alternatives. Closing the loop then on your initial suggestion (i.e. “One website, many stores - is it possible”). Assuming I take a critical path approach (in context of the features that I am after) to my implementation which could be limited to tenant level data separation only (i.e. excludes any cosmetic type areas such as logos and only involves tenants wanting to act, generate and report on their respective data aka invoicing appreciating ‘some’ tenant level configuration in context of taxation etc.) then would the “One website, many stores - is it possible?” approach provide the least impact to my particular problem? Or based on the additional info that I provided can I assume a multi DB approach would be the only way to go?
Thanks again guys; much appreciated frank -- View this message in context: http://ofbiz.135035.n4.nabble.com/multi-tenant-implementation-tp2538231p2538414.html Sent from the OFBiz - User mailing list archive at Nabble.com.
