Deploying Multiple Sites That Share a Single Data Warehouse

  • Article

You can deploy multiple Microsoft Commerce Server sites that share a single Data Warehouse. You can unpack the sites to a local or remote computer and add them to a Data Warehouse that is installed on a local or remote computer.

Ee799424.important(en-US,CS.20).gifImportant

  • Commerce Server reports will show data for all sites in the Data Warehouse. Use grouped reports to run reports for a single site. For information about grouped reports, see Creating Grouped Reports.

For information about using a single Data Warehouse with multiple sites, see Multiple Sites and One Data Warehouse.

Use the following procedures to unpack two sites that share a single Data Warehouse resource and a single Profiles resource.

To unpack the first site

To add an additional site to the Data Warehouse

To unpack the first site

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2002, and then click Commerce Site Packager.

  2. In the Welcome to the Commerce Server Site Packager dialog box, select Unpack from a package file (.pup), and then click Next.

  3. In the Unpack dialog box, type the path and file name of the file you want to unpack, or click Browse.

  4. If you clicked Browse , in the Open dialog box, navigate to the folder that contains the file you want to unpack, select the file, and then click Open.

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

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

  7. In the Site name dialog box, type the name for the new site, and then click Next.

    Ee799424.note(en-US,CS.20).gifNotes

    The site name has the following site name restrictions:

    • Do not use special characters (such as #, @, %, and ') that might not be recognized by SQL Server databases. For more information, see SQL Books Online.
    • Do not name your site "Commerce." This is a reserved OLAP database name. Naming your site "Commerce" could cause overwriting of your OLAP database the next time you unpack a site.
    • The site name can contain a maximum of 127 characters.

  8. In the Select Resources dialog box, click Add All, and then click Next.

    Ee799424.note(en-US,CS.20).gifNote

    • In the Select Resources dialog box, 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, in the Global resource pointers list, select Data Warehouse.

  10. In the Existing global resources drop-down list, select (Add new global resource).

  11. In the Global resourcepointers list, select Profiles, in the Existing global resources drop-down list, select (Add new global resource), and then click Next.

  12. In the Database Connection Strings dialog box, Site Packager lists the databases it will create and the servers on which it will create them. To change the databases and servers, click Modify. In the Data Link Properties dialog box, select or type the new database(s) and server name(s), and then click OK.

    Ee799424.note(en-US,CS.20).gifNote

    • If you want to copy a database connection string, select the row that contains the connection string you want to copy, and then click Modify. In the Data Link Properties dialog box, select or type the server and database name(s) you want to copy, and then click OK. In the Database Connection Strings dialog box, reselect the row that contains the connection string you want to copy, and then click Copy. Select the row(s) to which you want to copy the connection string, and then click Paste.

  13. Click Next.

  14. The Commerce Server Site Packager dialog box appears if Site Packager needs to create a database(s). The information you provide in this dialog box is used to connect to the Master database on your SQL Server installation.

  15. In the Commerce Server Site Packager dialog box, do the following:

    Use this To do this
    Use Windows Integrated security Select this option if you want to use integrated Windows security for the databases.

    Windows Integrated Security is the recommended configuration for Commerce Server. It is also known as Windows Authentication. For more information on Windows Authentication, see Using Windows Authentication.

    Ee799424.note(en-US,CS.20).gifNote

    • When you use Windows Integrated Security, user names and passwords are not stored in the SQL Server connection string, and are not affected by SQL password resets. For information about Commerce Server security, see Securing Your Site.
    Use a specific user name and password Select this option if you want to use SQL Server authentication when connecting to the databases.

    Ee799424.note(en-US,CS.20).gifNote

    • You should always use a strong password when creating passwords. For more information about strong passwords, see Using Strong Passwords.
    SQL Server Login Name Type the SQL Server login name for the databases.
    SQL Server Login Password Type the SQL Server login password.

  16. Click OK.

  17. In the Select Applications dialog box, verify that the applications you want to unpack are selected, and then click Next.

  18. In the Select IIS Computers, Web Sites and Paths dialog box, do the following:

    Use this To do this
    IIS computer name Type the computer name of the IIS Web server to which you want to unpack the application files.

    Ee799424.note(en-US,CS.20).gifNote

    • If you specify to unpack the application files on a remote server, the server onto which you unpack the applications must have Commerce Server 2002 installed, or you will not be able to run Business Desk on it.
    Refresh
    • Click to update the list of Web sites on the remote computer.
    IIS Web site Select the name of the IIS Web site for the selected applications.

    Ee799424.note(en-US,CS.20).gifNote

    • If you unpack a site onto the IIS Administrative Web site, the site and Business Desk will not function due to IIS administration security limitations.
    IIS path Type the name of the IIS path for the selected applications.

    Ee799424.note(en-US,CS.20).gifNotes

    • To avoid IIS errors, you should not include special characters (such as #, @, %, and ') in your virtual directory names.
    • 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.
    • If you want to unpack the application to the root of the Web site, you can use the "/" character or leave the IIS path field blank.

  19. Click Next.

  20. If you added the Data Warehouse resource to the site, the Data Warehouse dialog box appears. To specify the settings for the Data Warehouse resource, do the following:

    Use this To do this
    Name Type a name for 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.

  21. Click OK.

  22. If you added the Profiles resource to the site, the first of two Profiling System dialog boxes appears. If you are unpacking a Solution Site, click Next to accept the default entries.

    To specify your own profile settings, do the following:

    Use this To do this
    Profile Schema Definition When you pack a site, Site Packager extracts the profile schema from your Profiles database, and stores it in an XML file. Specify that XML file in this box so it is unpacked.

    When you unpack a Solution Site, accept the default XML file, ProfileDefinition. This file contains the following profile definitions: Address, BlanketPOs, Organization, Targeting Context, and User Object.
    Site Terms Definition When you pack a site, Site Packager extracts the site terms definition from your database and stores it in an XML file. Specify that XML file in this box so it is unpacked.

    When you unpack a Solution Site, accept the default XML file, SiteTerms. This file contains the predefined site terms for your use.
    Expression Definition When you pack a site, Site Packager extracts the definitions for expressions that you defined using Business Desk, and stores them in an XML file. Specify that XML file in this box so it is unpacked.

    When you unpack a Solution Site, a default XML file, ExpressionDefinition, is provided. This file does not contain any predefined expressions for the Solution Sites.

  23. Click Next.

  24. If you added the Profiles resource to the site, the second of two Profiling System dialog boxes appears. If you are unpacking a Solution Site, click Next to accept the default entries.

    To specify your own profile settings, do the following:

    Use this To do this
    Profiling System Connection String Accept the default connection string to the Profiles database, or click Modify to configure a new connection string.
    Schema definition scripts (*.sql, *.vbs) Specify the schema definition script that will create the Profiles tables in the runtime data stores (the SQL tables that store the data for the user, address, organization, and so on).

    When you unpack a Solution Site, SCHEMAUPM_SQLSource.SQLSource creates the tables for the default profile definitions: Address, BlanketPOs, Organization, Targeting Context, and User Object.

    For a sample script, see ProfileSQL.sql, which is located in \Program Files\Microsoft Commerce Server 2002.

    If you modify the UserObject table or other profile schema definitions, you must use SQL Server Enterprise Manager to generate a script to use here. For more information, see Packaging Extended Profile Schema.
    Data population scripts (*.sql) If you have extracted the profile data from a Profiles database, you can specify data population scripts so when you unpack, that data is imported into your new Profiles database.

    For a sample script that contains data for two users, see PopulateProfileSql.sql, which is located in \Program Files\Microsoft Commerce Server 2002.

  25. Click OK.

  26. If you are using Windows Integrated security, in the Commerce Server Site Packager dialog box, review the list of resources that are being unpacked and that require access permissions on the appropriate Windows accounts, and then click OK.

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

  28. To close Site Packager, click Finish.

To add an additional site to the Data Warehouse

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2002, and then click Commerce Site Packager.

  2. In the Welcome to the Commerce Server Site Packager dialog box, select Unpack from a package file (.pup), and then click Next.

  3. In the Unpack dialog box, type the path and file name of the file you want to unpack, or click Browse.

  4. If you clicked Browse, in the Open dialog box, navigate to the folder that contains the file you want to unpack, select the file, and then click Open.

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

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

  7. In the Site name dialog box, type the name for the new site, and then click Next.

    Ee799424.note(en-US,CS.20).gifNote

    The site name has the following restrictions:

    • Do not use special characters (such as #, @, %, and ') that might not be recognized by SQL Server databases. For more information, see SQL Books Online.
    • Do not name your site "Commerce." This is a reserved OLAP database name. Naming your site "Commerce" could cause overwriting of your OLAP database the next time you unpack a site.
    • The site name can contain a maximum of 127 characters.

  8. In the Select Resources dialog box, click Add All, and then click Next.

    Ee799424.note(en-US,CS.20).gifNote

    • In the Select Resources dialog box, 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, in the Global resource pointers list, select Data Warehouse.

  10. In the Existing global resources drop-down list, select an existing Data Warehouse resource for your site.

  11. In the Global Resource Pointers dialog box, in the Global resource pointers list, select Profiles.

  12. In the Existing global resources drop-down list, select an existing Profiles resource for your site, and then click Next.

  13. In the Database Connection Strings dialog box, the Data Warehouse and Profiles connection strings no longer appear. This is because these resources existed before unpacking this site, and all of the connection strings are already defined.

To add additional sites to the same Data Warehouse, see To add an additional site to the Data Warehouse.

Copyright © 2005 Microsoft Corporation.
All rights reserved.