16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 15: Configuring Windows SharePoint Services 373<br />

SharePoint Services should leave it alone. Included paths can be further categorized<br />

into the following two types:<br />

■ Explicit inclusions. Includes only the specific path that you set. Use explicit<br />

inclusions, for example, if you want Windows SharePoint Services to manage<br />

a specific path (such as /portal) but not any possible sites below it (such as<br />

/portal/webapp).<br />

■ Wildcard inclusions. Includes any sites below the path that you set so that<br />

you don’t have to add them individually. This is the type of inclusion to use for<br />

Self-Service Site Creation, when you want users to be able to create top-level<br />

websites underneath a specific path, such as /sites.<br />

Note Web server performance declines linearly with the number of inclusions<br />

<strong>and</strong> exclusions. You can minimize the performance impact by using<br />

wildcard inclusions rather than many explicit inclusions, <strong>and</strong> by putting as<br />

many excluded applications under the same excluded path as possible.<br />

Included <strong>and</strong> excluded paths are used only for directories, not pages in a website,<br />

<strong>and</strong> they are recursive. (For example, if you exclude /mango, Windows Share-<br />

Point Services ignores any URL beginning with /mango/ or equal to /mango.)<br />

Exclusions take precedence over inclusions, so if you accidentally set a particular<br />

path to be both included <strong>and</strong> excluded, the path is excluded. Inclusions are evaluated<br />

by length; longer URLs are checked before shorter URLs, so an inclusion<br />

for http://My_Server/sites/teams is evaluated before an inclusion for http://My_Server<br />

/teams.<br />

You can manage paths by using HTML Administration or the comm<strong>and</strong>-line<br />

administration tool. You can use the addpath <strong>and</strong> deletepath operations to manage<br />

paths on the comm<strong>and</strong> line. Both operations take the -url <strong>and</strong> -type parameters. The<br />

-type parameter has three values: exclusion, explicitinclusion, <strong>and</strong> wildcardinclusion.<br />

For example, to add a new wildcard inclusion to manage all sites at the top level of<br />

http://My_Server, you would use syntax such as the following:<br />

Stsadm –o addpath –url http://My_Server/ -type wildcardinclusion<br />

You can also remove an included or excluded path by using the comm<strong>and</strong> line.<br />

For example, to remove an exclusion for the site at http://server1/hrweb/webapp, you<br />

would use syntax such as the following:<br />

Stsadm –o deletepath –url http://My_Server/hrweb/webapp<br />

Create or Delete a Top-Level Website<br />

You can create a new top-level website or delete an existing top-level website. If you<br />

are an administrator of the server computer, you can also create sites <strong>and</strong> subsites by

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!