Unpacking a Site Using Default Properties

  • Article

To shorten the unpacking process and to install all of your database files on one local or remote SQL Server computer, use the following procedures.

To unpack a site quickly, accepting most default settings

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

    The Commerce Server Site Packager screen appears.

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

    The Unpack screen appears.

  3. In the Unpack screen, click Browse.

    The Open dialog box appears.

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

    The Unpack screen appears. The *.pup package that you selected appears in the File to unpack dialog box.

  5. In the Unpack screen, select Quick unpack, and then click Next.

    The Quick Unpack screen appears.

  6. In the Quick Unpack screen, do the following:

    Use this To do this
    Site name Type the name for the site, if you want to change it. For a list of name restrictions, see Site Packager Name and Size Restrictions.
    IIS Web site Select the name of the IIS Web site where the application(s) will be installed, from the drop-down list.

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

    • Do not unpack a site onto the Administration Web Site. If you unpack a site onto the Administration Web Site, the site and Business Desk will not function due to IIS administration security limitations.
    SQL Server Computer Type the name of the computer running SQL Server that will contain the databases for the site, or accept the default setting.
    Use Windows Integrated security Select this option if you want to use integrated Windows authentication.

    This is the recommended configuration.
    Use a specific user name and password Select this option if you want to use SQL Server authentication when connecting to the databases.
    SQL Server Login Name Type the SQL Server login name for the databases.

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

    • For security purposes, do not use the sa login for access to the databases. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager.
    SQL Server Login Password Type the SQL Server login password for the databases.

  7. Click Next.

    The Unpacking... screen appears displaying the tasks that are being performed. When these tasks are finished, the Data Warehouse screen appears if the Data Warehouse resource was installed during the installation process.

  8. To specify the settings for the Data Warehouse resource, do the following:

    Use this To do this
    Name Type a name for your global Data Warehouse resource, or accept the default setting.
    Server Type the name of the SQL Analysis online analytical processing (OLAP) computer, or accept the default setting.
    Database Type the name of the Analysis (OLAP) database to use, or accept the default setting.

  9. Click OK.

    The Unpacking... screen appears displaying the tasks that are being performed. When these tasks are finished, the first Profiling System screen appears.

    If the Profiles resource was installed during the installation process, the first of two Profiling System dialog boxes appears.

  10. If you are unpacking a Solution Site, and want to accept the default settings, skip to step 12 below.

  11. To specify your own profile settings, do the following:

    Use this To do this
    Profile Schema Definition Specify the XML file that was stored when you packed your site.

    When you pack your site, Site Packager extracts the profile schema from your Profiles database and stores it in an XML file.

    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 Specify the XML file that was stored when you packed your site.

    When you pack your site, Site Packager extracts the site terms definition from your Profiles database, and stores it in an XML file.

    When you unpack a Solution Site, accept the default XML file, SiteTerms. This file contains the predefined site terms for your use.
    Expression Definition Specify the XML file that was stored when you packed your site.

    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.

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

  12. Click Next.

    If the Profiles resource was installed during the installation process, the second of two Profiling System dialog boxes appears.

  13. If you are unpacking a Solution Site, and want to accept the default settings, skip to step 15 below.

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

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

    • If you change the XML file, Commerce Server does not preserve the connection string information. The new XML file can contain a different type and number of aggregated data stores than the data stores that are in the default XML file. Therefore, you must re-enter the 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 forth.).

    When you unpack a Solution Site, SCHEMAUPM_SQLSource.SQLSource creates the tables for the default profile definitions: Address, BlanketPOs, Organization, Targeting Context, 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 that import data into your new Profiles database when you unpack,.

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

    For information about using scripts with site packager, see Using Scripts with Site Packager.

  15. Click OK.

  16. 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 require access permissions on the appropriate Windows accounts, and then click OK.

    If you did not select Windows Integrated security, proceed to the next step.

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

  18. To close Site Packager, click Finish.

Copyright © 2005 Microsoft Corporation.
All rights reserved.