Microsoft Office Tutorials and References
In Depth Information
site collection level but doesn’t appear in the list for the web application itself, it was either
scoped to apply to the whole farm, was designed to only be deployed at the site collection
level (as a sandbox solution for example), or was deployed as part of a farm solution.
Manage Paths This button opens a form that specifies what data SharePoint explicitly
manages and what data it doesn’t. More importantly, it specifies what managed paths are
available, per web application, to make site collections. By default, in SharePoint, the first site
collection made in a web application gets the coveted root path (unless you specifically
configure it otherwise). That means its URL is at the root of the web application, just as in this
book’s example, the Company Site is at the root of SharePoint-80, at http://spf2. (SharePoint
prefers that there is always a site collection at the root of a web application. If you decide to
use the /sites/ path for all your site collections for some reason, Search may not work.)
SharePoint offers two different kinds of managed paths, explicit and wildcard. Explicit paths
mean the path you enter will be the address for a particular site collection’s top-level site,
such as http://spf2/managersite. You can then create a site collection and specifically give
it that address. When you create a new web application, you are prompted to create the first
site collection for that web application soon after. Usually that first site collection is put at
the root of the web application, so its address would be the web application’s address, such
as http://spf2. It can be considered an explicit path in that respect. No other site collection
in the web application can use that specific address. A wildcard path is a path that is general
and meant to hold any number of additional site collections. That’s why, when you specify a
wildcard path for a site collection, it’s referred to as a site prefix. SharePoint has a default
wildcard path for web applications, /sites/ (as in http://spf2/sites/), for you to put the rest
of the site collections in a web application. That is only an example, though; you can create as
many managed paths as you’d like. (You can see in Figure 11.8 that I am getting ready to
create a mgmt wildcard path.) Managed paths are an important part of planning the namespace
of your SharePoint sites. SharePoint managed paths are covered extensively in Chapter 10.
Keep in mind that you can make as many managed paths as you’d like, but there is a limit of
about 260 characters for a web address (which will include the name of the page the user is
on while there), so keep your paths as brief as you can.
FIGURE 11.8
The Define
Managed Paths form
Search JabSto ::




Custom Search