[
https://issues.apache.org/jira/browse/OFBIZ-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651132#action_12651132
]
youssef khaye commented on OFBIZ-2020:
--------------------------------------
Hi Mr Jones;
Thanks for your interesting.
Reading your comment makes me think of the matter, It seems to be more
significant to create a dispatcher in the same time with a delegator if someone
request a connection for a database without them already created, and why not a
new jobmanager too.
This would solve the issue because every dispatcher with its own
(jobManager,delegator) will continue working with their DB.
Since the issue of multi delegator can be very useful in a production
environment, I will be volunteer to accomplish the necessary work, of course
with the guidance of persons like you and Mr Le Roux.
Best regards.
> Using one Ofbiz instance with multiple databases
> ------------------------------------------------
>
> Key: OFBIZ-2020
> URL: https://issues.apache.org/jira/browse/OFBIZ-2020
> Project: OFBiz
> Issue Type: New Feature
> Affects Versions: SVN trunk
> Reporter: youssef khaye
> Assignee: Jacques Le Roux
> Fix For: SVN trunk
>
> Attachments: entitymodel.xml.rej, ofbiz-multi.patch,
> ofbiz-multi.patch, ofbiz-multi.patch
>
>
> I want to share my work with you implementing the use of one OFBiz instance
> with multiple databases, by defining multiple delegators, in the
> entityengine.xml, one for each databases. this is useful when we implementing
> ofbiz for semi-independent subsidiaries of one company having users allowed
> to use two or more databases.
> This involve mainly the user authentication procedure by asking for a company
> name in the login form. This company name represents a delegator name that
> describe a specific subsidiary database. After a successful user login
> operation, the passed company name is used to retrieve the corresponding
> delegator. The method CoreEvents.chageDelegator is modified to change the
> delegator of related Dispatcher and JobManager.
> Of course I needed to store the delegator name in the GenericValue UserLogin
> to navigate among different ofbiz applications keeping the same original
> database.
> I also provided a kind of mechanism to activate or deactivates the use of
> multi-delegator by adding a "multi.delegator" property in the
> security.properties configuration file that when set true, cause the ofbiz to
> display he company field in the login form and do the necessary work to
> switch from default database to the provided one.
> I will be open to discuss any suggestion for improving this issue.
> Following is a patch for current ofbiz trunk version:
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
