16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

12 Part I: Introduction to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

In SharePoint Team Services, the term for the top-level content directory of a<br />

Web server is root Web site. In a multihosting environment, each virtual Web server<br />

that is configured on the Web server contains one top-level (root Web) site. Additionally,<br />

the term for a site within a root website in SharePoint Team Services is<br />

subweb. Subweb is a term adopted from <strong>Microsoft</strong> FrontPage websites (the original<br />

technology on which SharePoint Team Services was built). You can create multiple<br />

subwebs in a root Web site, <strong>and</strong> you can create subwebs within other subwebs.<br />

In SharePoint Portal Server 2001, the term for the top-level content directory of<br />

a Web server is workspace. The term for a site within a workspace is subdashboard.<br />

You can create additional subdashboards <strong>and</strong> personal dashboards for subprojects<br />

<strong>and</strong> individual users.<br />

In the latest version of SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>, the term site (in<br />

the SDK, the term site is called myweb) replaces the previous terms. There are two<br />

types of SharePoint sites you can use to divide site content into distinct, separately<br />

manageable sites: top-level websites <strong>and</strong> subsites. A top-level SharePoint site is the<br />

parent site of all sites in a site collection. Top-level websites can contain multiple<br />

subsites, <strong>and</strong> subsites can also contain multiple subsites, continuing for as many levels<br />

as your users require. You can use this hierarchy to create a main subsite for your<br />

entire team <strong>and</strong> create individual subsites or shared sites for side projects. Top-level<br />

websites <strong>and</strong> subsites permit different levels of control over site features <strong>and</strong> settings.<br />

Single-Server Scenario<br />

SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> supports both vertical, single-server solutions<br />

<strong>and</strong> horizontal, server farm solutions. This section describes a single-server<br />

configuration.<br />

One of the minimum system requirements for Windows SharePoint Services is<br />

the Windows Server 2003 operating system. Additionally, you must install <strong>and</strong> configure<br />

Internet Information Services (IIS) <strong>and</strong> ASP.NET before you install Windows<br />

SharePoint Services. When you install Windows SharePoint Services, it creates <strong>and</strong><br />

configures a virtual server named SharePoint Central Administration. Additionally, if<br />

you install Windows SharePoint Services in a single-server configuration, it automatically<br />

extends the existing default website that was created when you installed IIS.<br />

Windows IIS websites are also referred to as IIS virtual Web servers, virtual<br />

servers, or v-servers. In addition to the two default IIS virtual servers that are created<br />

when you install Windows SharePoint Services, you can configure as many as nine<br />

end-user virtual servers with separate application pools or 99 end-user virtual servers<br />

with a shared application pool on a single Windows Server 2003–based computer.<br />

Each IIS virtual server can host multiple SQL Server content stores. (For a<br />

discussion of application pools, please consult the Internet Information Services 6.0<br />

<strong>Resource</strong> <strong>Kit</strong>, <strong>Microsoft</strong> Press 2003.)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!