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.

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

Server Farm Scenario<br />

Portal Sites<br />

Security<br />

Note If you are a developer, note that the SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

object model uses the (sometimes overlapping) names from<br />

SharePoint Team Services for many of the new SharePoint <strong>Products</strong> <strong>and</strong><br />

<strong>Technologies</strong> components. Use the preceding table to cross-reference<br />

terms from the old <strong>and</strong> new naming conventions.<br />

In a server farm scenario, the terminology remains the same, <strong>and</strong> the requirement<br />

that all SharePoint sites use the same SQL Server configuration database as the toplevel<br />

website remains the same. However, you can use multiple stateless front-end<br />

Web servers to support a large number of user connections <strong>and</strong> to render ASP.NET<br />

Web pages. Logically located behind these front-end Web servers, a SharePoint<br />

<strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> configuration can use many back-end database servers.<br />

You can use multiple content database servers to support multiple site collections<br />

<strong>and</strong> to provide fault-tolerant failover. Optionally, you can use separate database<br />

servers to store the configuration database for server farm configuration maps<br />

<strong>and</strong> site collection-to-content database maps.<br />

One of the minimum system requirements for SharePoint Portal Server 2003 is Windows<br />

SharePoint Services. When you install SharePoint Portal Server 2003, Setup<br />

automatically installs Windows SharePoint Services if it is not already installed.<br />

You can configure only one portal site for each end-user IIS virtual Web server.<br />

The portal site corresponds to the SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> top-level<br />

website for both the virtual server <strong>and</strong> the site collection rooted at the virtual server.<br />

The new security features in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> is described in<br />

this section. Included is an introduction to groups, authorization, <strong>and</strong> authentication.<br />

Site Groups <strong>and</strong> Rights<br />

SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> uses a security model based on site groups<br />

<strong>and</strong> rights. Site groups are groups of users with related security requirements. Security<br />

rights are assigned to each security group. You can customize the rights assigned<br />

to these site groups or add new site groups to combine different sets of rights. By<br />

default, Windows SharePoint Services includes the following five site groups:

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

Saved successfully!

Ooh no, something went wrong!