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.

284 Part IV: Deployment Scenarios<br />

SharePoint Portal Server 2003, checks this configuration database for component<br />

assignment changes every 30 seconds. If it detects a change, the service turns on or off<br />

those portions of the SharePoint Portal Server code to run only the assigned services.<br />

For example, let’s assume you have a server in a large server farm that has been<br />

assigned the index <strong>and</strong> job server roles. Now, let’s assume that you decide to move<br />

the job server role to another index server in the farm. On both of these servers, all<br />

the SharePoint Portal Server code is installed, but when you make the service assignment<br />

change, the Admin service on the first server will “turn off” the job server role<br />

services <strong>and</strong> the Admin service on the second server will “turn on” the job server<br />

role services <strong>and</strong> assume these responsibilities. In this manner, each server in the<br />

farm will know its role in the farm, the services it is to run to “complete” the farm,<br />

<strong>and</strong> when to change its role to meet new role assignments you select on the Components<br />

Selection page.<br />

Preparing for Deploying a Farm<br />

Before building a server farm, you need to collect some information <strong>and</strong> create prerequisite<br />

accounts. Table 12-1 shows the information needed to create a portal site<br />

<strong>and</strong> includes the values for each item used for a medium farm in this chapter. The<br />

numbers <strong>and</strong> DNS entries filled in are examples. You should fill in your own IP<br />

Address Range <strong>and</strong> DNS entries based on your environment.<br />

Table 12-1 Roles, IP Addresses, <strong>and</strong> Names in a Medium Farm<br />

Physical<br />

Server DNS Name IP Address Subnet Mask Description Notes<br />

n/a cluster.sps.test.local 172.16.12.200 255.255.0.0 Corporate portal<br />

virtual host<br />

SPS-01 SPS-01.sps.test.local 172.16.12.10 255.255.0.0 Host address<br />

for front-end<br />

Web/search<br />

server SPS-01<br />

SPS-01 172.16.12.200 255.255.0.0 Cluster address<br />

for front-end<br />

Web/search<br />

server SPS-01<br />

Used for NLB<br />

If only one NIC<br />

in server, bind<br />

this address <strong>and</strong><br />

cluster address<br />

(below). If multiple<br />

NICs, choose<br />

the NIC connected<br />

to the internal<br />

network for this<br />

address.<br />

If only one NIC in<br />

server, bind this<br />

address <strong>and</strong> host<br />

address (above).<br />

If multiple NICs,<br />

choose the NIC<br />

connected to the<br />

external network<br />

for this address.

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

Saved successfully!

Ooh no, something went wrong!