Multi-tenant ecommerce
Locked
 
|
Ofbiz looks like exactly what I need for an upcoming project (thanks all for
that) and I will need multi-tenant behaviour to the ecommerce side if it's not there. https://cwiki.apache.org/OFBIZ/multitenancy-support.html states that: "Currently the Ecommerce for Tenants is not supported." Question: Is this still correct? Assuming yes can anyone give an indication of how big a job it would be to make the ecommerce portion multi-tenant on exactly the same basis as the backend application is already? i.e. individual database per tenant but a single web application. It looks like I will need this if the project goes ahead, so I'd like to get my head around how massive a job it might be. Thanks, Gareth. |
|
|
Hi Gareth,
It should be possible to have a dedicated e-commerce solution per tenant. First you have to create/set up a tenant for the backend, and after that you should create a new e-commerce store app in hot-deploy, with setting the appropriate configuration items in the code. With regards, Pierre 2011/10/9 Gareth O'Brien <[hidden email]> > Ofbiz looks like exactly what I need for an upcoming project (thanks all > for > that) and I will need multi-tenant behaviour to the ecommerce side if it's > not there. > > > > https://cwiki.apache.org/OFBIZ/multitenancy-support.html states that: > "Currently the Ecommerce for Tenants is not supported." > > > > Question: > > Is this still correct? > > > > Assuming yes can anyone give an indication of how big a job it would be to > make the ecommerce portion multi-tenant on exactly the same basis as the > backend application is already? i.e. individual database per tenant but a > single web application. > > > > It looks like I will need this if the project goes ahead, so I'd like to > get > my head around how massive a job it might be. > > > > Thanks, > > > > Gareth. > > > > |
|
|
Thanks for the reply Pierre.
So the current design is that each web store is a separate web application attached to a particular tenantId? I was thinking of a single web application that is connected to the appropriate database in similar manner to the way the back-end works. The tenantId would be passed either in the URL or tenantId in the login widget as currently in the back end. The majority of my experience has been in MS .NET, IIS, etc. As a result I might be over thinking this ... I'm thinking that the management overhead of say 500 web applications on the disk would become tedious. More importantly, I'm wondering if/how much performance penalty would there be to running multiple web applications rather than one web application for all sites. Is this a valid concern with Tomcat? Do you have a gut feel for whether reducing such performance concern would be worth the dev effort? Thanks, Gareth. |
|
|
You do not have the choice of passing the tenantId in the login as
access to the e-commerce store is not restricted Only way you can do it passing as URL parameter and then collect those parameters in ControlServlet. Thanks, Raj On Monday 10 October 2011 02:59 PM, gobrien wrote: > Thanks for the reply Pierre. > > So the current design is that each web store is a separate web application > attached to a particular tenantId? > > I was thinking of a single web application that is connected to the > appropriate database in similar manner to the way the back-end works. The > tenantId would be passed either in the URL or tenantId in the login widget > as currently in the back end. > > The majority of my experience has been in MS .NET, IIS, etc. As a result I > might be over thinking this ... > > I'm thinking that the management overhead of say 500 web applications on the > disk would become tedious. More importantly, I'm wondering if/how much > performance penalty would there be to running multiple web applications > rather than one web application for all sites. Is this a valid concern with > Tomcat? > > Do you have a gut feel for whether reducing such performance concern would > be worth the dev effort? > > Thanks, > > Gareth. > > -- > View this message in context: http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3889648.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > |
|
|
In reply to this post by gobrien
Hi Gareth,
IMO, I would not like to see that a (potential) customer would be required to enter the tenant ID, as this would surely deminish user satisfaction. And on the other hand passing the tenant ID in a url would also not be preferable regarding security issues. I can imagine that the webstore of each tenant would be requiring specific style sheets and componant layouts, so that would lead to having to maintain several dedicated instances of the ecommerce application and associated themes. Plus, if you are indeed talking about so many tenants and eStores times several hundreds of users (viewers, clients and backend users) you would have to have some high availability c.q. failover solution in place. Today the front end (the ecommerce) component relies heavily on several backend components, where handling of tenant delegation is already in place. So the ecommerce application should only contain the bear necessities to deliver the tenant dedicated eStore. With regards, Pierre Smits 2011/10/10 gobrien <[hidden email]> > Thanks for the reply Pierre. > > So the current design is that each web store is a separate web application > attached to a particular tenantId? > > I was thinking of a single web application that is connected to the > appropriate database in similar manner to the way the back-end works. The > tenantId would be passed either in the URL or tenantId in the login widget > as currently in the back end. > > The majority of my experience has been in MS .NET, IIS, etc. As a result I > might be over thinking this ... > > I'm thinking that the management overhead of say 500 web applications on > the > disk would become tedious. More importantly, I'm wondering if/how much > performance penalty would there be to running multiple web applications > rather than one web application for all sites. Is this a valid concern with > Tomcat? > > Do you have a gut feel for whether reducing such performance concern would > be worth the dev effort? > > Thanks, > > Gareth. > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3889648.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > |
|
|
In reply to this post by gobrien
Hi Gareth,
IMO, I would not like to see that a (potential) customer would be required to enter the tenant ID, as this would surely deminish user satisfaction. And on the other hand passing the tenant ID in a url would also not be preferable regarding security issues. I can imagine that the webstore of each tenant would be requiring specific style sheets and componant layouts, so that would lead to having to maintain several dedicated instances of the ecommerce application and associated themes. Plus, if you are indeed talking about so many tenants and eStores times several hundreds of users (viewers, clients and backend users) you would have to have some high availability c.q. failover solution in place. Today the front end (the ecommerce) component relies heavily on several backend components, where handling of tenant delegation is already in place. So the ecommerce application should only contain the bear necessities to deliver the tenant dedicated eStore. With regards, Pierre Smits 2011/10/10 gobrien <[hidden email]> > Thanks for the reply Pierre. > > So the current design is that each web store is a separate web application > attached to a particular tenantId? > > I was thinking of a single web application that is connected to the > appropriate database in similar manner to the way the back-end works. The > tenantId would be passed either in the URL or tenantId in the login widget > as currently in the back end. > > The majority of my experience has been in MS .NET, IIS, etc. As a result I > might be over thinking this ... > > I'm thinking that the management overhead of say 500 web applications on > the > disk would become tedious. More importantly, I'm wondering if/how much > performance penalty would there be to running multiple web applications > rather than one web application for all sites. Is this a valid concern with > Tomcat? > > Do you have a gut feel for whether reducing such performance concern would > be worth the dev effort? > > Thanks, > > Gareth. > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3889648.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > |
|
|
Pierre, I’m getting stuck into the code to get a better understanding of how it all hangs together. In the market we’re addressing there is a degree of paranoia about competitors being able to see one’s prices, so it is not unusual to hide the entire web store behind a login and use a customer-specific URL even to see the catalog. These are mostly B2B players so it’s not [quite] as insane as it first sounds! Actually each tenant may well have multiple sites, i.e. they have separate catalogs, style sheets, etc. for many of their customer companies. I am extremely impressed with OfBiz. Regards, Gareth. From: Pierre Smits-3 [via OFBiz] [mailto:[hidden email]] Hi Gareth, > Thanks for the reply Pierre. > > So the current design is that each web store is a separate web application > attached to a particular tenantId? > > I was thinking of a single web application that is connected to the > appropriate database in similar manner to the way the back-end works. The > tenantId would be passed either in the URL or tenantId in the login widget > as currently in the back end. > > The majority of my experience has been in MS .NET, IIS, etc. As a result I > might be over thinking this ... > > I'm thinking that the management overhead of say 500 web applications on > the > disk would become tedious. More importantly, I'm wondering if/how much > performance penalty would there be to running multiple web applications > rather than one web application for all sites. Is this a valid concern with > Tomcat? > > Do you have a gut feel for whether reducing such performance concern would > be worth the dev effort? > > Thanks, > > Gareth. > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3889648.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > If you reply to this email, your message will be added to the discussion below: http://ofbiz.135035.n4.nabble.com/Multi-tenant-ecommerce-tp3888115p3893111.html To unsubscribe from Multi-tenant ecommerce, click here. |
|
|
In reply to this post by gobrien
https://issues.apache.org/jira/browse/OFBIZ-3579
if you add something. tenant was designed to get ID from login. so for ecommerce you need to have separated webapps like eccomerclone, and put the tenantID in the web.xml. the problems I believe is how do you select which webapplication is selected for which URL. mysubdomain.domain.com www.mydoamin.com There is a patch I believe where the virtualhost is put in the web.xml as well. I took a difference approach using Website entity. Gareth O'Brien sent the following on 10/9/2011 6:47 AM: > Ofbiz looks like exactly what I need for an upcoming project (thanks all for > that) and I will need multi-tenant behaviour to the ecommerce side if it's > not there. > > > > https://cwiki.apache.org/OFBIZ/multitenancy-support.html states that: > "Currently the Ecommerce for Tenants is not supported." > > > > Question: > > Is this still correct? > > > > Assuming yes can anyone give an indication of how big a job it would be to > make the ecommerce portion multi-tenant on exactly the same basis as the > backend application is already? i.e. individual database per tenant but a > single web application. > > > > It looks like I will need this if the project goes ahead, so I'd like to get > my head around how massive a job it might be. > > > > Thanks, > > > > Gareth. > > > > |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |