Recently i heard from one my friend who playing SharePoint developer role. He asked what is mean by explicit inclusion. What is the purpose of it and how it works. And they knew only wild card inclusion managed path and they thought that is the one which available in SharePoint.
With this experience i would like to share the information about explaining the managed path and its uses in SharePoint.
What's in a SharePoint Managed Path?
I often hear and sense confusion about SharePoint managed paths. Managed paths are essentially 'mount points' for site collections.
There are two types of managed paths available in SharePoint.
- Explicit
- Wildcard.
What's the difference between an explicit managed path and a Wildcard managed path?
By default, the root ‘/’ managed path is explicit, meaning only one site collection can be in it and it assumes the identity of the managed path. That's how you browse to http://servername:port and get a Web page. A Web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://servername:port/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.
A Wildcard managed path is basically 180 degrees in the opposite direction. A Wildcard managed path can support hundreds or thousands of site collections, but they are appended to the managed path, like http://servername:port/sites/team, with sites being the Wildcard managed path. It will always return a 404 error when browsing directly to a Wildcard managed path. But, you can create many Wildcard MPs like teams or projects. Wildcard managed paths are like a sorting mechanism for site collections.
I hope this helps your Web application structure and design.
With this experience i would like to share the information about explaining the managed path and its uses in SharePoint.
What's in a SharePoint Managed Path?
I often hear and sense confusion about SharePoint managed paths. Managed paths are essentially 'mount points' for site collections.
There are two types of managed paths available in SharePoint.
- Explicit
- Wildcard.
What's the difference between an explicit managed path and a Wildcard managed path?
By default, the root ‘/’ managed path is explicit, meaning only one site collection can be in it and it assumes the identity of the managed path. That's how you browse to http://servername:port and get a Web page. A Web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://servername:port/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.
A Wildcard managed path is basically 180 degrees in the opposite direction. A Wildcard managed path can support hundreds or thousands of site collections, but they are appended to the managed path, like http://servername:port/sites/team, with sites being the Wildcard managed path. It will always return a 404 error when browsing directly to a Wildcard managed path. But, you can create many Wildcard MPs like teams or projects. Wildcard managed paths are like a sorting mechanism for site collections.
I hope this helps your Web application structure and design.
No comments:
Post a Comment