Managing Paths (Windows SharePoint Services 2.0)
When you extend a virtual server, create a top-level Web site, or configure Self-Service Site Creation, you may also need to define managed paths. Managed paths allow you to perform two important tasks:
Indicate which pieces of the Uniform Resource Locator (URL) namespace are controlled by Microsoft Windows SharePoint Services.
Many organizations installing Windows SharePoint Services already have a Web server or server farm in use, and must be able to identify areas of the existing URL namespace that should not be managed by Windows SharePoint Services. For example, if you have a Web application on your Web server already, and you install Windows SharePoint Services, you need a way to tell Windows SharePoint Services not to attempt to control content in or settings for that path.
Specify paths to use for Self-Service Site Creation.
You can restrict Self-Service Site Creation users to specific paths when they create sites. By default, the path /sites is created and added as a path for Self-Service Site Creation users when you enable Self-Service Site Creation. You can create other paths for Self-Service Site Creation users, or remove the /sites path when you manage paths.
There are two categories of paths you can manage: included and excluded paths. An included path indicates that Windows SharePoint Services manages that path. An excluded path indicates that the path is managed by a different application, and that Windows SharePoint Services should leave it alone. Included paths can be further broken down into the following two types:
Explicit inclusions Includes only the specific path you set. Use explicit inclusions, for example, if you want Windows SharePoint Services to manage a specific path, such as /portal, but not any possible sites below it, such as /portal/webapp.
Wildcard inclusions Includes any sites below the path you set, so you don't have to add them individually. This is the type of inclusion to use for Self-Service Site Creation, when you want users to be able to create top-level Web sites underneath a specific path, such as /sites.
Note
Web server performance declines linearly with the number of inclusions and exclusions. You can minimize the performance impact by using wildcard inclusions rather than many explicit inclusions, and by putting as many excluded applications under the same excluded path as possible.
The following table lists example URLs and explains the types of paths.
| Path type | Example URL | Path name | Comments |
|---|---|---|---|
Explicit inclusion |
https://server1/site1 |
/site1 |
Identifies the Web site at /site1 as a Windows SharePoint Services site. |
Wildcard inclusion |
https://server1/sites/* |
/sites/* |
Identifies all sites below the /sites/ path as Windows SharePoint Services sites. |
Exclusion |
https://server1/webapp |
/webapp |
Indicates that the /webapp directory is not handled by Windows SharePoint Services. |
Top-level Web site explicit inclusion |
https://server1 |
/ |
Indicates an explicit inclusion for the top-level Web site. Only the top-level Web site is a Windows SharePoint Services site, not any other sites below the top-level Web site. |
Top-level Web site wildcard inclusion |
https://server1 |
/* |
Indicates a wildcard inclusion for the top level of the virtual server. Every directory under the specified path is a Windows SharePoint Services top-level Web site. |
Included and excluded paths are used only for directories, not pages in a Web site, and they are recursive (for example, if you exclude /mango, Windows SharePoint Services will ignore any URL beginning with /mango/ or equal to /mango). Exclusions take precedence over inclusions, so if you accidentally set a particular path to be both included and excluded, the path will be excluded. Inclusions are evaluated by length; longer URLs are checked before shorter URLs, so an inclusion for https://server1/sites/teams will be evaluated before an inclusion for https://server1/teams.
You can manage paths by using either HTML Administration pages or the command line.
Managing Paths by Using HTML Administration Pages
To include or exclude a new path, use the Define Managed Paths page for the virtual server that contains the path.
Add a new path
Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
On the Central Administration page, under Virtual Server Configuration, click Configure virtual server settings.
On the Virtual Server List page, select the virtual server you want to configure.
On the Virtual Server Settings page, under Virtual Server Management, click Define managed paths.
In the Add a New Path section, in the Path box, type the path to add.
Select Excluded path or Included path. If you select Included path, select a type (wildcard or explicit) in the Type box.
Click OK.
If you change how you use the URL namespace, and no longer need a path to be included or excluded, you can remove the path.
Remove a path
Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
On the Central Administration page, under Virtual Server Configuration, click Configure virtual server settings.
On the Virtual Server List page, select the virtual server you want to configure.
On the Virtual Server Settings page, under Virtual Server Management, click Define Managed Paths.
Under Included Paths or Excluded Paths, select the check box next to the path you want to remove, and then click Remove selected paths.
Managing Paths from the Command Line
You can use the addpath and deletepath operations to manage paths on the command line. Both operations take the -url and -type parameters. The -type parameter has three values: exclusion, explicitinclusion, and wildcardinclusion. For example, to add a new wildcard inclusion to manage all sites at the top level of https://server1, you would use syntax like the following:
stsadm -o addpath -url https://server1/ -type wildcardinclusion
You can also remove an included or excluded path by using the command line. For example, to remove an exclusion for the site at https://server1/hrweb/webapp, you would use syntax like the following:
stsadm -o deletepath -url https://server1/hrweb/webapp
Related Topics
For more information about how managed paths affect extending a virtual server, creating sites, or allowing users to create sites by using Self-Service Site Creation, see Extending Virtual Servers (Windows SharePoint Services 2.0), Creating Sites and Subsites (Windows SharePoint Services 2.0), and Configuring Self-Service Site Creation (Windows SharePoint Services 2.0).