-
Download SP3 from Microsoft. Search http://www.microsoft.com/downloads for "SQL SP3" and download sql2ksp3.exe .
-
Run sql2ksp3.exe to unpack the files.
-
Run setup.bat from the unpacked files. Setup starts the installation wizard to walk you through the rest of the process.
The version number of SQL Server 2000 SP3 is 8.0.760 (SP3). To verify that a SQL Server is running SP3:
-
Start SQL Server Enterprise Manager.
-
Select the server and choose Action Properties General. The version information appears on the dialog box.
If SQL Server is running on a dedicated server, get the connection settings SharePoint needs during the installation process:
-
Server name .
-
Authentication type (Windows integrated or SQL).
-
If using Windows integrated authentication, record the account the SharePoint server will use to connect to the SQL server.
-
If using SQL authentication, record the SQL user name and password SharePoint will use to connect.
2.8.3. Preparing Your Host Server
If you are installing SharePoint on a server that is already hosting other web sites, be aware that installing SharePoint makes those sites unavailable at times during the installation. Before installing you should:
-
Check for integration, upgrade, and compatibility issues with existing sites.
-
Choose a time when site use is at a minimum.
-
Notify users that sites will be unavailable during installation.
-
Consider moving existing sites to another server during installation.
-
Create a full backup of the server (of course).
The following sections outline some of the integration, upgrade, and compatibility issues you may encounter.
2.8.3.1 Integrating existing sites
If you have existing web sites on the server, you need to figure out how your new SharePoint sites fit in the organization of your sites. You may make the SharePoint site the new top-level site for your server, make it subordinate to your existing top-level site, or set up separate host headers or port numbers for your existing site and new SharePoint site.
Changing the structure of an existing site affects current users and breaks links they have established to your site, but it may be the best option if you are rolling out new capabilities. In general, it is best to roll out features gradually, so you may want to do some of both. See the section "Re-Enabling Existing Sites" later in this chapter for more information.
2.8.3.2 Upgrading from SharePoint Team Services
If you're upgrading a previous installation of SharePoint Team Services V1.0, Microsoft provides a migration tool ( smigrate.exe ). Extensive instructions can be found in the Administrator's Guide ( WindowsSharePointServicesAdmin.chm ), in the section "Migrating and Upgrading Web Sites."
2.8.3.3 Coexisting with Exchange Server
If your host server is also hosting Microsoft Exchange Server, you'll need to change the authentication method used by SharePoint in IIS after SharePoint is installed (see http://support.microsoft.com/default.aspx?scid=kb;en-us;823265). Note that you can't host Portal Server and Microsoft Exchange on the same machine.
2.8.4. Installing SharePoint
I hope the preceding sections didn't scare you off. Installing SharePoint Services is actually very simple, but I wanted you to be prepared because it's critical to choose your data source before you begin. Changing a live web server is serious business, and you don't want your support line to ring off the hook. Life is a lot easier if you are starting with a new, clean server.
To start installing SharePoint:
-
Download the SharePoint Services installation ( STSV2.EXE ). Search http://www.microsoft.com/downloads for "SharePoint Services."
-
Run STSV2.EXE . The download extracts the installation files and starts the SharePoint setup program. The first step is to select your database configuration, as shown in Figure 2-20.
| In some cases, Setup may require you to restart Windows 2003 after installing some components. After you restart, you'll have to run Setup again to resume installation. | |
If you choose the Typical Installation option, Setup installs SharePoint, configures it to use WMSDE, and creates an SQL instance named machinename /SHAREPOINT which is used to contain the SharePoint configuration and content databases.
To use a local installation of SQL Server, rather than WMSDE, choose Typical Installation, then upgrade the WMSDE database to SQL Server after installation is complete.
To use a SQL Server instance on a dedicated server, choose the Server Farm option. As mentioned earlier, setting up a dedicated SQL Server is more complex than using
animal 2-20. Choosing the database configuration
the other two database configurations, but it provides much better performance and room for growth in the future.
2.8.5. Upgrading WMSDE to SQL Server
To upgrade the default WMSDE database created by the Typical Installation option to use SQL Server:
-
Install SQL Server 2000 on the web server. Be sure to include the Full-Text Search component.
-
Install SP3 (see the section "Checking SQL Server" earlier in the chapter). Installing SQL Server should upgrade the instance of the WMSDE database to use SQL Server automatically.
-
Start SQL Server Enterprise manager and register the machinename \SHAREPOINT server instance.
If SQL Server SP3 was present when you installed SharePoint with the Typical Installation option, Setup still configures SharePoint to use WMSDE. To upgrade that database to use SQL Server without reinstalling SQL, use SQL Enterprise Manager to copy the content and configuration databases from the machinename \SHAREPOINT server instance to the installed SQL Server 2000 instance; then change the SharePoint database settings using the SharePoint Central Administration site. See Appendix A for details.
2.8.6. Setting Up a Web Farm
To install SharePoint using the Web Farm option, use the SharePoint Central Administration site to configure SharePoint's IIS settings and database connection:
-
Choose the IIS application pool to use for the Central Administration site shown in Figure 2-21. IIS can run each web site in a separate process, and those processes run under a Windows identity that determines their permissions.
animal 2-21. Configuring IIS settings
-
If you change the application pool, you must run iisreset.exe to restart IIS before continuing.
-
Enter the database connection information for the SharePoint configuration database shown in Figure 2-22. The configuration database stores information about the SharePoint server and all the virtual servers it contains.
In Figure 2-22 I specified SQL server authentication rather than Windows-integrated authentication because my network is based on workgroups rather than domains. Most home networks are workgroup-based and most business networks are domain-based. You should use Windows authentication in domain-based networks since it makes administering security easier and passwords more secure.
The Active Directory Account Creation section in Figure 2-22 is used mainly by ISPs, such as those providing SharePoint hosting services. It allows SharePoint to automatically create user accounts and generate passwords, as mentioned in "Adding Members" earlier. If you're not an ISP, you'll want to keep the default setting.
animal 2-22. Configuring the database connection
2.8.7. Creating Virtual Servers
SharePoint uses separate databases for the server configuration and for virtual server content. Each virtual server in SharePoint represents a top-level web site in IIS. The content for each virtual server is contained in a database, as shown in Figure 2-23.
You can't see this association if you used WMSDE as your database because WMSDE doesn't include SQL Server Enterprise Manager. However, WMSDE creates a database instance called SHAREPOINT and then creates databases within that instance. You can find those databases on the server in C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data .
To create a new virtual server in SharePoint, create a new, top-level site in IIS. Then extend that site using SharePoint Central Administration. The following sections describe these steps in greater detail.
2.8.7.1 Creating a top-level site in IIS
To create a new top-level site in IIS:
-
On the SharePoint server, choose Start Administrative Tools Internet Information Service (IIS) Manager.
-
New
Web Site. IIS starts the Web Site Creation wizard.
-
When creating a top-level site in IIS, you can assign the site a specific IP address or port number on the server, as shown in Figure 2-24.
animal 2-24. Assigning top-level sites different IP addresses or port numbers
You can set different port numbers to handle different top-level sites on your server. In fact, that's how SharePoint configures the Central Administration siteby assigning it to an available port number. You can view that site by including the port number along with the domain, for instance http://wombat1:21960/ displays the Central Administration site on my network.
Each top-level site must have a unique IP address or port number so IIS knows where to route requests. Port 80 is the default port for HTTP requests , so whichever site you assign to port 80 is the default site for that IP address.
Networks can assign multiple IP addresses to a single server, but SharePoint only supports the All Unassigned setting: you can't host multiple IP addresses on a SharePoint server.
| You can change the port number assigned to a top-level site from the Properties dialog box in IIS after the site is created. | |
2.8.7.2 Extending the site with SharePoint
To extend a top-level site with SharePoint Central Administration:
-
Choose Start Administrative Tools SharePoint Central Administration to display the Central Administration site.
-
Complete list and select the name of the site you just created in IIS. SharePoint displays the Extend Virtual Server page.
-
Enter the IIS application pool for the site, select the database settings, and enter the contact information for the site administrator; then choose OK.
Extending a site with SharePoint configures IIS to send requests through the SharePoint ISAPI filter ( stsfltr.dll ), which then responds to those requests with data from the virtual server's content database as shown in Figure 2-25.
2.8.8. Re-Enabling Existing Sites
To re-enable non-SharePoint sites on your server after you install SharePoint services, add a unique host header for the site; host the site under a different port number; or host the site as a subsite .
Adding a host header for the site creates a unique domain for each virtual server hosted at a single IP address. For example, both http://www.mstrainingkits.com and
animal 2-25. Extending a site lets SharePoint handle requests
http://www.usingsharepoint.com refer to the IP address of my Windows 2003 server. IIS determines which site to display based on the header received with the request. To add a host header in IIS:
-
Select the site in IIS and choose Action Properties Web Site and click Advanced. IIS displays the Advanced Web Site Identification dialog.