Microsoft Office Tutorials and References
In Depth Information
There are two types of managed paths, explicit and wildcard.
Explicit Managed Path An explicit managed path is a path that is itself a SharePoint site.
Root is an explicit path because if you enter the root of the server into a browser (for example,
http://spf2:8080/ or http://spf2/), you’d get to the top-level site of a SharePoint site
collection. It’s the end of the path; it goes no further.
Wildcard Managed Path A wildcard managed path is a URL that can contain multiple site
collections. Sites, in our case, is a wildcard managed path because the path can have any
number of site collections starting from there, such as http://spf2/sites/london, http://
spf2/sites/toronto, and http://spf2/sites/cleveland.
When you create a new managed path and you want that path to host a single SharePoint site
collection, it needs to be explicit (think of it as an explicit address, “Your top-level site address
is http://spf2/”). If you want to host multiple site collections within the managed path, you
need to make it a wildcard managed path. Making it a more general address, as in “Your site is
somewhere under /sites/.”
To create a new managed path, simply specify the path (such as blogs) in the Add New Path
section of the page. Specify whether the path is explicit or wildcard, and then click Add Path
(Figure 10.42). When you create a managed path, it doesn’t close the page, assuming that you are
going to create more. The page closes only if you click OK.
You can also test the URL to make certain it works and isn’t already in use somewhere by
clicking the Check URL button. If a page comes up for that path, it’s obviously already being
used, so having the URL fail to display a page when you check it is good.
TO SLASH OR NOT TO SLASH
The Define Managed Paths page says you have to precede paths that start at the root address of the
web application with a forward slash. In my experience, this isn’t necessary.
To specify a managed path, you have to type in each path from the web application address
forward. For example, it is possible that you might want to provision some longer managed
paths for members of a presales presentation team for when they use self-service site creation to
create their blogs. (Self-service site creation lets users make their own site collections; we’ll be
covering it later in this chapter.)
In that case, instead of just adding blogs to the managed paths list as a wildcard path, you’d
need to add blogs/sales . Then the presales team users could use their names to specify their
sales blog addresses, such as http://spf2:8080/blogs/sales/BasilMullien. This also lets you
organize the paths, so other teams can have blogs, such as blogs/HR, blogs/mgmt, and so on.
DON’T NEGLECT THE ROOT
Keep in mind when planning your URL namespace that SharePoint requires a site collection at the
root path first before you add site collections to any other managed path. If you decide to use the
/sites/ path for all your site collections for some reason, Search may not work. Weird but true.
 
Search JabSto ::




Custom Search