|
|
Question : Multiple URL access points into different pages in a single MOSS site collection?
|
|
Hi, Can someone explain to me how to set up the following? We want to create a single site collection split broadly into two parts: community.mydomain.com for general access and management.mydomain.com for a restricted group. We'll also have a separate mysite site collection on its own url. All access is from the internet, none from local domain. I can't see how to point URLs like the above at specific pages within a site collection. Alternate Access Mappings will do the top level so I could have community and management pointing at the same collection, but how do I make an entry point further down into the collection?
|
Answer : Multiple URL access points into different pages in a single MOSS site collection?
|
|
To my knowledge, this is not possibly with MOSS itself. As you already mentioned, the MOSS mechanism for this is the alternate access mappings, which operate at a web app level, not a site collection, or sub site level. IIS also allows you to add host-headers, but this would also be at a web application level. There may be third-party DNS or routing apps or appliances that can do this, bu not in native SharePoint.
Is there a specific reason that both DNS names need to live in the same site collection? The easiest solution would be to break them apart in to two Web apps. Another option might be to use the same URL but enable audience targeting for the management-type web parts or lists (or sites), so that they do not even appear to regular users.
|
|
|
|
|