[
https://issues.apache.org/jira/browse/OFBIZ-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850352#action_12850352
]
David E. Jones commented on OFBIZ-3540:
---------------------------------------
BJ: Please don't add patches to an issue that are outside the scope of the
issue. The additional ecommerce webapps should go in a separate issue so they
can be evaluated separately and have their own issue lifecycle. I'm removing it
from this issue to make this easier to manage.
About the problem you're seeing: the error message says there is no Tenant
record for that ID, meaning there is no record in the Tenant entity's database
table for that ID. Based on what you wrote here it is because you are only
loading the seed data and the OOTB Tenant records are demo data since there is
nothing inherent to the system about them, and even the IDs are meant to convey
that they are for demo purposes only (ie "DEMO1" and "DEMO2").
> 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: ecommercetenatsadd.patch, 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.
