Microsoft Office Tutorials and References
In Depth Information
case). SharePoint sets up the first SharePoint website (or as it’s called, web application ) simply to
listen for and respond to traffic on port 80. So, any requests that are addressed to that server’s address
on port 80 (the default port for HTTP traffic, and the default port for anything typed into a browser)
will be directed to the SharePoint website and therefore will be served the home page you saw in
Figure 2.35. You can have SharePoint respond to other kinds of addresses, such as a fully qualified
domain name (FQDN), but for right now, the machine name is the default.
SharePoint can seem a little anticlimactic when you first get a glimpse of it. The interface
consists of some tabs (Browse and Page, reminiscent of the Office 2010 ribbon bar tabs) and icons on the
top left of the screen; beneath the tabs are the title of the site (Team Site by default) and the name of
the page you are on (Home in this case). Under the title is a Home tab, which is on the left above a
navigation bar, called a Quick Launch bar, that goes down the left side of the page containing links
to lists, libraries, and other objects in the site. In the center of the page is the web part area, now
formatted as a wiki page (for those of you familiar with wikis), containing a web part and some rich
text and a picture as examples. At the top right are the Account menu (which always indicates the
account you are logged in with), with the search field and the help icon below.
SharePoint is not supposed to be busy and intimidating but easy on the eyes, uncluttered,
and easy to use. If you are not intimidated, then SharePoint has achieved its objective. For
details about using the new SharePoint Foundation interface, see Chapter 4, “Introduction to the
SharePoint Interface.”
That’s it. That’s all it takes to install SharePoint using the Standalone option. You are on the
home page of your first SharePoint site, ready to add users, explore the existing lists and
libraries, and do all the things you need to make it your own. You can immediately begin to use and
manage it without much, if any, additional effort. All databases and services were created and
configured automatically for you.
However, I don’t know about you, but helplessly watching a wizard do mysterious things to
my server, regardless of the immediate outcome, makes me nervous. One of the first things I do,
after a product is installed and running, is check to see what actually changed on the server in
order for the product to function properly. It’s also helpful to get to know what a good
installation looks like, under the hood, so you’ll recognize what’s missing should an install go bad. So,
now that SharePoint is up and running, let’s see what actually happened during the SharePoint
Standalone installation.
We won’t be going back to the site for a while, so feel free to close out of the browser (until we
come back later). In addition, you’re done with the installation, so feel free to exit the SharePoint
Foundation 2010 installation screen, because you’ve obviously finished using it.
Confirming Changes in the File System
During the installation process, SharePoint had to create a file structure to store the files it
requires on the server. This structure was called the 12 hive in the previous version because
the topmost folder had a 12 as its name, and all folders organized beneath it were used by
SharePoint, rather like the way settings are organized in the registry. Now the folder has gone
up to 14 (obviously Microsoft skipped version number 13) and is supposed to be called the
SharePoint root (although many will still call it the 14 hive ). This folder structure starts with a
14 folder, and all other folders and files organized beneath it are solely required by SharePoint.
This is the root file structure for all things SharePoint. Any file SharePoint needs that isn’t in a
database, particularly those web or design based, is located here (although, with a Standalone
installation, the database files are stored in the SharePoint root as well). This file structure needs
to be the same for each SharePoint server in the farm (with the exception of indexing files).
Search JabSto ::

Custom Search