|
Home > Archive > Commerce Server General > April 2004 > Multiple web applications in once site
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Multiple web applications in once site
|
|
|
| I need to have multiple websites run off of one commerce site (I'm using
..net). I was going to deterimine which site the user should be at by
web1\site1, web1\site2, etc. So, if they are site one they get one layout
and catalog and site2 gets another.
However, when playing around in commerce server I added an application to my
site. Basically, I unpacked a pup file into my site (so now i have web1 and
web2). Web2 didn't work, but it made me curious. So, I went into IIS and
told it to point back to the other application in my site (so, web2 points
to web1). It works fine, allows me to have different shopping bags and
stuff.
My question is, will I run into problems with this if I go ahead and develop
and deploy using this method. So, instead of having web1\site1, web1\site2
etc, I have web1, web2 etc. and depending on the application you're coming
from you get different layouts and catalogs.
Any thoughts? Any one done this? Pros and cons?
Thank you!
Evie
| |
| Michael O'Donovan [MSFT] 2004-04-01, 3:40 am |
| Hi Evie,
So here is the deal.
CS applications in a CS site share the same resources. Therefore if you
create your web sites as CS applications, they will all share the same
catalog, authentication, profile etc resources. If this is OK, or if this is
the desired behaviour then this might be the correct option. Also to note is
that if you use the CS API to generate your URL's within your code then all
CS applications within a CS site will share the same host name. E.g.
www.foo.com/csapplicationA, www.foo.com/csapplicationB.
What might be the deciding factor for you is the licensing. CS Standard
Edition only allows 2 CS applications per site (usually this would be one
for the web site and one for the BizDesk).
It might be better to create CS site per web site. You can also share
resources between CS sites, however this is not required, its an option. E.g
share profile resource.
Hope this helps,
Michael
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Evie" <erote@no_spamthatchertech.com> wrote in message
news:OPBke81FEHA.576@TK2MSFTNGP11.phx.gbl...
> I need to have multiple websites run off of one commerce site (I'm using
> .net). I was going to deterimine which site the user should be at by
> web1\site1, web1\site2, etc. So, if they are site one they get one layout
> and catalog and site2 gets another.
> However, when playing around in commerce server I added an application to
my
> site. Basically, I unpacked a pup file into my site (so now i have web1
and
> web2). Web2 didn't work, but it made me curious. So, I went into IIS and
> told it to point back to the other application in my site (so, web2 points
> to web1). It works fine, allows me to have different shopping bags and
> stuff.
> My question is, will I run into problems with this if I go ahead and
develop
> and deploy using this method. So, instead of having web1\site1,
web1\site2
> etc, I have web1, web2 etc. and depending on the application you're
coming
> from you get different layouts and catalogs.
> Any thoughts? Any one done this? Pros and cons?
>
> Thank you!
> Evie
>
>
| |
|
| Michael,
I do want the sites to share the same resources and code base and we already
own CS Enterprise Edition. So, I think from what you're saying is I can
have multiple "sites" running off the same code base, but I was a little off
about how to access them. This way would be www.foo.com/csapplicationA,
www.foo.com/csapplicationB and doing it from one "site" would be
www.foo.com/csapplicationA/company1, www.foo.com/csapplicationA/company2.
So, I think I should be ok with having multiple applications in one site
using the same directory as the code base (as well as sharing all
resources).
Thank you!
Evie
"Michael O'Donovan [MSFT]" <michodon@online.microsoft.com> wrote in message
news:uGaWW$7FEHA.3568@tk2msftngp13.phx.gbl...
> Hi Evie,
>
> So here is the deal.
>
> CS applications in a CS site share the same resources. Therefore if you
> create your web sites as CS applications, they will all share the same
> catalog, authentication, profile etc resources. If this is OK, or if this
is
> the desired behaviour then this might be the correct option. Also to note
is
> that if you use the CS API to generate your URL's within your code then
all
> CS applications within a CS site will share the same host name. E.g.
> www.foo.com/csapplicationA, www.foo.com/csapplicationB.
>
> What might be the deciding factor for you is the licensing. CS Standard
> Edition only allows 2 CS applications per site (usually this would be one
> for the web site and one for the BizDesk).
>
> It might be better to create CS site per web site. You can also share
> resources between CS sites, however this is not required, its an option.
E.g
> share profile resource.
>
> Hope this helps,
> Michael
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
|
| Well, upon review of the actual server machine, it turns out we CS Standard.
So, I'm back to thinking about other ways to handle multiple sites off of
one set of code or one application. One thing I've found to work is to
create a virtual directory in IIS and point it to the folder with the CS
application in it. In the code I can parse which directory users are coming
from to determine which site they want.
Has anyone else done this? Are there any problems with it? Anything odd
that happens?
Thanks!
Evie
"Evie" <erote@no_spamthatchertech.com> wrote in message
news:edzHmw%23FEHA.2808@TK2MSFTNGP10.phx.gbl...
> Michael,
>
> I do want the sites to share the same resources and code base and we
already
> own CS Enterprise Edition. So, I think from what you're saying is I can
> have multiple "sites" running off the same code base, but I was a little
off
> about how to access them. This way would be www.foo.com/csapplicationA,
> www.foo.com/csapplicationB and doing it from one "site" would be
> www.foo.com/csapplicationA/company1, www.foo.com/csapplicationA/company2.
>
> So, I think I should be ok with having multiple applications in one site
> using the same directory as the code base (as well as sharing all
> resources).
>
> Thank you!
> Evie
>
|
|
|
|
|