You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Andrew Sykes (JIRA)" <ji...@ofbiz.org> on 2006/06/24 10:41:18 UTC

[JIRA] Commented: (OFBIZ-890) multi-tenanting ofbiz (many instances on one server)

     [ http://jira.undersunconsulting.com/browse/OFBIZ-890?page=comments#action_13566 ]
     
Andrew Sykes commented on OFBIZ-890:
------------------------------------

Si,

This is already do-able, I seem to remember telling you we had been doing this for ages about a year ago with no problems.

For multiple servers, you simply bind each server to a different ip rather than a different port, that makes life much easier.

Hope that helps.

- Andrew Sykes

> multi-tenanting ofbiz (many instances on one server)
> ----------------------------------------------------
>
>          Key: OFBIZ-890
>          URL: http://jira.undersunconsulting.com/browse/OFBIZ-890
>      Project: [OFBiz] Open For Business
>         Type: New Feature
>   Components: webapp
>     Versions: SVN
>     Reporter: Si Chen
>     Assignee: Jira Administrator
>      Fix For: SVN

>
>
> I've been thinking about a way to run multiple instances (ie, many companies) on one server, and I think it could be done reasonably easily this way:
> 1.  In ofbiz-component.xml, in each <webapp ...>, allow many servers to be declared in the server="" attribute.  (ie: server="company1, company2, company3")
> 2.  In ofbiz-containers.xml, declare each of those servers to run on different ports.
> 3.  In entityengine.xml and serviceengine.xml, declare a different delegator and dispatcher for each instance or company.  This means each company will have its own database, though possibly all on the same database server, which I think is a good thing.
> 4.  When system starts up, it will load each webapp into every server specified in <webapp server=""> in ofbiz-component.xml
> 5.  Then, when it is loading delegator and dispatcher, it will create one based on server="" name and the name of delegator and dispatcher in web.xml.  Hence, there'd be a company1-default and company2-default.  Out of respect for current convention, we can keep it so that server="default" gets us "default" delegator and dispatcher rather than "default-default".
> 6.  When loading data with install or install-seed, add optional parameter to specify delegator name, so seed data can be loaded into various separate delegators for different companies.
> Would this cause any problems?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.undersunconsulting.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira