Unpacking a Site

Use the following procedure on each server to unpack your site.

To unpack your site on a server

1. Click Start, point to Programs, point to Microsoft Commerce Server 2002, 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 Quick Unpack, and then click Next.

6. In the Quick Unpack dialog box, do the following:

   Use this	To do this
   Site name	Type the name for the site, if you want to change it. 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 the overwriting of your OLAP database the next time you unpack a site. The site name can contain a maximum of 127 characters.
   IIS Web site	Select the name of the IIS Web site where the application(s) will be installed. Note 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.
   SQL Server Computer	Type the name of the computer running SQL Server that will contain the databases for the site.
   Use Windows Integrated security	Select this option if you want to use integrated Windows authentication. 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.
   SQL Server Login Name	Type the SQL Server login name for the databases. Note 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.

8. If the Data Warehouse resource was installed during the installation process, 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 your global Data Warehouse resource.
   Server	Type the name of the SQL Analysis online analytical processing (OLAP) computer.
   Database	Type the name of the analysis database to use.

9. Click OK.

10. If the Profiles resource was installed during the installation process, the first of two Profiling System dialog boxes appears. To specify the settings for the Profiles resource, 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.

11. Click Next.

12. If the Profiles resource was installed during the installation process, the second of two Profiling System dialog boxes appears. To specify the settings for the Profiles resource, 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. Site Packager uses a default schema definition script. 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)	Specify the data population scripts to import.

13. Click OK.

    Note

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

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

15. To close Site Packager, click Finish.

The process of unpacking your site is complete. For instructions on accessing Commerce Server Business Desk for this site, see Installing the Business Desk Client.

Copyright © 2005 Microsoft Corporation.
All rights reserved.