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.

■ Hosting the Single Sign-On pages<br />

■ Importing user profiles<br />

■ Performing audience calculations<br />

■ Crawling <strong>and</strong> indexing portal site content<br />

■ Hosting the Alerts service<br />

Index Management Server<br />

Chapter 5: SharePoint Portal Server Architecture 117<br />

Windows SharePoint Services combines the services of hosting site pages, crawling<br />

content, <strong>and</strong> processing search queries from clients into one front-end Web server.<br />

SharePoint Portal Server allows these services to be performed separately. An index<br />

management server is dedicated to building <strong>and</strong> updating indexes, which includes<br />

crawling content <strong>and</strong> breaking down the crawled information through the indexing<br />

process.<br />

Only one index server can crawl a content source. If you need better performance<br />

on crawls, you cannot get it by adding another index management server. To<br />

improve crawl performance, you must upgrade the server that is assigned to a particular<br />

content source. Index management servers <strong>and</strong> the indexing process are covered<br />

thoroughly in Chapter 21.<br />

Changes to Back-End Database Components<br />

Windows SharePoint Services installs one configuration database <strong>and</strong> one or more<br />

content databases for use with its sites. Even though SharePoint Portal Server installs<br />

over Windows SharePoint Services, it does not use any Windows SharePoint Services<br />

databases in their original installed state. When a portal site is created in Share-<br />

Point Portal Server, an additional three databases are created that are not in a<br />

Windows SharePoint Services deployment. A fourth database is created if the Single<br />

Sign-On service is used. SharePoint Portal Server also makes changes to the configuration<br />

database that is installed by Windows SharePoint Services.<br />

In addition to changing existing databases, SharePoint Portal Server also<br />

changes how the front-end Web servers connect to the databases. Windows Share-<br />

Point Services front-end Web servers can use <strong>Microsoft</strong> SQL Server authentication or<br />

Windows authentication to connect to back-end databases, but SharePoint Portal<br />

Server front-end Web servers can use only Windows authentication. Also, Windows<br />

SharePoint Services front-end Web servers use OLE DB to connect to back-end databases.<br />

For most connections, SharePoint Portal Server front-end servers use<br />

ADO.Net instead. Only the <strong>Microsoft</strong> SharePoint Portal Search service uses OLE DB<br />

to connect to back-end databases.

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

Saved successfully!

Ooh no, something went wrong!