Unpacking a Site Using Custom Properties

  • Article

To add resources or an application to an existing site, or to add a Web server to an existing application use the following procedures. You can also specify that more than one database server will be used with the site.

To unpack a site, using Custom unpack

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

  2. In the Welcome totheCommerce 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 the Browse button.

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

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

  5. In the Unpack Method dialog box, select one of the unpack options, and then click Next.

The unpack options are explained in the following procedures.

To create a new site

To add resources in the package to an existing site

To add an application in the package to an existing site

To add a Web server to an existing application in an existing site

To create a new site

You use this option to unpack the contents of the selected site package to a new site, use the following procedures.

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

  2. In the Select Resources dialog box, select the resources you want to add, click Add, and then click Next.

    Ee797221.note(en-US,CS.20).gif Note

    • In the Select Resources dialog box, you must install the CS Authentication and Profiles resources together. They do not work unless both are installed.

  3. In the Global Resource Pointers dialog box, select the existing global resource pointer to which you want to map an existing or new global resource. In the Existing global resources box, select the global resource you want to map to the selected global resource pointer, and then click Next.

    In the Database Connection Strings dialog box, Site Packager lists the databases it will create and the servers on which it will create them.

  4. To change the databases and servers, select a resource from the Resource column, and then click Modify.

  5. In the Data Link Properties dialog box, select or type the new database(s) and server name(s), click OK, and then click Next.

    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.

    Ee797221.note(en-US,CS.20).gif Note

    • The Data Warehouse resource should always be unpacked to a separate database.

    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.

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

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

    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. This configuration is not recommended.
    SQL Server login name Type the SQL Server login name for the databases. This configuration is not recommended.
    SQL Server login password Type the SQL Server login password. This configuration is not recommended.

  7. Click OK.

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

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

    To update the list of Web sites on the remote computer, click Refresh.
    IIS Web site Select the name of the IIS Web site for the selected applications.

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

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

    To unpack an application to the root of the Web site, use the ‘/' character or leave this field blank.

    Ee797221.note(en-US,CS.20).gif Notes

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

  10. Click Next.

    If you added the Data Warehouse resource to the site, the Data Warehouse dialog box appears.

  11. 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 server running SQL Analysis (OLAP).

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

    • The Data Warehouse resource should always be installed to a server running SQL Server as the OLAP database.
    Database Type the name of the Analysis (OLAP) database to use.

  12. Click OK.

    If you added the Profiles resource to the site, the first of two Profiling System dialog boxes appears.

  13. 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 here 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 here 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 here 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.

  14. Click Next.

    If you added the Profiles resource to the site, the second of two Profiling System dialog boxes appears.

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

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

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

  16. Click OK.

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

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

  19. To close Site Packager, click Finish.

To add resources in the package to an existing site

  1. In the Unpack Method dialog box, select Add resources in the package to an existing site, and then click Next.

  2. In the Select Site dialog box, select the existing site to which you want to add the resource(s), and then click Next.

  3. In the Select Resources dialog box, select the resources you want to add, click Add, and then click Next.

    Ee797221.note(en-US,CS.20).gif Note

    • In the Select Resources dialog box, you must install the CS Authentication and Profiles resources together. They do not work unless both are installed.

    The Global Resource Pointers screen appears. You use this screen to map to existing global resources or 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.

  4. In the Global Resource Pointers dialog box, select the existing global resource pointer to which you want to map an existing or new global resource. In the Existing global resources box, select the global resource you want to map to the selected global resource pointer, and then click Next.

    The Database Connection Strings screen appears. In this screen, all connection strings, server names, and databases are listed for the resources that will be installed for your site.

  5. 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), click OK, and then click Next.

    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.

  6. 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 authentication for the databases.

    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.
    SQL Server Login Password Type the SQL Server login password.

  7. Click OK.

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

  9. Click OK.

  10. 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 the settings for the Profiles resource, 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 here 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 here 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 here so it is unpacked.

    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.

  11. Click Next.

  12. 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 the connection string.

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

  13. Click OK.

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

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

  16. To close Site Packager, click Finish.

To add an application in the package to an existing site

  1. In the Unpack Method dialog box select Add an application to the package to an existing site, and then click Next.

  2. In the Select Site dialog box, select the existing site to which you want to add an application, and then click Next.

  3. In the Select Applications dialog box, select the applications you want to unpack, and then click Next.

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

    To update the list of Web sites on the remote computer, click Refresh.
    IIS Web site Select the name of the IIS Web site for the selected applications.

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

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

    • To unpack an application to the root of the Web site, use the ‘/' character or leave this field blank.

    Ee797221.note(en-US,CS.20).gif Notes

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

  5. Click Next.

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

  7. To close Site Packager, click Finish.

To add a Web server to an existing application in an existing site

  1. In the Unpack Method Dialog box select Add a Web server to an existing application in an existing site, and then click Next.

  2. In the Select Site dialog box, select the existing site to which you want to add a Web server, and then click Next.

  3. In the Select Applications dialog box, select the applications you want to unpack, and then click Next.

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

    To update the list of Web sites on the remote computer, click Refresh.
    IIS Web site Select the name of the IIS Web site for the selected applications.

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

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

    • To unpack an application to the root of the Web site, use the ‘/' character or leave this field blank.

    Ee797221.note(en-US,CS.20).gif Notes

    • Site Packager unpacks 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.

  5. Click Next.

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

  7. To close Site Packager, click Finish.

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

  • 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 you install Commerce Server databases (other than the Data Warehouse) on a remote computer, it is possible there will be a delay before these databases appear on that computer.
  • After you create an application, an unpack.vbs script may exist in the root folder of the application (if you unpack the Blank site, it will not exist). Make sure you delete or secure the file immediately after unpacking. Anonymous users can access the file. Unauthorized use of this script file could lead to denial of service or the breaking of site settings. For information about securing your site, see Securing Your Site.
  • This file is used when a site is unpackaged using Commerce Server Site Packager.

See Also

Securing Your Site

Packaging a Site

Running Site Packager from the Command Line

Troubleshooting Site Packager

Copyright © 2005 Microsoft Corporation.
All rights reserved.