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.

Single Server<br />

Server Farms<br />

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

In a single-server configuration, all components (both front-end <strong>and</strong> back-end) are<br />

on a single server. This configuration can use a separate installation of SQL Server or<br />

use SQL Server 2000 Desktop Engine for the back-end databases.<br />

Server farms are created in a SharePoint Portal Server environment when components<br />

are placed on separate servers. Server farms can range from small to large,<br />

depending on the needs of the environment.<br />

The components that are considered front-end are the Web server hosting the<br />

portal site, the index server crawling the content <strong>and</strong> creating the index, the search<br />

server that processes client search requests, <strong>and</strong> the job server that coordinates available<br />

services. A small server farm keeps the front-end components on the same<br />

server while separating the back-end databases onto one or more servers. Medium<br />

server farms separate the indexing functions <strong>and</strong> the job server from the front-end<br />

Web servers <strong>and</strong> search services. A large farm can h<strong>and</strong>le up to four index management<br />

servers, one of which must be a job server, <strong>and</strong> four search servers, which are<br />

separate from the Web front-end servers. To find out more about deploying server<br />

farms, see the chapters in Part 4, “Deployment Scenarios.”<br />

Personal Sites vs. My Site<br />

Personal sites <strong>and</strong> the My Site feature are separate features that are both available<br />

only in SharePoint Portal Server. Although the names of these two features are often<br />

used as synonyms for each other, they are not the same. Site administrators need a<br />

good underst<strong>and</strong>ing of the architectural differences between the two features to<br />

underst<strong>and</strong> differences in the behavior of each.<br />

Personal sites are Windows SharePoint Services sites that are created for individual<br />

users. Every user who has the Create Personal Site right can have a personal<br />

site. By default, the location of a user’s personal site is portalname/personal/username,<br />

where portalname is the name of the portal <strong>and</strong> username is the name of the<br />

individual user.<br />

My Site is a single page located in the SharePoint Portal Server site. By default,<br />

the path for this page is portalname/My Site/default.asp, where portalname is the<br />

name of the portal. Every user who accesses the My Site URL downloads the same<br />

page. However, users often don’t realize this because some of the information on<br />

the page is personalized based on the user’s profile information <strong>and</strong> information<br />

from the user’s personal site.<br />

So the difference between My Site <strong>and</strong> personal sites is that My Site is the portal<br />

page through which all users must pass to get to their own personal site. A user links<br />

to his personal site through the My Site page. It is hard to recognize that the My Site

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

Saved successfully!

Ooh no, something went wrong!