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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Shared services is an all-or-nothing configuration at the server-farm level. This<br />

means that if one portal site in a server farm is using shared services, all portal sites<br />

in that farm are using shared services. Once a portal site in a farm is designated as<br />

the parent, all other portal sites in the farm automatically become child portal sites.<br />

It is also a one-way decision, meaning that once you decide to turn on shared services,<br />

you can’t turn it off later.<br />

Database Access in Shared Services<br />

Summary<br />

When shared services is implemented, child portal sites look to the parent’s configuration<br />

database for shared services data. Although some data is still needed from<br />

the original databases used by the child sites after shared services is configured,<br />

most information is retrieved from the parent site’s databases. By default, each portal<br />

site has two user accounts that are used to access databases. These accounts are<br />

called the configuration database administration account <strong>and</strong> the application pool<br />

account for the portal site.<br />

The configuration database administration account is the account used by the<br />

CentralAdminAppPool application pool to access the configuration database <strong>and</strong><br />

all other databases for a portal site. It is recommended that all servers in a server<br />

farm use the same account for the configuration database administration account.<br />

Once shared services is implemented, this recommendation becomes a requirement.<br />

The MSSharePointPortalAppPool is used by the portal site to access the Share-<br />

Point Portal Server databases. Although child portal sites must have access to the<br />

parent configuration <strong>and</strong> content databases for added security, that access can be<br />

limited to read-only.<br />

Because SharePoint Portal Server 2003 is built on Windows SharePoint Services,<br />

much of the underlying architecture is the same. Both h<strong>and</strong>le page requests <strong>and</strong><br />

.aspx pages in the same manner. The main architectural differences lie in the way<br />

the additional services provided by SharePoint Portal Server are h<strong>and</strong>led. As the<br />

server product in <strong>Microsoft</strong> SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>, SharePoint Portal<br />

Server 2003 has additional services that support a larger <strong>and</strong> more diverse set of<br />

users. To accommodate this, additional database types <strong>and</strong> additional front-end<br />

roles are included in SharePoint Portal Server that are not included in Windows<br />

SharePoint Services.

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

Saved successfully!

Ooh no, something went wrong!