Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

 
 
SharePoint Portal Server 2003 IT Documentation
Search
Search
 
Check for updates: (c) Microsoft
Office downloads
 
 
 
Versions
Table of Contents
 
Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.
Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version Bookmark and ShareShare
Deploying a Large Server Farm
 

For Microsoft Office SharePoint Portal Server 2003, you must set up and configure a large server farm according to the following instructions. Following these steps ensures a supported configuration.

You must configure the servers in your server farm as follows:

  • Two or more front-end Web servers.
  • Two or more search servers. It is recommended that you have no more than four search servers.
  • One or more index management servers, one of which is the job server. It is recommended that you have no more than four index management servers.
  • One or more computers running Microsoft SQL Server 2000.
  • Optional: One computer running the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

Operating System and Setup Requirements

Ensure that you have installed Microsoft Windows Server 2003 before you install SharePoint Portal Server.

Set up Windows Network Load Balancing

Note  You can use other network load balancing solutions.

You must be logged on to the computer as a member of the local Administrators group to complete this procedure.

Note  You can perform the following steps to set up network load balancing. In addition, you can use Network Load Balancing (NLB) Manager to help configure network load balancing.

  1. Set a static IP on the front-end network interface card (NIC). To do this:
    1. Click Start, point to Control Panel, and then click Network Connections.
    2. Right-click Front-End NIC and click Properties.
    3. In the This connection uses the following items area, select the Internet Protocol (TCP/IP) check box.
    4. Click Properties.
    5. Select Use the following IP address.
      1. In the IP address box, type your assigned front-end static IP.
      2. In the Subnet mask box, type your assigned front-end subnet mask, if needed.
      3. In the Default gateway box, type your assigned front-end gateway, if needed.
    6. Select Use the following DNS server addresses.
    7. In the Preferred DNS server and Alternate DNS server boxes, type the appropriate IPs.
    8. Click Advanced.
    9. On the IP Settings tab, in the IP addresses section, click Add.
    10. In the IP address box, type the virtual IP address.
    11. In the Subnet mask box, type the subnet mask.
    12. Click Add, and then click OK.

    Note  The virtual IP address is the load-balanced IP address that is the entry point to your server farm.

  2. On the LAN Connection Properties dialog box, in the This connection uses the following items area, select the Network Load Balancing check box.
  3. Click Properties.
  4. On the Cluster Parameters tab, do the following:
    1. In the IP address box, type the cluster IP.

      Cluster IP is the virtual IP address that is the entry point to your server farm. This IP address will need to be mapped to a DNS entry so that you can type the name of the cluster from Microsoft Internet Explorer instead of typing the IP address.

    2. In the Subnet mask box, type the subnet mask.

      Use the same subnet mask for this NIC as reported by IPCONFIG /ALL for this NIC.

    3. In the Full Internet name box, type the DNS name.

      Note  If you are using Microsoft Windows Internet Name Service (WINS) resolution, enter the WINS name without the domain extension. For example, enter server_farm instead of server_farm.organization.com.

    4. In the Cluster operation section, click Unicast (the default choice).
    5. Leave the Allow remote control check box at its default (cleared) setting.
  5. On the Host Parameters tab, do the following:
    1. In the Priority box, enter 1 on your first front-end Web server and 2 on your second front-end Web server.
    2. In the Dedicated IP Configuration area, in the IP address box, type the address originally assigned to this front-end NIC.

      Note  You are assigning two IP addresses to the front-end NIC.

    3. In the Subnet mask box, type the subnet mask originally assigned to this front-end NIC.
    4. Do not change any of the settings in the Initial host state section.
  6. On the Port Rules tab, click Edit.
  7. In the Filtering mode section, click Multiple host.
  8. In the Affinity group, click None.

    Note  SharePoint Portal Server works with affinity, if a third-party application requires it.

  9. Click OK, and then click OK again.

    Note  If you see a dialog box stating that you must enter the new address in the TCP/IP component, you have not completed all of the previous steps. Click OK, and then do the following before you proceed:

    1. In the Properties dialog box for the front-end NIC, on the General tab, click Internet Protocol (TCP/IP), and then click Properties.
    2. Click Advanced.
    3. On the IP Settings tab, in the IP addresses section, click Add.
    4. In the IP address box, type the virtual IP address.
    5. In the Subnet mask box, type the subnet mask.
    6. Click Add, and then click OK.
  10. Restart the server.
  11. Repeat the previous steps on all front-end Web servers. Ensure that you change the priority setting on each one to be unique.
  12. Test network load balancing before installing SharePoint Portal Server:
    1. Open a command prompt, and then ping the virtual name of the server farm from a client computer that is not part of the server farm. For example, if server_farm is the name you entered as the full Internet name or you are using WINS, you would type ping server_farm. Server_farm is the virtual server farm name in this example.
    2. Ensure that you receive a reply.
      • If you receive no reply, ping your server farm by using the virtual IP address for the server farm. The virtual IP address is the cluster IP address that you specified in a previous step.
      • If you receive no reply, contact your network operations contact for DNS/WINS, routing, and static IP support.
    3. Type ping virtual_server_farm_name -t.

      This performs a continuous ping.

    4. On the first front-end Web server, do the following:
      1. On the taskbar, click Start, point to Control Panel, point to Network Connections, and then click Local Area Connection for the NIC associated with network load balancing.
      2. On the General tab, click Disable.
    5. On the second front-end Web server, do the following:
      1. On the taskbar, click Start, point to Control Panel, point to Network Connections, and then click Local Area Connection for the NIC associated with network load balancing.
      2. On the General tab, click Disable.
    6. On the client computer that is continuously pinging the virtual name of the server farm, you should see a message that the request timed out.
    7. On the first front-end Web server, on the taskbar, click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection for the NIC associated with network load balancing, and then click Enable.
    8. On the client computer that is continuously pinging the virtual name of the server farm, you should see a reply to the ping within 10 seconds. If you do not see a reply, ensure that your network load balancing configuration and your network configuration are correct.
    9. On the first front-end Web server, do the following:
      1. On the taskbar, click Start, point to Control Panel, point to Network Connections, and then click Local Area Connection for the NIC associated with network load balancing.
      2. On the General tab, click Disable.
    10. On the client computer that is continuously pinging the virtual name of the server farm, you should see a message that the request timed out.
    11. On the second front-end Web server, on the taskbar, click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection for the NIC associated with network load balancing, and then click Enable.
    12. On the client computer that is continuously pinging the virtual name of the server farm, you should see a reply to the ping within 10 seconds. If you do not see a reply, ensure that your network load balancing configuration and your network configuration are correct.
    13. On the second front-end Web server, do the following:
      1. On the taskbar, click Start, point to Control Panel, point to Network Connections, and then click Local Area Connection for the NIC associated with network load balancing.
      2. On the General tab, click Disable.
    14. On the client computer that is continuously pinging the virtual name of the server farm, you should see a message that the request timed out.
    15. On the first front-end Web server, on the taskbar, click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection for the NIC associated with network load balancing, and then click Enable.
    16. On the second front-end Web server, on the taskbar, click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection for the NIC associated with network load balancing, and then click Enable.
    17. On the client computer that is continuously pinging the virtual name of the server farm, press CTRL+C to break the ping cycle.

Note  When the back-end NICs of the front-end Web servers and the client computers accessing them are on the same subnet, the back-end NICs will respond to the client computers instead of the load-balanced front-end NICs. This can cause performance to degrade. The back-end NICs will be flooded with traffic to client computers, and propagations to the front-end Web servers will be competing for bandwidth.

Note  It is recommended that you implement some type of health checking to monitor the front-end Web servers. The worker process recycles nightly. During this time, the front-end Web servers remain active in the network load-balanced cluster. The load balance solution continues to distribute the load to all computers, including those that will not respond because the worker process is recycling. To avoid this issue, it is recommended that you implement health checking to monitor the front-end Web servers and remove them from the server farm when they are not available.

Perform all pre-setup server farm preparations

Note  Ensure that you use the same domain account (in the form DOMAIN\domain_account) wherever you see domain account in the server farm instructions. Do not use different accounts for each instance of the domain account.

The domain account that you are adding here is used as the configuration database administration account. This account is used later in the installation section.

  1. Log on to each server as a local or domain administrator.
  2. Add a domain account to the local Power Users group on each computer in the server farm, except on the computer running SQL Server.

    Note  You must add the domain account to the local Administrators group on any server that hosts the components for backward-compatible document libraries.

  3. On the computer running SQL Server, do the following:
    1. Configure the MSSQLSERVER service to start automatically, and then confirm that the service starts successfully at startup.
    2. Configure the domain account that you added to the server farm computers to have the Security Administrators and Database Creators server roles on this SQL Server instance.

Install Microsoft Office SharePoint Portal Server 2003

On the front-end Web servers, the search servers, the index management and job server, and on any additional index management servers, do the following:

  1. Log on to the computer running Windows Server 2003 as a local or domain administrator.
  2. Insert the SharePoint Portal Server CD into your CD-ROM drive.
  3. Click Install Microsoft Office SharePoint Portal Server 2003 components.
  4. On the Install Microsoft Office SharePoint Portal Server 2003 page, click Next.

    A message about services that will be stopped appears.

  5. If you want to stop the listed services and continue Setup, click OK.

    Setup installs Windows SharePoint Services, and then the Welcome to the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page appears.

  6. On the Welcome to the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, click Next.
  7. On the End-User License Agreement page, read the license agreement. If you accept the terms of the agreement, select the I accept all of the terms in the license agreement check box, and then click Next.
  8. On the Product Key page, type the product key in the spaces provided, and then click Next.

    The product key is located on the back of your SharePoint Portal Server CD case or on your Certificate of Authenticity. If the number that you type is not accepted, check the following:

    • If you are using the numeric keypad on your keyboard, ensure that NUM LOCK is on.
    • Ensure that you are not using the letter I for the number one.
    • Ensure that you are not using the letter O for the number zero.
  9. On the Installation Type and File Location page, do the following:
    1. Click Install without database engine.
    2. To specify file locations, click Browse, and then specify a location.
    3. Click Next.
  10. On the Microsoft Office SharePoint Portal Server 2003 page requesting account information, do the following:
    1. In the Account name box, type the user account name to be used for administrative operations that create, modify, or grant access to the configuration or portal site databases.

      The account must be a member of the Power Users group on this server. The account must have the Database Creators and Security Administrators server roles on this SQL Server instance. In addition, the account must be a domain account if you have more than one server in your configuration.

      Specifying an account that is a member of the local Administrators group on the server on which you are installing SharePoint Portal Server is not recommended.

      Important  The following user rights are granted automatically to this account (the configuration database administration account) on the local server: Replace a process level token, Adjust memory quotas for a process, and Log on as a service. If you change this account by using the Configure Server Farm Account Settings page, the rights are not revoked automatically for the previous account. However, you can remove these rights by using Local Security Settings. To open Local Security Settings, click Start, point to Administrative Tools, and then click Local Security Policy.

      Type the account name in the format DOMAIN\user_name.

    2. In the Password box, type the password for the account.
    3. Click Next.
  11. On the Install Microsoft Office SharePoint Portal Server 2003 page, click Next.

    Note  It may take up to one minute for the Next button to become active.

  12. On the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, click Finish.

Configure the first front-end Web server

On the first front-end Web server, after you click Finish on the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, the Configure Server Farm Account Settings page appears.

Using an instance of Internet Explorer that is running on the computer that you have designated as the first front-end Web server, do the following:

  1. On the Configure Server Farm Account Settings page, do the following:
    1. In the Default Content Access Account section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.

        This account is an existing Windows account that is used as the default account when creating a content index of content sources. The account must have read access to the content being crawled.

      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    2. In the Portal Site Application Pool Identity section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.
      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    3. Click OK.
  2. On the Specify Configuration Database Settings for server_name page, do the following:
    1. In the Database Connections section, click Create configuration database.
    2. In the Configuration Database Server section, in the Database server box, type the name of the computer running Microsoft SQL Server.

      This is the server on which the configuration database will be stored.

      Note  If you have a named SQL Server instance, specify both the name of the computer running SQL Server and the SQL Server instance name in the format server_name\SQL_instance_name.

    3. In the Configuration Database Name section, do one of the following:
      • If you want to use the default database name that is displayed, click Use default name.
      • If you want to specify a name for the database, click Specify custom name, and then, in the Custom Name box, type a name for the database.

        You might specify a custom configuration database name so that you can host multiple server farms on a single SQL Server instance.

    4. Click OK.
  3. On the Configure Server Farm Account Settings page, do the following:
    1. In the Contact E-mail Address section, in the E-mail address box, type the e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site.
    2. In the Proxy Server Settings section, do one of the following:
      • Click Do not connect by using a proxy server.
      • Click Use the proxy server specified, and then specify the following:
        1. In the Address box, type the address of the proxy server that you want SharePoint Portal Server to use while creating content indexes.
        2. In the Port box, type the port number for the proxy server that you want SharePoint Portal Server to use while creating indexes of sites and servers.
        3. If you do not want SharePoint Portal Server to use the proxy server when creating an index of local addresses, select the Bypass proxy server for local (intranet) addresses check box.
        4. If you have specific addresses for which you do not want to use the proxy server, in the Do not use proxy server for addresses beginning with box, type the addresses.
    3. Click OK.
  4. On the Configure Server Topology page, click Change Components.
  5. On the Change Component Assignments page, select the Web check box for the first front-end Web server.

    Ensure that the Search and Index check boxes are cleared for the first front-end Web server, and ensure that -none- appears for the job server component and that the box for the document library server is empty.

  6. Click OK.
  7. On the Configure Server Topology page, click Close.

Configure additional front-end Web servers

You must configure at least two front-end Web servers when deploying a large server farm.

On the second front-end Web server, after you click Finish on the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, the Configure Server Farm Account Settings page appears.

Using an instance of Internet Explorer that is running on the computer that you have designated as the second front-end Web server, do the following:

  1. On the Configure Server Farm Account Settings page, do the following:
    1. In the Default Content Access Account section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.

        This account is an existing Windows account that is used as the default account when creating a content index of content sources. The account must have read access to the content being crawled.

      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    2. In the Portal Site Application Pool Identity section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.
      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    3. Click OK.
  2. On the Specify Configuration Database Settings for server_name page, do the following:
    1. In the Database Connections section, click Connect to existing configuration database.

      In the following steps, you should choose the same server, instance, and database name that you specified when you created the configuration database.

    2. In the Configuration Database Server section, in the Database server box, type the name of the computer running Microsoft SQL Server.

      This is the server on which the configuration database is stored.

      Note  If you have a named SQL Server instance, specify both the name of the computer running SQL Server and the SQL Server instance name in the format server_name\SQL_instance_name.

    3. In the Configuration Database Name section, do one of the following:
      • If you want to use the default database name that is displayed, click Use default name.
      • If you want to specify a name for the database, click Specify custom name, and then, in the Custom Name box, type a name for the database.
    4. Click OK.
  3. On the Configure Server Farm Account Settings page, do the following:
    1. In the Contact E-mail Address section, in the E-mail address box, type the e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site.
    2. In the Proxy Server Settings section, do one of the following:
      • Click Do not connect by using a proxy server.
      • Click Use the proxy server specified, and then specify the following:
        1. In the Address box, type the address of the proxy server that you want SharePoint Portal Server to use while creating content indexes.
        2. In the Port box, type the port number for the proxy server that you want SharePoint Portal Server to use while creating indexes of sites and servers.
        3. If you do not want SharePoint Portal Server to use the proxy server when creating an index of local addresses, select the Bypass proxy server for local (intranet) addresses check box.
        4. If you have specific addresses for which you do not want to use the proxy server, in the Do not use proxy server for addresses beginning with box, type the addresses.
    3. Click OK.
  4. On the Configure Server Topology page, click Change Components.
  5. On the Change Component Assignments page, select the Web check box for the second front-end Web server.

    Ensure that the Search and Index check boxes are cleared for the second front-end Web server, and ensure that -none- appears for the job server component and that the box for the document library server is empty.

  6. Click OK.
  7. On the Configure Server Topology page, click Close.

Configure the first search server

On the first search server, after you click Finish on the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, the Configure Server Farm Account Settings page appears.

Using an instance of Internet Explorer that is running on the computer that you have designated as the first search server, do the following:

  1. On the Configure Server Farm Account Settings page, do the following:
    1. In the Default Content Access Account section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.

        This account is an existing Windows account that is used as the default account when creating a content index of content sources. The account must have read access to the content being crawled.

      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    2. In the Portal Site Application Pool Identity section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.
      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    3. Click OK.
  2. On the Specify Configuration Database Settings for server_name page, do the following:
    1. In the Database Connections section, click Create configuration database.
    2. In the Configuration Database Server section, in the Database server box, type the name of the computer running Microsoft SQL Server.

      This is the server on which the configuration database will be stored.

      Note  If you have a named SQL Server instance, specify both the name of the computer running SQL Server and the SQL Server instance name in the format server_name\SQL_instance_name.

    3. In the Configuration Database Name section, do one of the following:
      • If you want to use the default database name that is displayed, click Use default name.
      • If you want to specify a name for the database, click Specify custom name, and then, in the Custom Name box, type a name for the database.

        You might specify a custom configuration database name so that you can host multiple server farms on a single SQL Server instance.

    4. Click OK.
  3. On the Configure Server Farm Account Settings page, do the following:
    1. In the Contact E-mail Address section, in the E-mail address box, type the e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site.
    2. In the Proxy Server Settings section, do one of the following:
      • Click Do not connect by using a proxy server.
      • Click Use the proxy server specified, and then specify the following:
        1. In the Address box, type the address of the proxy server that you want SharePoint Portal Server to use while creating content indexes.
        2. In the Port box, type the port number for the proxy server that you want SharePoint Portal Server to use while creating indexes of sites and servers.
        3. If you do not want SharePoint Portal Server to use the proxy server when creating an index of local addresses, select the Bypass proxy server for local (intranet) addresses check box.
        4. If you have specific addresses for which you do not want to use the proxy server, in the Do not use proxy server for addresses beginning with box, type the addresses.
    3. Click OK.
  4. On the Configure Server Topology page, click Change Components.
  5. On the Change Component Assignments page, select the Search check box for the first search server.

    Ensure that the Web and Index check boxes are cleared for the first search server, and ensure that -none- appears for the job server component and that the box for the document library server is empty.

  6. Click OK.
  7. On the Configure Server Topology page, click Close.

Configure additional search servers

You must configure at least two search servers when deploying a large server farm.

On the second search server, after you click Finish on the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, the Configure Server Farm Account Settings page appears.

Using an instance of Internet Explorer that is running on the computer that you have designated as the second search server, do the following:

  1. On the Configure Server Farm Account Settings page, do the following:
    1. In the Default Content Access Account section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.

        This account is an existing Windows account that is used as the default account when creating a content index of content sources. The account must have read access to the content being crawled.

      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    2. In the Portal Site Application Pool Identity section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.
      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    3. Click OK.
  2. On the Specify Configuration Database Settings for server_name page, do the following:
    1. In the Database Connections section, click Connect to existing configuration database.

      In the following steps, you should choose the same server, instance, and database name that you specified when you created the configuration database.

    2. In the Configuration Database Server section, in the Database server box, type the name of the computer running Microsoft SQL Server.

      This is the server on which the configuration database is stored.

      Note  If you have a named SQL Server instance, specify both the name of the computer running SQL Server and the SQL Server instance name in the format server_name\SQL_instance_name.

    3. In the Configuration Database Name section, do one of the following:
      • If you want to use the default database name that is displayed, click Use default name.
      • If you want to specify a name for the database, click Specify custom name, and then, in the Custom Name box, type a name for the database.
    4. Click OK.
  3. On the Configure Server Farm Account Settings page, do the following:
    1. In the Contact E-mail Address section, in the E-mail address box, type the e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site.
    2. In the Proxy Server Settings section, do one of the following:
      • Click Do not connect by using a proxy server.
      • Click Use the proxy server specified, and then specify the following:
        1. In the Address box, type the address of the proxy server that you want SharePoint Portal Server to use while creating content indexes.
        2. In the Port box, type the port number for the proxy server that you want SharePoint Portal Server to use while creating indexes of sites and servers.
        3. If you do not want SharePoint Portal Server to use the proxy server when creating an index of local addresses, select the Bypass proxy server for local (intranet) addresses check box.
        4. If you have specific addresses for which you do not want to use the proxy server, in the Do not use proxy server for addresses beginning with box, type the addresses.
    3. Click OK.
  4. On the Configure Server Topology page, click Change Components.
  5. On the Change Component Assignments page, select the Search check box for the second search server.

    Ensure that the Web and Index check boxes are cleared for the second search server, and ensure that -none- appears for the job server component and that the box for the document library server is empty.

  6. Click OK.
  7. On the Configure Server Topology page, click Close.

Configure the index management and job server

On the index management and job server, after you click Finish on the Completing the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, the Configure Server Farm Account Settings page appears.

Using an instance of Internet Explorer that is running on the computer that you have designated as the index management and job server, do the following:

  1. On the Configure Server Farm Account Settings page, do the following:
    1. In the Default Content Access Account section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.

        This account is an existing Windows account that is used as the default account when creating a content index of content sources. The account must have read access to the content being crawled.

      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    2. In the Portal Site Application Pool Identity section, do the following:
      1. In the User name box, type the account name in the format DOMAIN\user_name.
      2. In the Password box, type the password for the account.
      3. In the Confirm Password box, type the password again.
    3. Click OK.
  2. On the Specify Configuration Database Settings for server_name page, do the following:
    1. In the Database Connections section, click Connect to existing configuration database.

      In the following steps, you should choose the same server, instance, and database name that you specified when you created the configuration database.

    2. In the Configuration Database Server section, in the Database server box, type the name of the computer running Microsoft SQL Server.

      This is the server on which the configuration database is stored.

      Note  If you have a named SQL Server instance, specify both the name of the computer running SQL Server and the SQL Server instance name in the format server_name\SQL_instance_name.

    3. In the Configuration Database Name section, do one of the following:
      • If you want to use the default database name that is displayed, click Use default name.
      • If you want to specify a name for the database, click Specify custom name, and then in the Custom Name box, type a name for the database.
    4. Click OK.
  3. On the Configure Server Farm Account Settings page, do the following:
    1. In the Contact E-mail Address section, in the E-mail address box, type the e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site.
    2. In the Proxy Server Settings section, do one of the following:
      • Click Do not connect by using a proxy server.
      • Click Use the proxy server specified, and then specify the following:
        1. In the Address box, type the address of the proxy server that you want SharePoint Portal Server to use while creating content indexes.
        2. In the Port box, type the port number for the proxy server that you want SharePoint Portal Server to use while creating indexes of sites and servers.
        3. If you do not want SharePoint Portal Server to use the proxy server when creating an index of local addresses, select the Bypass proxy server for local (intranet) addresses check box.
        4. If you have specific addresses for which you do not want to use the proxy server, in the Do not use proxy server for addresses beginning with box, type the addresses.
    3. Click OK.
  4. On the Configure Server Topology page, click Change Components.
  5. On the Change Component Assignments page, do the following:
    1. Select the Index check box.

      Ensure that the Web and Search check boxes in the row for the index management and job server are cleared.

    2. In the Job Server Component section, in the Job server list, select the server you are configuring as the job server.
    3. Ensure that the box for the document library server is empty.
    4. Click OK.
  6. On the Configure Server Topology page, click Close.

Create a portal site from the first front-end Web server

  1. On the SharePoint Portal Server Central Administration for server_name page, in the Portal Site and Virtual Server Configuration section, click Create a portal site.
  2. On the Create Portal Site for server_name page, do the following:
    1. In the Portal Creation Options section, click Create a portal.
    2. In the Site Name section, in the Name box, type a name for the portal site.

      This name appears at the top of most portal site pages.

    3. In the Site URL section, do the following:
      1. In the Virtual server list, click the virtual server for this portal site.
      2. In the URL box, type the URL that users will use to connect to the portal site.

        Note  This is the load-balanced URL, not the local server URL.

        By default, this URL is http://server_name/. If you are not creating the portal site on the Default Web Site but on another virtual server, the URL includes the port number, for example, http://server_name:port_number/.

    4. In the Owner section, do the following:
      1. In the Account name box, type the account name for the site owner in the format DOMAIN\username.

        The site owner manages portal site content and user access.

      2. In the E-mail address box, type the e-mail address for the portal site owner.
    5. Click OK.
  3. On the Create Portal Site Confirmation for server_name page, click OK to begin creating the portal site.

    The Operation Status page appears.

Extend the virtual server on the second front-end Web server

If you have more than one front-end Web server, you must do the following on each additional front-end Web server:

  1. On the taskbar, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Central Administration.
  2. On the SharePoint Portal Server Central Administration for server_name page, in the Portal Site and Virtual Server Configuration section, click Extend an existing virtual server from the Virtual Server List page.
  3. On the list of virtual servers, click Default Web Site.
  4. On the Extend Virtual Server page, in the Provisioning Options section, click Extend and map to another virtual server.
  5. On the Extend and Map to Another Virtual Server page, in the Server Mapping section, select Default Web Site from the Host name or IIS virtual server name list.
  6. In the Application Pool section, do the following:
    1. Click Use an existing application pool.
    2. From the application pool list, click MSSharePointPortalAppPool.
  7. Click OK.
  8. On the Refresh Config Cache on Other Web front end servers page, click OK.

Optional: Install and configure the components for backward-compatible document libraries

You can install the components for backward-compatible document libraries on a separate computer.

Install the components for backward-compatible document libraries

  1. Log on to the computer running Microsoft Windows Server 2003 as a local or domain administrator.
  2. Do the following to ensure that the proxy server settings for Internet access are specified correctly:
    1. Click Start, point to Control Panel, and then click Internet Options.
    2. In the Internet Properties dialog box, click the Connections tab.
    3. Click LAN Settings.
    4. In the Local Area Network (LAN) Settings dialog box, in the Automatic configuration section, ensure that both check boxes are cleared.
    5. If you use a proxy server, in the Proxy server section, do the following:
      1. Select the Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections) check box.
      2. Select the Bypass proxy server for local addresses check box.
      3. In the Address box, type a valid proxy server address.
      4. In the Port box, type the port number for the proxy server.
      5. Click Advanced.
      6. In the Proxy Settings dialog box, select the Use the same proxy server for all protocols check box, and then click OK.
    6. Click OK to close the Local Area Network (LAN) Settings dialog box.
    7. Click OK to close the Internet Options dialog box.
  3. Insert the SharePoint Portal Server CD into your CD-ROM drive.
  4. Click Install optional components.
  5. On the installation page for optional components, click Install server and client components for backward-compatible document libraries.
  6. On the Welcome to the Document Library Setup Wizard page, click Next.
  7. On the License Agreement page, click I agree, and then click Next.
  8. On the Product Identification page, type the product key in the spaces provided, and then click Next.

    The product key is located on the back of your SharePoint Portal Server CD case or on your Certificate of Authenticity. If the number you type is not accepted, check the following:

    • If you are using the numeric keypad on your keyboard, ensure that NUM LOCK is on.
    • Ensure that you are not using the letter I for the number one.
    • Ensure that you are not using the letter O for the number zero.
  9. On the Document library component of Microsoft Office SharePoint Portal Server 2003 Setup page, specify the location on the server disk where you want to install the program and data files for the document library component.

    Note  If you are installing the optional components on a server that already has SharePoint Portal Server installed, you cannot choose the location for the program files. If you are installing the optional components on a server that does not have SharePoint Portal Server installed, you can choose the location for the program files.

    You can change the installation location for these files by clicking Change Folder.

    SharePoint Portal Server also installs additional required files on the operating system drive. Click Disk Information for information about the amount of disk space required and the amount remaining. If there are existing files in the installation paths, Setup removes these files.

    The path must meet the following restrictions:

    • The path name can have a maximum length of 80 characters.
    • The path name can contain only characters in the lower ASCII range.
    • The path cannot point to a root directory. For example, E:\ is not allowed, but E:\Installation is allowed.
  10. Click Next.

    A message that lists services that will be stopped appears.

  11. Click OK to stop the services and continue.

    The Component Progress page appears.

  12. On the Completing the Document Library Setup Wizard page, click Finish.

    You might be prompted to restart your computer.

Use the first front-end Web server to configure the components for backward-compatible document libraries

  1. Log on to the first front-end Web server, and then go to the SharePoint Portal Server Central Administration for server_name page.
  2. On the SharePoint Portal Server Central Administration for server_name page, in the Server Configuration section, click Configure server topology.
  3. On the Configure Server Topology page, click Change Components.
  4. On the Change Component Assignments page, in the Document Library Server Component (Optional) section, in the Document library server box, type the address of the server to run the document library server component.
  5. Click OK.
  6. On the Configure Server Topology page, click Close.

Create a document library

  1. Log on to the first front-end Web server, and then go to the SharePoint Portal Server Central Administration for server_name page.
  2. On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Configure document libraries (Web Storage System-based).
  3. On the List and Manage Document Libraries page, do the following:
    1. If you have previously specified a Simple Mail Transfer Protocol (SMTP) server (by using the Configure e-mail server settings link on the SharePoint Portal Server Central Administration for server_name page), you might need to synchronize the settings for the portal site server and the document library server. To do this, click Synchronize.
    2. Click Create document library.
  4. On the Create Document Library page, in the Name and Description section, do the following:
    1. In the Document library friendly name box, type the display name for the library that you are creating.

      Note  The display name cannot exceed 100 characters in length.

    2. In the Document library description box, type the description for the document library.
    3. In the Document library name box, type a word that will be used in the URL of the document library after the server name.

      For example, for a URL of http://AdventureWorks/Adventure, you would type Adventure.

  5. In the Associated Portal Site section, in the Portal site list, select the portal site to associate with this document library.

    The portal site provides search capability and the ability to personalize alerts for users of the document library. Users can get to the document library from the Document Library area on the home page of the portal site.

  6. In the Document Library Contact section, do the following:
    1. In the Contact name box, type the name of the user or group to which you are assigning overall responsibility for the document library.
    2. In the Contact e-mail address box, type the e-mail address for the contact.

      The contact e-mail address can be that of an individual user or a group. This e-mail address will be used as the reply-to address for e-mail messages sent by the document library during document approval routes.

  7. To limit the number of previous major versions of a document to retain when the document is approved, in the Document Versions section, select the Specify version limit check box, and then type a number in the Number of versions to retain box.

    Note  This setting does not affect the number of minor versions retained.

  8. Click OK.

    The Operation Status page appears. After the document library is successfully created, the List and Manage Document Libraries page appears.

Related Topics

Server Farm Deployments
See Also
advertisement
Printer-Friendly VersionPrinter-Friendly Version