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.

Chapter 13: Installing <strong>and</strong> Configuring Windows SharePoint Services in an Extranet 321<br />

servers <strong>and</strong> uses the TCP/IP networking protocol to route requests. Because<br />

NLB (<strong>and</strong> other software load-balancing solutions) run on the Web front-end<br />

servers, it uses the Web front-end system resources, trimming the resources<br />

you can use for serving Web pages. However, the impact on system resources<br />

is not great, <strong>and</strong> a software solution can h<strong>and</strong>le up to 32 Web front-end servers.<br />

■ Software configuration solutions, such as using the domain name system<br />

to route requests. You can configure your domain name system (DNS) to<br />

create a primitive load-balancing system. For more information about DNS, see<br />

your Windows Server 2003 documentation.<br />

■ Hardware load balancing. This method uses hardware such as a router or<br />

switch box. Load-balancing hardware uses your network to direct website traffic<br />

between your Web front-end servers. Load-balancing hardware is more<br />

expensive to set up than software but does not use up any of your Web frontend<br />

server resources to run <strong>and</strong> is the most scalable method. Windows Share-<br />

Point Services can be used with any load-balancing hardware. In addition,<br />

hardware load balancing provides the best use of your Web front-end server<br />

resources.<br />

You do not need to perform any configuration steps to make Windows Share-<br />

Point Services work with any of these load-balancing methods. Simply set up the<br />

load-balancing method in your server farm, <strong>and</strong> either install or continue using Windows<br />

SharePoint Services.<br />

Preparing the Database Back-End Servers<br />

To set up your database back-end servers, you must perform the following steps:<br />

■ Install SQL Server 2000, Service Pack 3. You can use SQL Server 2000<br />

St<strong>and</strong>ard or Enterprise Edition with Windows SharePoint Services. For more<br />

information about installing SQL Server, see the SQL Server 2000 documentation.<br />

■ Set a strong password for your SQL Server administration account. You<br />

must know both the administrator user account <strong>and</strong> password to be able to<br />

connect between Windows SharePoint Services on the front-end Web servers<br />

<strong>and</strong> SQL Server on the back-end servers. You should set a strong password<br />

for the administration account. If you are using Windows Authentication (recommended),<br />

you should use a domain account with permissions to create databases<br />

in SQL Server. If you are using SQL Server authentication, the<br />

“sa” account should have a strong password. For more information about<br />

setting the administrator user name <strong>and</strong> password, see the SQL Server 2000<br />

documentation.<br />

■ Configure the authentication method for connections between the Web<br />

servers <strong>and</strong> SQL Server. For better security in your server farm, you should<br />

use <strong>Microsoft</strong> Windows NT authentication, rather than SQL Server authentication,

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

Saved successfully!

Ooh no, something went wrong!