Yes willie, we r using profile. but user will not be
identified (except his url) until register himself with
the site.

Thanks in advance
bala

>-----Original Message-----
>are you using profiles?  if so, i would suggest attaching
>these virtual catalogs (catalog sets) to a profile.
>
>Willie 
>as 
>.
>

[ Post a follow-up to this message ]

Hi Bala,

First let me summarize what I believe to be your configuration:

You have one Commerce Server (CS) site with multiple CS applications, one
of which I'm assuming is the Business Desk, but each of the others
corresponds to a single distributor.

Each CS application is mapped to a different IIS Web site (the virtual
sites you refer to).

The Home Directory of each of the IIS Web sites is mapped to a single
common folder path that contains the code of your application.

I'm not clear why you're creating virtual directories within the Web sites
(rather than using the root, Home Directory). Perhaps this is because my
previous assumptions are incorrect.

I am not completely clear on your step 4. Do you give each distributor a
unique domain name and then map each of those domain names in DNS to
different IP addresses which correspond to each of your IIS Web sites? Can
you give an example of some of the DNS entries?

In step 5, you explain that the URL gets changed to the default/base site.
How are you retrieving the URL? Are you using the HttpRequest class (for
ASP.NET) or the Request object (for ASP)? Can you give an example of the
value that is returned for the URL?

-Rob, Microsoft
-------------------- 
microsoft.public.commerceserver.setup.deploymentoperations:3157 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

Thanks Rob,

No. we are using single site (retail) with two
application (one for site + another for bizdesk).

Here is our scenario.  We are having multiple
distributors. Each distributors has its own customer and
they will be asked to come to our site to purchase. For
this.. we need to display different catalog for each
distributors. So, we decided to use virtual catalogs.

For ex. Our site is www.xxxx.com. We've distributor A and
B, Distri. A has customerA1, customerA2. like wise
distributor B has customer B1, customerB2...We will have 2
catalogs-virtual (one for distri A users and another for
dist B users). So distri. A users will see virtual-A
catalog and distri B users only see virtual-B catalog.

We customize Retail site to meet above scenario. Also we
would like to give different url for each distributors.
Say Distri-A users will come to our site with
www.distributorA.xxxx.com and Distri-B users will come to
our site with www.distributorB.xxxx.com. Since URL is
different, our code will know which catalog to show to
users. (pls. Note that we initially allow users as a
anonymous user)


In the site configuration..
1.	We set our (default) site to www.xxxx.com.
2.	we create two more DSN name
www.distirbutorA.xxxx.com and www.distirbutorB.xxxx.com
(both should redifect to www.xxxx.com resource code).

Problem:
1.	If user browse our site with www.xxxx.com then it
show default catalog (base catalog). And works perfectly.
(code knows base catalog has to display for that user as
his url is www.xxxx.com
2.	If another user who is come to our site by
distributor A with www.distributorAxxxx.com url. If he
types this url in browser it will redirect to
www.xxxx.com. So he lost his original URL that
(www.distributorAxxxx.com) we need this should retail.
Then only we can able to show virtual-A catalog.

We are using Request.server variable to get URL. I would
be thankful if you got any other possible solutions.

Thanks,
Bala


>-----Original Message-----
>Hi Bala,
>
>First let me summarize what I believe to be your
configuration:
>
>You have one Commerce Server (CS) site with multiple CS
applications, one
>of which I'm assuming is the Business Desk, but each of
the others
>corresponds to a single distributor.
>
>Each CS application is mapped to a different IIS Web site
(the virtual
>sites you refer to).
>
>The Home Directory of each of the IIS Web sites is mapped
to a single
>common folder path that contains the code of your
application.
>
>I'm not clear why you're creating virtual directories
within the Web sites
>(rather than using the root, Home Directory). Perhaps
this is because my
>previous assumptions are incorrect.
>
>I am not completely clear on your step 4. Do you give
each distributor a
>unique domain name and then map each of those domain
names in DNS to
>different IP addresses which correspond to each of your
IIS Web sites? Can
>you give an example of some of the DNS entries?
>
>In step 5, you explain that the URL gets changed to the
default/base site.
>How are you retrieving the URL? Are you using the
HttpRequest class (for
>ASP.NET) or the Request object (for ASP)? Can you give an
example of the
>value that is returned for the URL?
>
>-Rob, Microsoft
>-------------------- 
microsoft.public.commerceserver.setup.deploymentoperations 
>microsoft.public.commerceserver.setup.deploymentoperations
:3157 
microsoft.public.commerceserver.setup.deploymentoperations 
url). 
so 
as 
our 
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>EBusiness Server Team
>
>.
>

[ Post a follow-up to this message ]

Hi Bala, thanks for the clarification.

Perhaps this issue could be corrected by adjusting your DNS entries. Rather
than registering www.distributorA.xxxx.com and www.distributorB.xxxx.com,
etc., as redirects to www.xxxx.com (are CNAME records being used for
these?), could you register them as A records to the IP address of
www.xxxx.com? This way the original URL the client types in will be
preserved and your server could programatically determine which catalog to
use.

-Rob, Microsoft
-------------------- 
<dGxaJuw2DHA.2900@cpmsftngxa07.phx.gbl> 
microsoft.public.commerceserver.setup.deploymentoperations:3223 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]