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.

122 Part II: SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> Architecture<br />

Individual authentication is used when users know <strong>and</strong> manage their own credentials<br />

for the enterprise application. In this case, the enterprise-application definitions<br />

map the user’s SharePoint Portal Server credentials to individual credentials<br />

needed by the enterprise application that are stored in the credential database. If a<br />

user’s credentials are not yet in the Single Sign-On credential database, the Web Part<br />

redirects the user to the Single Sign-On logon form used to enter his credentials.<br />

Once the credentials are stored in the credentials database, the mapping should<br />

happen automatically so that user intervention is no longer needed.<br />

Shared Services<br />

In SharePoint Portal Server, by default, each portal site is configured as a separate<br />

entity from other portal sites. As a separate entity, a portal site individually supports<br />

<strong>and</strong> provides needed resources for all services. If the portal sites within a server farm<br />

belong to the same organization <strong>and</strong> support the same set of users, the use of<br />

shared services can allow the portal sites to consolidate <strong>and</strong> save resources.<br />

Shared services centralizes the work required to provide services to one portal<br />

site by creating a parent/child relationship between the portal sites. When shared<br />

services is implemented, the portal site that provides the services becomes the parent<br />

while all other portal sites become children. Because the parent portal site provides<br />

services, the child portal sites are left with only site information—such as<br />

pages, areas, <strong>and</strong> lists—to support. The following lists how services change when<br />

shared service is implemented:<br />

■ Search <strong>and</strong> index. With shared services, crawling <strong>and</strong> index creation are<br />

consolidated in the parent portal site. Search requests from child portal sites<br />

are processed by the parent portal site.<br />

■ Alerts. With shared services, alerts are managed <strong>and</strong> tracked in a single alert<br />

store in the parent portal site.<br />

■ Personal sites. With shared services, personal sites are created only in the<br />

parent portal site <strong>and</strong> can be viewed <strong>and</strong> accessed from the child portal sites.<br />

The My Site portal page is also located in the parent portal site.<br />

■ User profiles. With shared services, a single user profile database is configured<br />

in the parent portal site <strong>and</strong> is accessed by the child portal sites.<br />

■ Audiences. With shared services, audiences are compiled <strong>and</strong> stored only in<br />

the parent portal site.<br />

■ Single Sign-On service. With shared services, only one Single Sign-On credentials<br />

database is created. This database is located <strong>and</strong> administered only in<br />

the parent portal site.

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

Saved successfully!

Ooh no, something went wrong!