Microsoft Office Tutorials and References
In Depth Information
IIS usually stores all websites in the file system. If you have a normal web page with the URL
http://www.mycompany.com/sales/default.html, a sales folder containing the file default
.html will reside somewhere on the IIS server (by default in the WWWroot folder). All your
website content—images, pages, scripts, and so on—will reside somewhere in the file system,
nested within the root path assigned in the IIS Web Site settings.
SharePoint, on the other hand, compiles its web pages on the fly based on the content in the
content database. This means there is no need for separate files to be stored in the local file
system for each and every page. If you create new content, such as a list named Order, or upload a
document to a library, everything will be stored in the database, not in the file system. In other
words, the Order list’s Allitems.aspx page is compiled from the master page and other
components that exist in the file system by default (depending on the site template or definition),
but the unique data and settings for that list are all stored in the content database for the site.
SharePoint web applications do have a virtual directory that contains necessary components to
display web content, but most of it is information for compiling pages on the fly.
The new London site collection (in our original http://spf2 web application) is located at
http://spf2/sites/london because the path for the URL defaulted to /sites/ when the site
collection was created.
No matter where you look in the local file system, you’ll never find a London folder with
HTML (or ASPX) files in it. Instead, all that data will be in the content database, and all other
pages for the site will be compiled when requested from shared components in the file system.
IIS and SharePoint distinguish between paths that are normal IIS websites (and exist in the
file system) and paths that are SharePoint sites (and exist in the database) by using managed
paths. A managed path is a path for which SharePoint tells IIS, “I’ll handle this request.”
With this version of SharePoint, all unspecified paths are by default excluded —they are not
managed. For a path to be used by SharePoint (and available as a path for new site collections
within the web application), it needs to be set as a managed path. SharePoint creates two
managed paths for new web applications, such as the SharePoint-80 web application created earlier
in the topic. They can be viewed in Central Administration, under Application Management
Manage Web Applications.
To see what managed paths are available for our new web application (SharePoint-8080),
make sure it is selected, and click the Managed Paths button in the ribbon. See Figure 10.41. As
you can see, there are two managed paths by default, the root and sites .
FIGURE 10.41
The Define
Managed Paths page
Search JabSto ::




Custom Search