[
https://issues.apache.org/jira/browse/OFBIZ-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847187#action_12847187
]
Saad Hage commented on OFBIZ-3540:
----------------------------------
I'm currently writing a web application can easily deployed in OFBiz platform.
This application will use many functionality of OFBiz (accounting, ..), and
will be hosted. We have very very small clients and I can't create an instance
of OFBiz for each of them, this very expensive. Each OFBiz instance take about
200 meg in RAM. That's why a solution like multi-tenants is very important for
us. My concern with this branch is won't be supported by OFBiz team like 9.04
branch.
Anyway, Jacques, can you suggest an idea (other than multi-tenants) or an
architecture to resolve this ?
Regards,
Saad
> Multi-Tenant Support (Login Based)
> ----------------------------------
>
> Key: OFBIZ-3540
> URL: https://issues.apache.org/jira/browse/OFBIZ-3540
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: SVN trunk
> Reporter: David E. Jones
> Assignee: David E. Jones
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: MultiTenant20100305.patch, MultiTenant20100305.patch,
> MultiTenant20100305.patch
>
>
> Support multiple tenants in a single instance of OFBiz. Each tenant will have
> its own databases (one for each entity group). Database settings will
> override the settings on the delegator with parameters from an entity record
> so that new tenants can be added on the fly without restarting the server
> (new tenants will still need to have data loaded in their databases just like
> any other).
> If valid Tenant ID is specified when user logs in then webapp context will be
> setup with tools for that tenant as a variation of the base delegator
> (including delegator, dispatcher, security, authz, visit, server hit, etc
> handled for it).
> Demo data includes a couple of sample tenants. After loading demo data (ant
> run-install) try logging in to webtools or any other admin app with the
> Tenant ID of "DEMO1".
> NOTE: this patch also addresses some stability issues with the LoginWorker,
> ControlServlet, Visit, and ServerHit functionality that was exposed while
> developing this. For example, after a logout functionality that runs in the
> ControlServlet may fail because things that were in the session before are
> not there any more. In this patch there is code to rebuild the request and
> session after logout (necessary for changing tenants, helpful for these other
> issues).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
