Share via

Example A: Installing on a Four-Computer Clustered Configuration

  • Article

This topic contains procedures describing how to install Commerce Server 2000 and unpack applications on a four-computer configuration consisting of:

  • Two Web servers in a Network Load Balancing (NLB) cluster. These servers also contain the Commerce Server administration tools.

  • Two SQL Servers configured as a single server cluster. These servers are referred to by their shared cluster name.

To view a figure showing this configuration, see Small Site Configuration.

Step 1: To install Commerce Server on the Web servers

Step 2: To install Commerce Server on the SQL Server cluster

Step 3: To unpack your Web site and applications

Step 1: To install Commerce Server on the Web servers

  1. Insert the Commerce Server2000 compact disc into your disc drive, and run the Commerce Server 2000 Setup program. Accept the license agreement, type your customer information, and accept the default destination folder.

  2. In the Setup Type dialog box, select Custom, and then click Next.

  3. In the Custom Setup dialog box, select the Administration Tools, Commerce Server Site Packages, and Online Documentation options. Optionally, you can also select Predictor Service, if you plan to use it.

  4. Verify that the Analysis and Data Warehouse and Direct Mailer Service options are not selected (each check box should have an X in it, indicating that you are not selecting it). The following figure shows the Custom Setup dialog box.

    Ee797466.cs_dp_deploy_customsetupaweb(en-US,CS.10).gif

  5. Click Next.

  6. In the Administration Database Configuration dialog box, do the following:

    Use this To do this
    SQL Server Computer Type the computer name for the database server.
    SQL Server Login Name Type the SQL Server login for this computer. To create a new database, you must use a login that is a member of one of the following SQL Server roles: sysadmin or dbcreator. To avoid online analytical processing (OLAP) errors, you should avoid special characters (such as #, @, %, and ').
    SQL Server Login Password Type the SQL Server password for this login name. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

    The Administration database is located on the SQL cluster, and in this step you are pointing this computer to that database. The following figure shows the Administration Database Configuration dialog box.

    Ee797466.cs_dp_deploy_admindbconfig(en-US,CS.10).gif

  7. Click Next.

  8. In the Services Accounts dialog box, do the following:

    Use this To do this
    Username Type the Windows user name of the account under which the Commerce Server services will run on this computer.
    Password Type the password of the Windows account.
    Domain Type the domain of the Windows account.

    The following figure shows the Services Accounts dialog box.

    Ee797466.cs_dp_deploy_servicesaccounts(en-US,CS.10).gif

  9. Click Next.

  10. In the Ready to Install dialog box, click Install.

    Commerce Server Setup installs the administration tools and site packages.

  11. To exit the Setup program, click Finish.

Step 2: To install Commerce Server on the SQL Server cluster

  1. Insert the Commerce Server2000 compact disc into your disc drive, and run the Commerce Server 2000 Setup program. Accept the license agreement, type your customer information, and accept the default destination folder.

  2. In the Setup Type dialog box, select Custom, and then click Next.

  3. In the Custom Setup dialog box, select the Analysis and Data Warehouse option.

  4. Verify that you have cleared all the other options (each check box should have an X in it, indicating that you are not selecting it). The following figure shows the Custom Setup dialog box.

    Ee797466.cs_dp_deploy_customsetupa2(en-US,CS.10).gif

Ee797466.note(en-US,CS.10).gifNote

  • In the initial release of Commerce Server 2000, Commerce Server Direct Mailer does not support installation to a SQL Server virtual cluster. Install Direct Mailer to a physical node of the SQL Server virtual cluster using the name of the physical computer, and use a SQL Server instance that is separate from the virtual instance. Check the Microsoft Commerce Server Web site for an updated solution.

  1. Click Next.

  2. In the Administration Database Configuration dialog box, do the following:

    Use this To do this
    SQL Server Computer Type the cluster name of this server cluster.
    SQL Server Login Name Type the SQL Server login name that will be used to access the administration database. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').
    SQL Server Login Password Type the password for the SQL Server login. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

    The following figure shows the Administration Database Configuration dialog box.

    Ee797466.cs_dp_deploy_admindbconfigdb(en-US,CS.10).gif

  3. Click Next.

  4. In the Services Accounts dialog box, do the following:

    Use this To do this
    Username Type the Windows user name of the account under which the Commerce Server services will run on this computer.
    Password Type the password of the Windows account.
    Domain Type the domain of the Windows account.

  5. Click Next.

  6. In the Ready to Install dialog box, click Install.

    Commerce Server Setup installs the Analysis and Data Warehouse features onto the SQL Server cluster.

  7. To exit the Setup program, click Finish.

Step 3: To unpack your Web site and applications

  1. On the Web server you want, click Start, point to Programs, point to Microsoft Commerce Server 2000, and then click Commerce Server Manager.

  2. Expand Commerce Server Manager, and then click Commerce Sites.

  3. Right-click Commerce Sites, point to New, and then click Unpack Site.

  4. In the Unpack Site From dialog box, navigate to the folder that contains the package file you want to unpack, select the package file, and then click Open.

    Commerce Server Site Packager is started.

  5. In the Unpack dialog box, select Custom unpack, and then click Next.

    The following figure shows the Unpack dialog box.

    Ee797466.cs_dp_deploy_unpack(en-US,CS.10).gif

  6. In the Unpack Method dialog box, select Create a new site, and then click Next.

    The following figure shows the Unpack Method dialog box.

    Ee797466.cs_dp_deploy_unpackmethodnewsite(en-US,CS.10).gif

  7. In the Site Name dialog box, in the Site Name box, type the name for the site or accept the default name, and then click Next.

    The following figure shows the Site Name dialog box.

    Ee797466.cs_dp_deploy_sitename(en-US,CS.10).gif

    Ee797466.note(en-US,CS.10).gifNotes

    • To avoid unpacking errors, you should avoid special characters (such as #, @, %, and ') in your site name. By default, the database names of a site are prefixed with the site name, and special characters might not be recognized in SQL Server.

    • Do not specify a site name of more than 256 single-byte characters or 128 double-byte characters.

    • Do not name your site "Commerce." This is a reserved online analytical processsing (OLAP) database name. Naming your site "Commerce" could cause the overwriting of your OLAP database the next time you unpack a site.

  8. In the Select Resources dialog box, keep all of the resources in the list on the right, except Direct Mail. To remove Commerce Server Direct Mailer, select Direct Mail, and then click Remove. The following figure shows the Select Resources dialog box.

    Ee797466.cs_dp_deploy_selectresourcesnodm(en-US,CS.10).gif

  9. If you are not installing the Predictor resource, select Predictor, and then click Remove.

    Ee797466.note(en-US,CS.10).gifNote

    • You must install the CS Authentication and Profiles resources together. They do not work unless both are installed.

  10. In the Global Resource Pointers dialog box, click Next.

    You use the Global Resource Pointers dialog box to map to existing global resources or to create new ones. You also use this dialog box when you have already unpacked global resources onto your computer and you now want to unpack global resource pointers in a site that will use those global resources.

    The following figure shows a sample screen of the Global Resource Pointers dialog box.

    Ee797466.cs_dp_deploy_globalresourcepointersnodm(en-US,CS.10).gif

    In the Database Connection Strings dialog box, Site Packager lists the databases it will use and the servers on which they exist. The following figure shows how the Database Connection Strings dialog box appears with default settings.

    Ee797466.cs_dp_deploy_dbconnectionstringsa1(en-US,CS.10).gif

    In the Database Connection Strings dialog box, click New Database. Because you are putting the databases on the database server cluster, you need to create the database.

  11. In the New Database dialog box, do the following:

    Use this To do this
    SQL Server computer Type the name of the SQL Server cluster.
    Database name Type the name you want for the Data Warehouse database.
    SQL user name To create a new database, you must use a login that is a member of one of the following SQL Server roles: sysadmin or dbcreator. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').
    SQL password Type the SQL Server login password. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

    The following figure shows the New Database dialog box.

    Ee797466.cs_dp_deploy_newdatabase1(en-US,CS.10).gif

  12. Click Create database to create the new database.

    The other data stores (such as catalogs and transactions) will be stored in another database on the database server cluster. You will also need to create these databases.

    The databases are created on the database server cluster.

  13. When you are returned to the Database Connection Strings dialog box, select Global Data Warehouse, and then click Modify.

  14. In the Data Link Properties dialog box, on the Connection tab, in the Select or enter a server name box, type the name of the database server cluster. In the Select the database on the server box, select the name you assigned to the Data Warehouse database that you created, and then click OK.

Ee797466.note(en-US,CS.10).gif Note

  - Make sure the **Allow saving password** box is selected. If it is not selected, Site Packager will not create the database.

The following figure shows the **Data Link Properties** dialog box.

![Ee797466.cs\_dp\_deploy\_datalinkpropertiesdw(en-US,CS.10).gif](images\Ee797466.cs_dp_deploy_datalinkpropertiesdw(en-US,CS.10).gif "Ee797466.cs_dp_deploy_datalinkpropertiesdw(en-US,CS.10).gif")

  1. When you are returned to the Database Connection Strings dialog box, select all of the other databases, and then click Modify.

  2. In the Data Link Properties dialog box, on the Connection tab, in the Select or enter a server name box, type the name of the database server cluster. In the Select the database on the server box, select the name you assigned to the other database that you created, and then click OK.

Ee797466.note(en-US,CS.10).gif Note

  - Make sure the **Allow saving password** box is selected. If it is not selected, Site Packager will not create the database.

The following figure shows how the **Database Connection Strings** dialog box appears after you modify it.

![Ee797466.cs\_dp\_deploy\_dbconnectionstringsa2(en-US,CS.10).gif](images\Ee797466.cs_dp_deploy_dbconnectionstringsa2(en-US,CS.10).gif "Ee797466.cs_dp_deploy_dbconnectionstringsa2(en-US,CS.10).gif")

  1. Click Next.

  2. In the Select Applications dialog box, verify that the applications you want to unpack are selected, and then click Next. The following figure shows the Select Applications dialog box.

    Ee797466.cs_dp_deploy_selectapplicationsboth(en-US,CS.10).gif

  3. In the Select IIS Web Sites and Virtual Directories dialog box, verify that the IIS Web site and IIS path for each application is correct. To change the IIS Web site for an application, select the application in the list and choose the IIS Web site from the drop-down list.

    To change the name of the virtual directory for an application, select the application in the list. In the IIS virtual directory box, type the name you want.

    Notes

    • To avoid IIS errors, you should not include special characters (such as #, @, %, and ') in your IIS virtual directory names.

    • Site Packager does not support unpacking a site on a remote computer.

    • Site Packager will unpack each application under the home directory of its corresponding IIS Web site. Within the home directory, Site Packager creates a subfolder using the IIS virtual directory name of the application.

    The following figure shows the Select IIS Web Sites and Virtual Directories dialog box.

    Ee797466.cs_dp_deploy_selectiiswebsite(en-US,CS.10).gif

  4. Click Next.

  5. If the Data Warehouse dialog box appears, do the following:

    Use this To do this
    Name Type the name you want to give to the global Data Warehouse resource.
    Server Type the name of the SQL Analysis (OLAP) computer.
    Database Type the name of the Analysis (OLAP) database to use.

  6. Click Next.

  7. If the first Profiling System dialog box appears, do the following:

    Use this To do this
    Profile Schema Definition Specify the profile schema definition to import.
    Site Terms Definition Specify the site terms definition to import.
    Expression Definition Specify the expression definition to import.

  8. Click Next.

  9. If the second Profiling System dialog box appears, do the following:

    Use this To do this
    Profiling System Connection String Specify the files to import into the OLEDB data store. Click Modify to specify a different database.
    Schema definition scripts (*.sql, *.vbs) Specify the schema definition scripts to import.
    Data population scripts (*.sql) Specify the data population scripts to import.

  10. Click Next.

  11. In the Unpacking is complete! dialog box, review the list of SQL Server databases and IIS applications that were created. To review the list of events in the Site Packager log file, click View Log File.

  12. To close Site Packager, click Finish.

Ee797466.note(en-US,CS.10).gif Notes

  • Immediately after you install your site, and any time you make major configuration changes to your Commerce Server deployment, you may want to back up your Administration database with a different name. You can use this backup to roll back any changes that are made later, if necessary.

  • Do not run more than one instance of Site Packager on a computer at a time.

See Also

Using Scripts with Site Packager


All rights reserved.