Click to Rate and Give Feedback
TechNet
TechNet Library
Windows
Operations
 Define managed paths

  Switch on low bandwidth view
Define managed paths (Windows SharePoint Services)

Updated: 2008-01-17

Before you perform this procedure, confirm that:

Defining managed paths

Use the following procedures to define managed paths for a Web application.

ImportantImportant:

At the minimum, you must be a member of the Farm Administrators SharePoint group to complete this procedure using the user interface.

Define the managed paths for a Web application by using Central Administrator

  1. On the top link bar of the Central Administration Web site, click Application Management.

  2. On the Application Management page, in the SharePoint Web Application Management section, click Define managed paths.

  3. On the Define Managed Paths page, verify that the Web application you want is selected. If it is not, in the Web Application section, on the Web Application menu, click Change Web Application.

  4. On the Select Web Application page, click the Web application for which you want to define managed paths.

  5. After the correct Web application is selected, in the Add a New Path section, to include a new path within the URL namespace, type the path in the Path box.

  6. Click Check URL to check the URL. A Web browser will open to the specified path.

  7. In the Type list, select one of the following:

    • Wildcard inclusion to include all paths that are subordinate to the specified path.

      ImportantImportant:

      Do not use “/*” to indicate wildcard managed sites at the root of the site collection. Using this wildcard prevents a site being created at the root of the Web application. Many SharePoint features rely on having a site collection at the root of the Web application, and if this is missing, these features will not work correctly. For example, Explorer View will not work for a document library.

    • Explicit inclusion to include the site that is indicated by the specified path. Sites subordinate to the specified path are not included.

  8. To delete a path or paths, in the Included Paths section, select the check boxes for the paths that you want to delete and then click Delete selected paths.

  9. Click OK.

ImportantImportant:

The account that you use to run the Stsadm command-line tool must be a member of the Administrators group on the local computer.

Define the managed path for a Web application by using the Stsadm command-line tool

  1. On the drive where SharePoint Products and Technologies is installed, open a command-line window and type the following command:

    cd %CommonProgramFiles%\Microsoft Shared\web server extensions\12\bin

  2. To add a path, type the following command:

    stsadm -o addpath -url <http://managed path> -type {Explicitinclusion | Wildcardinclusion}

    where http://managed path is the URL path to the Web application.

    Use one of the following values for type:

    • Explicitinclusion to include the site indicated by the specified path, but not include sites subordinate to the specified path.

    • Wildcardinclusion to include all paths that are subordinate to the specified path.

    For more information, see Addpath: Stsadm operation (Windows SharePoint Services).

  3. To delete a path, type the following command:

    stsadm -o deletepath -url <http://managed path>

    where http://managed path is the URL path to the Web application.

    For more information, see Deletepath: Stsadm operation (Windows SharePoint Services).

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Known Issue related to Explicit Paths and InfoPath Forms Publishing      Richard Harbridge   |   Edit   |   Show History
If you try to publish an InfoPath form to a Site Content Type while using an explicit path you will run into an error when it tries to retrieve site columns.

This is stated as something that will be resolved in SP2 for WSS 3.0/MOSS 2007 by community but I can find no official statement declaring that it is on the list of fixes for the feb-april timeline Microsoft has set for SP2.

In my humblest of opinions after using explicit paths for some time and experiencing many issues with it (some navigation things also don't work as designed) I would recommend avoiding explicit paths when possible. (Until post SP2, in theory.)

Here are a few community references:

  • http://sheetal-d.spaces.live.com/blog/cns!237C3DEA7120098B!649.entry
  • http://www.yeschandana.com/category/InfoPath.aspx
  • http://social.msdn.microsoft.com/Forums/en-US/sharepointinfopath/thread/32f3a039-b5d0-4805-be04-388f80799da2/

Hope this helps,
Richard Harbridge

Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker