Friday, March 22, 2013

Share Point Managed Paths

In Share point we have Managed paths for web applications. When we create a new site collection in a web application by default root site collection will be created with web application URL. Remaining site collections will create using '/site' managed path. If we want to create a site collection with the name 'test' it will take next to '/site' managed path. We can create our own managed paths in share point instead of existing.

In SharePoint 2010, "Central Administration -> Application Management--> Manage Web Applications--> 'By selecting the web application On the Top ribbon you can see the option managed paths'". You can create your own managed paths.

By default you can see two managed paths, (root) (Explicit inclusion) , sites (Wildcard inclusion). 

Explicit inclusion and Wildcard inclusion:

In explicit inclusion, you can't create more than one site collection under that managed path. For Example you have created a explicit managed path 'MyExplicitPath', You can create only one site collection, like "http://Servername:9090/MyExplicitPath", You don't have any option to create one more site collection. You can see this in the image below.

As shown the above image, you can see only one site collection with 'MyExplicitPath' managed path.

In wildcard inclusion, you can have option to create multiple site collections with the managed path. For example, you have created a managed path 'MyWildCardPath', you can add multiple site collection under http://servername:9090/MyWildCardPath/SiteCollection1http://servername:9090/MyWildCardPath/SiteCollection2http://servername:9090/MyWildCardPath/SiteCollection3....

As shown in the above image wildcard inclusion will allow text box after managed path. So that we can create multiple site collections.

we can choose Explicit inclusion to create site collections with unique site collection under a managed path and Wildcard inclusion to create multiple site collections under a managed path.

Share this

4 Responses to "Share Point Managed Paths"

  1. Please suggest me how to implement below req..

    Extending Managed paths site collections to extranet

    ​The information architecture is like this:

    we have one web application with 5 site collections in managed path. The requirement is to extend 3 site collections out of these 5 to extranet. We proposed to put these 3 site collections under a separate web applications and then extending it and using FBA for the extended zone. But it is ruled out due to Infrastructure/security constarints.

  2. @laxman.. As per your comment i got understand the following

    "You have five site collections in intranet zone. You need to make them available to extranet users."

    You can make them availablr through FBA. What is the security issue you are facing?

    You can use Alternative Access mapping also. But it will be applicable for domain users who is having permissions in that intranet site.

  3. Finding the time and actual effort to create a superb article like this is great thing. I’ll learn many new stuff right here! Good luck for the next post buddy..
    PHP training in chennai