Best structure for Portals and Sites
From: Rob (anonymous_at_discussions.microsoft.com)
Date: 08/11/04
- Next message: AC: "RE: MCMS Page Listing Problem"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Issues with pdf files"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 11 Aug 2004 12:12:48 -0700
Not understanding Microsoft's intention fully, I have
developed a Portal site for the company with Sites
created on the Sites page for the departments in the
company. The Sites are created under the Portal hierarchy
(i.e. http://myportal.com/Sites/DeptSite/Default.aspx).
As I understand, this means that all the Sites I create
fall under the responsibility of the same virtual server.
I need 'nice' DNS entries for these sites, so I've
created empty virtual directories that map to the Site so
that I can bind 'nice' DNS entries to them. For example,
http://myportal.com/Sites/DeptSite/Default.aspx can be
visited by typing http://DeptSite.myportal.com.
I keep reading that the best practice is to contain each
sites content in its own virtual server, but I don't see
how to move things there in the right way. Also, I keep
reading about 'extending' the virtual server, but I don't
really understand what is intended by that. I've tried
extending a virtual server on a test Site, and my DNS
mapping would no longer point to it (giving a Security
Validation error).
Can anyone point me in the right direction?
- Next message: AC: "RE: MCMS Page Listing Problem"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Issues with pdf files"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|