Jaya,

How do you register the group under delegator?

If it is under same delegator then it shouldn't be problem ideally. And if
it is different then you should try to register all groups under the same
delegator then it should work.



Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Mon, Mar 26, 2018 at 12:29 PM, jayachandr...@gmail.com <
jayachandr...@gmail.com> wrote:

>
>
> On 2018/03/26 05:00:58, Rishi Solanki <rishisolan...@gmail.com> wrote:
> > Paul,
> >
> > Thank you for your reply and more insights. I was just trying to tell the
> > group OFBiz capabilities that how quickly entities can be separated among
> > databases if required (not to everyone but to those who are newer). And
> yes
> > in that case CRUD would be slower and only gains is in reads.
> >
> > If we talk about FKs, I did this in past and in case of mysql it maintain
> > the FKs the referential integrity among different db. I do agree with you
> > on the fact that, this is not good idea to have more database, instead
> > OFBiz supports many ways to retrieve the data way faster rather
> separating
> > the database.
> >
> > So rather that using the separate database, considering the flat
> > information storage would be better idea IMO for faster read.
> >
> > Best Regards,
> >
> >
> > Rishi Solanki
> > Sr Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> > www.hotwax.co
> >
> > On Sun, Mar 25, 2018 at 7:12 AM, Paul Foxworthy <p...@cohsoft.com.au>
> wrote:
> >
> > > On 25 March 2018 at 01:58, Rishi Solanki <rishisolan...@gmail.com>
> wrote:
> > >
> > >
> > > > Register new group in entityengine.xml with new name and data
> resource;
> > > >
> > > > <group-map group-name="your.group.name"
> > > > datasource-name="yourDataResourceName"/>
> > > >
> > > > Add new data resource entry in the entityengine.xml like we have
> many. In
> > > > your case entityengine will contains two entry as localmysql and
> > > > localmysql2 (or any name you prefer).
> > > > Now register all the entities with "your.group.name" in
> > > entity-group.xml.
> > > >
> > > > Refer <group-map group-name="org.apache.ofbiz.tenant"
> > > > datasource-name="localderbytenant"/> and related entries for more
> > > details.
> > > >
> > >
> > > Thanks Rishi.
> > >
> > > If you do define a new group, does that mean:
> > >
> > > - any transaction that modifies entities in two different groups will
> be
> > > slower as the transaction must be a distributed transaction with
> two-phase
> > > commit? To put it another way, with good design decisions, entity
> groups
> > > may well give you  faster reads, but writes very likely won't be?
> > > - Foreign key constraints and thus guaranteed referential integrity
> might
> > > not be possible between groups because not all DBMSes support FKs that
> > > refer to another database?
> > >
> > > Thanks
> > >
> > > Paul Foxworthy
> > >
> > > --
> > > Coherent Software Australia Pty Ltd
> > > PO Box 2773
> > > Cheltenham Vic 3192
> > > Australia
> > >
> > > Phone: +61 3 9585 6788
> > > Web: http://www.coherentsoftware.com.au/
> > > Email: i...@coherentsoftware.com.au
> > >
> >
>
>
> Hi Rishi,
>
> Thanks for your reply on this.
>
> As i said different entity groups allow us  to make different database
> with set of entities. And we have done successfully for communication event
> related tables.
>
> As you said about FKs thats absolutely right about referential integrity
> among different db in mysql.
>
> Coming to the CRUD operations with different groups : ofbiz will create DB
> datasource for each group and maintain the connection pool and perform the
> CRUD operations. While performing ofbiz delegator  uses the group related
> datasource connection perform the actions and its depend on the  DB how
> quickly respond.
>
> With CommunicationEvent related group in our case was performing good and
> not have the issue with writing how ever it's totally different process
> from order/product info.
>
> Now issue is when we want read data from view entity(tables are in
> differents groups(databases)) then ofbiz only uses primary db connection
> and throwing another table not available error.
>
>
> Like communication event to different for inventory we have so many
> dependent view entities in ofbiz.
>
> So looking for solution to maintain this facility data as separtion from
> the actual process.
>
>
> Thanks & Regards
> Jaya
>
>
>
>
>

Reply via email to