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 14<br />

Shared Services<br />

In this chapter:<br />

Multiple Portal Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339<br />

Use Intra-Farm Shared Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341<br />

Configuring Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343<br />

Adding Portal Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345<br />

Recovery Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347<br />

Inter-Farm Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348<br />

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349<br />

This chapter discusses the shared services functionality of <strong>Microsoft</strong> Office Share-<br />

Point Portal Server 2003. Shared services provide common storage <strong>and</strong> management<br />

capabilities for alerts, audiences, user profiles, My Sites, <strong>and</strong> search between multiple<br />

portal sites on the same farm or between farms. This chapter will discuss when<br />

<strong>and</strong> why shared services should be used <strong>and</strong> how to enable shared services.<br />

Multiple Portal Sites<br />

There are many reasons an organization would choose to run multiple portal sites on<br />

the same server farm. For example, there could be a corporate news portal site that<br />

has information about what is going on in the company <strong>and</strong> then portal sites for each<br />

division, such as Legal, Human <strong>Resource</strong>s (HR), or Marketing. That is a perfectly fine<br />

structure, but you could also choose to have a corporate portal site with divisional<br />

topics in that portal site, <strong>and</strong> then have portal sites for each major team. For example,<br />

a software company might have portal sites for each product. It is really up to each<br />

individual organization to determine the structure of the server farm.<br />

There are several things to consider when determining how many portal sites<br />

to use, however. The first consideration is resources. Full portal sites consume a significant<br />

amount of RAM. They can also use a lot of processing power, depending on<br />

the number of users. In a single-server environment or small server farm, it is expensive<br />

to host many non–shared services portal sites. Each non–shared services portal site<br />

339

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

Saved successfully!

Ooh no, something went wrong!