Discussion Multitenant Entity Loading.

[BJ Freeman]

It is important to show the correct way to load tenant data in a demo so
users have a model.
As a stop gap, till a more elaborate scheme is devised, have an install
reader for each tenant including the default.
This should not take any code changes only the way the install readers
are setup.
reader=demotenantdefault
reader=demotenantDEMO1
reader=demotenantDEMO2

And for Real data
reader=seedtenantdefault
reader=seedtenant[teanantID put in by developer]

Separate the Entitymodel.xml for tenant to a separate file
TenantEntitymodel.xml

TenantDemoData.xml and TenantEntitymodel.xml would be loaded under
demotenantdefault


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

[David E. Jones-2]

Why not use the already supported syntax that clearly separates two very different concepts (ie the delegator name and the tenant ID)?

-David


On Apr 3, 2010, at 10:07 AM, BJ Freeman wrote:

> It is important to show the correct way to load tenant data in a demo so
> users have a model.
> As a stop gap, till a more elaborate scheme is devised, have an install
> reader for each tenant including the default.
> This should not take any code changes only the way the install readers
> are setup.
> reader=demotenantdefault
> reader=demotenantDEMO1
> reader=demotenantDEMO2
>
> And for Real data
> reader=seedtenantdefault
> reader=seedtenant[teanantID put in by developer]
>
> Separate the Entitymodel.xml for tenant to a separate file
> TenantEntitymodel.xml
>
> TenantDemoData.xml and TenantEntitymodel.xml would be loaded under
> demotenantdefault
>
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
> Specialtymarket.com <http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat  Y! messenger: bjfr33man
> Linkedin
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>
>

[Adam Heath-2]

David E Jones wrote:
> Why not use the already supported syntax that clearly separates two very different concepts (ie the delegator name and the tenant ID)?

Because # is a comment char in shell, which would require special
shell quoting, that some people are confused by.

I personally don't have a problem with shell quoting, but others do.
Who is the final target?  Smart developers, or people who are
evaluating new technologies, to see if they serve a purpose?

[BJ Freeman]

I understand delegator and tenantID
so you mean that the reader code would be expanded to look for the
delegator to know which files to look for.
it would append to the reader=demo the demo[tenantID from the delagator]

under that scheme would ofbiz-component.xml
    <entity-resource type="data" reader-name="demo" loader="main"
location="data/TenantDemoData.xml"/>
 modify it to be
    <entity-resource type="data" reader-name="demodefault" loader="main"
location="data/TenantDemoData.xml"/>

       
I was looking for simpler solution(no code change) but this seems very
workable.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


David E Jones sent the following on 4/3/2010 12:57 PM:

> Why not use the already supported syntax that clearly separates two very different concepts (ie the delegator name and the tenant ID)?
>
> -David
>
>
> On Apr 3, 2010, at 10:07 AM, BJ Freeman wrote:
>
>> It is important to show the correct way to load tenant data in a demo so
>> users have a model.
>> As a stop gap, till a more elaborate scheme is devised, have an install
>> reader for each tenant including the default.
>> This should not take any code changes only the way the install readers
>> are setup.
>> reader=demotenantdefault
>> reader=demotenantDEMO1
>> reader=demotenantDEMO2
>>
>> And for Real data
>> reader=seedtenantdefault
>> reader=seedtenant[teanantID put in by developer]
>>
>> Separate the Entitymodel.xml for tenant to a separate file
>> TenantEntitymodel.xml
>>
>> TenantDemoData.xml and TenantEntitymodel.xml would be loaded under
>> demotenantdefault
>>
>>
>> =========================
>> BJ Freeman
>> http://bjfreeman.elance.com
>> Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
>> Specialtymarket.com <http://www.specialtymarket.com/>
>>
>> Systems Integrator-- Glad to Assist
>>
>> Chat  Y! messenger: bjfr33man
>> Linkedin
>> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>>
>>
>
>

[Adrian Crum-2]

David,

Thank you for bringing multi-tenant capability into the project!

I will be able to use this feature where I work - to set up a demo dataset that is separate from our live data. Our legacy (non-OFBiz) software is set up that way, and one of the obstacles I've had getting our users to try out OFBiz is the lack of a sandbox where they can try out ideas without corrupting live data.

-Adrian

--- On Sat, 4/3/10, David E Jones <[hidden email]> wrote:

> From: David E Jones <[hidden email]>
> Subject: Re: Discussion Multitenant Entity Loading.
> To: [hidden email]
> Date: Saturday, April 3, 2010, 12:57 PM
>
> Why not use the already supported syntax that clearly
> separates two very different concepts (ie the delegator name
> and the tenant ID)?
>
> -David
>
>
> On Apr 3, 2010, at 10:07 AM, BJ Freeman wrote:
>
> > It is important to show the correct way to load tenant
> data in a demo so
> > users have a model.
> > As a stop gap, till a more elaborate scheme is
> devised, have an install
> > reader for each tenant including the default.
> > This should not take any code changes only the way the
> install readers
> > are setup.
> > reader=demotenantdefault
> > reader=demotenantDEMO1
> > reader=demotenantDEMO2
> >
> > And for Real data
> > reader=seedtenantdefault
> > reader=seedtenant[teanantID put in by developer]
> >
> > Separate the Entitymodel.xml for tenant to a separate
> file
> > TenantEntitymodel.xml
> >
> > TenantDemoData.xml and TenantEntitymodel.xml would be
> loaded under
> > demotenantdefault
> >
> >
> > =========================
> > BJ Freeman
> > http://bjfreeman.elance.com
> > Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
> > Specialtymarket.com <http://www.specialtymarket.com/>
> >
> > Systems Integrator-- Glad to Assist
> >
> > Chat  Y! messenger: bjfr33man
> > Linkedin
> > <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
> >
> >
>
>