Share via

Example B: Installing on a Three-Computer Non-clustered Configuration

  • Article

You use Commerce Server Site Packager to deploy site resources from any Commerce Server 2000 computer into the Administration database. If you have three computers, for example, you could install Commerce Server on your Web server, and then deploy your Commerce Server databases onto a different computer. You could configure them as follows:

  • Computer A. Used for the Administration database and administration tools. You will use this computer to manage Commerce Server.

  • Computer B. Used for the Data Warehouse and other databases.

  • Computer C. Used as the Web server, and contains the Active Server Pages (ASP) for your application.

These instructions assume you have installed Microsoft Windows 2000 Server on all three computers, and Microsoft SQL Server 7.0 or SQL Server 2000 on Computers A and B. If you have not yet done so, see Installing Commerce Server for instructions.

Step 1: Install Commerce Server on Computer A

Step 2: Install Commerce Server on Computer B, selecting only the Data Warehouse

Step 3: Install a Commerce Server Web server on Computer C

Step 4: Unpack your site from Computer A

Step 5: Add the Commerce Server Web server (Computer C) to your application

Step 1: Install Commerce Server on Computer A

  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, then click Next.

  3. In the Custom Setup dialog box, under the Runtime Objects folder, verify that the Analysis and Data Warehouse option is not selected (the checkbox should have an X in it, indicating that you are not selecting it). Select the other features you want to install, such as Predictor. The following figure shows the Custom Setup dialog box.

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

  4. 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 (Computer B).
    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 computer. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

  5. Click Next.

  6. 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.

  7. Click Next.

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

    Commerce Server Setup installs the features you specified on Computer A, including the administration tools. You can use this computer to manage your Commerce Server installation.

  9. To exit the Setup program, click Finish.

Step 2: Install Commerce Server on Computer B, selecting only the Data Warehouse

  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, under the Runtime Objects folder, select the Analysis and Data Warehouse option, and then clear the other options, except for Direct Mailer, if you plan to use it. Click Next. The following figure shows the Custom Setup dialog box.

    Ee785246.cs_dp_deploy_customsetupdb(en-US,CS.10).gif

  4. 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 (Computer B).
    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 computer. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

  5. If you are installing Direct Mailer, in the Direct Mailer Database Configuration dialog box, do the following:

    Use this To do this
    SQL Server Computer Accept the default (Computer B).
    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 OLAP errors, you should avoid special characters (such as #, @, %, and ').
    SQL Server Login Password Type the SQL server login password for this server. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

  6. In the Services Accounts dialog box, type the Windows user name and password of the account under which the Commerce Server services will run on this computer, and then click Next.

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

    Commerce Server Setup installs the Analysis and Data Warehouse features onto Computer B.

  8. To exit the Setup program, click Finish.

Step 3: Install a Commerce Server Web server on Computer C

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

  2. Click Next.

  3. 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 (Computer B).
    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 computer. To avoid OLAP errors, you should avoid special characters (such as #, @, %, and ').

  4. Click Next.

  5. In the Services Accounts dialog box, type the Windows user name and password of the user granted access to Commerce Server services on this computer. Then click Next.

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

    Commerce Server Setup installs the Runtime Objects and Commerce Server Site Packages onto Computer C.

  7. To exit the Setup program, click Finish.

Step 4: Unpack your site from Computer A

  1. On Computer A, 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.

    Ee785246.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.

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

  7. In the Site Name box, the default name for the site appears. Change the name as needed, and then click Next.

    Ee785246.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 the 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 OLAP database name. Naming your site "Commerce" could cause the deletion of your OLAP database the next time you unpack a site.

  8. In the Select Resources dialog box, select all of the resources. If you are not installing Commerce Server Direct Mailer, select Direct Mailer, and then click Remove. If you are not installing the Predictor resource, select Predictor, and then click Remove. The following figure shows the Select Resources dialog box.

    Ee785246.cs_dp_deploy_selectresourcesall(en-US,CS.10).gif

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

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

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

    You use this screen 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.

    In the Database Connection Strings dialog box, Site Packager lists the databases it will use and the servers on which they exist.

    Because you are putting the Data Warehouse on a different computer, you need to create the database. To create a database called Blank_dw for the Data Warehouse on Computer B, click New Database.

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

    Use this To do this
    SQL Server computer Type the name of the SQL Server computer (Computer B).
    Database name Type Blank_dw or 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.

    Ee785246.cs_dp_deploy_newdatabaseb1(en-US,CS.10).gif

  11. Click Create Database. The Blank_dw database is created on Computer B.

  12. When you are returned to the Database Connection Strings dialog box, click New Database.

    You are also putting the other Commerce Server databases on Computer B.

  13. To create a separate database called Blank_commerce to group these databases, repeat Step 11 and type Blank_commerce in the Database name box instead. The following figure shows the New Database dialog box with the Blank_commerce database.

    Ee785246.cs_dp_deploy_newdatabaseb2(en-US,CS.10).gif

  14. Click Create Database. The Blank_commerce database is created on Computer B.

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

  16. In the Data Link Properties dialog box, in the Select or enter a server name box, type the name of Computer B. In the Select the database on the server box , select the name (Blank_dw) you assigned to the Data Warehouse that you created on Computer B, and then click OK.

Ee785246.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.

![Ee785246.cs\_dp\_deploy\_datalinkpropertiesb1(en-US,CS.10).gif](images\Ee785246.cs_dp_deploy_datalinkpropertiesb1(en-US,CS.10).gif "Ee785246.cs_dp_deploy_datalinkpropertiesb1(en-US,CS.10).gif")

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

  2. In the Data Link Properties dialog box, in the Select or enter a server name box, type the name of Computer B. In the Select the database on the server box, select the name (blank_commerce) you assigned to the database, and then click OK.

Ee785246.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.

![Ee785246.cs\_dp\_deploy\_dbconnstringsb2(en-US,CS.10).gif](images\Ee785246.cs_dp_deploy_dbconnstringsb2(en-US,CS.10).gif "Ee785246.cs_dp_deploy_dbconnstringsb2(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.

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

  3. In the Select IIS Web Sites and Virtual Directories dialog box, verify that the Internet Information Services (IIS) 5.0 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.

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

  4. In the Data Warehouse dialog box, 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.

  5. Click Next.

  6. 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.

  7. Click Next.

  8. 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.

  9. Click Next.

  10. 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.

  11. To close Site Packager, click Finish.

Step 5: Add the Commerce Server Web Server (Computer C) to your application

  1. On Computer C, the Web server that you want to add to the application, expand Commerce Server Manager, expand Commerce Sites, and then click the site you want to administer.

  2. Expand Applications, and then click the name of the application to which you want to add the Web server. Right-click that name, point to New, and then click Add Web server.

    The Open dialog box appears containing a list of the existing package files.

  3. In the Open dialog box, select the package file that contains the Web server files you want to add to the Web server, and then click Open.

    Commerce Server Site Packager is started.

  4. The Select IIS Web Sites and Virtual Directories dialog box displays the name of the IIS Web site where the application will be installed and the IIS virtual directory for each Commerce application. This information is read-only; the IIS Web site and virtual directory must be the same across all Web servers in the application. Click Next.

    Site Packager adds your files to the Web server, and then adds the Commerce Web server object to the selected application. When you open Commerce Server Manager, the Commerce Web server object appears under the application.

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

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

  5. In the Unpacking is complete! dialog box, review the log file, and then click Finish.

After you add a Web server to an application, the Commerce Web server object appears under the application node in Commerce Server Manager. The Commerce Web server object contains properties required by the Data Warehouse resource in order to import log files: server name, Internet Protocol (IP) address, log file path, and log file period. These properties are automatically populated from IIS when you add a Commerce Web server object to an application. For instructions about configuring these Web server properties, see Configuring a Web Server.

Ee785246.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.

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

See Also

Configuring a Web Server


All rights reserved.