Managed Path || Wildcard Inclusion || Explicit Inclusion || Basic Concept


Yesterday I was working with my team mates and their came a requirement to create a site collection but with consideration of future also. Things need to be fulfilled with help of Managed path. So , I thought to share the concept of managed path, wildcard inclusion and explicit inclusion with you all.

Let’s work with an example. Suppose I have a SharePoint site http://abc.com or any for abc company and today I got a requirement to create 3 site collection 1 for HR , Finance and Learning and the first 2 (HR and Finance will contain no of sites & site collection in it) and constraint for the 3 Learning, is that it should be directly under the root site abc.com .

How the things will be configured and work? We have to work with Managed path.
Managed path is a concept given by Microsoft to create different site collection according to different requirement. It is a path managed by SharePoint which will specify how many site collection can reside in a particular url. SharePoint has two type of managed paths:

1) Explicit Inclusion: it is a managed path under which no further site collection can be created. By default MOSS has a root as an explicit inclusion. N no of inclusion can be created manually. So as per my requirement I have to create site collection directly under abc.com. so first I will use root explicit inclusion to create my first ever site collection http://abc.com/ . and then I will create an another explicit inclusion “/Learning” and then I have a site collection with url as http://abc.com/learning .

Constraint: in Future I will never be able to create any site collection under learning.

2) Wildcard Inclusion: It is managed path under which n number of site collection can be created. By default MOSS has sites as only wildcard inclusion. N no of inclusion can be created manually
So as per my requirement I have to create 2 site collection under which number of site and site collection can reside .So with this requirement I will create an wildcard inclusion with name /HR and /Finance and the url for that will be http://abc.com/HR and http://abc.com/finance and now I have n no of site collection under /finance and /HR . ex. /HR/dep1 & /HR/dep2

So, on working with concept of wildcard and explicit requirement should be crystal clear . so that the things can be created to suit specific purpose.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help
Ashi

About these ads
This entry was posted in MOSS 2007, SQLServerPedia and tagged , , , . Bookmark the permalink.

11 Responses to Managed Path || Wildcard Inclusion || Explicit Inclusion || Basic Concept

  1. mestreseo says:

    thanks for sharing in the above information.

  2. lista de email says:

    thanks for a great post and interesting comments. i found this post while surfing the web. thanks for sharing this article.

  3. Nick says:

    this is nice post!

  4. Gautam says:

    simply, admirable what you have done here. it is pleasing to look you express from the heart. remarkable post and will look forward to your future update.

  5. Anjani niranjan says:

    i am new to sharepoint. what is the maximum number of the site collections can be created under the wildcard ???????

    • ashishbanga says:

      Hello Anjani,

      Wild card is just a managed path.After creating a wildcard inclusion you can create N number of site collection under it. You should take care that your content db should increase more than 100 GB. It is recommended by microsoft. Usually nothing happens beyond 100 GB but in case of issues microsoft will not support the environment.

      Thanks

  6. Nikita says:

    this website makes the difference, not all bloggers have the gift to explain in some worlds something so perplexing.

  7. Zane Seratt says:

    Everything is very open with a very clear clarification of the issues. It was truly informative. Your site is very useful. Thanks for sharing.

  8. debu says:

    dhamaka……!!!!!

  9. Sudarshan Bodke says:

    Awesome article … something that I was trying out in SharePoint Central Admin. You cleared my doubts .

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s