Unpacking a Site

  • Article

You use Commerce Server Site Packager to unpack a site or a subset of a site onto one or more computers. When running Site Packager, you must have appropriate permissions to copy files to the destination folders.

To unpack a site quickly, accepting most default settings

To unpack a site, specifying all settings yourself

Ee811762.note(en-US,CS.10).gif Notes

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

  • To unpack a site onto an Internet Information Services (IIS) 5.0 Web site other than the default, use the Custom mode of Site Packager.

  • If you unpack the Direct Mailer resource after you unpack a Business Desk application and install the Business Desk client, you must restart Internet Information Services (IIS) 5.0 on the Web server hosting the Business Desk application in order for the addition of Direct Mailer to be detected. Business Desk clients must re-connect to the application. For instructions about restarting IIS, see Restarting IIS.

  • Business Desk modules are not automatically removed from the Business Desk application if you choose not to unpack a required resource. For example, if you do not unpack Product Catalog, the Catalogs modules will still appear in Business Desk, but they will not work.

Use the following procedure if you are making this computer a Web server, and you are going to put all of your database files on one SQL Server.

To unpack a site quickly, accepting most default settings

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

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

  3. In the Unpack dialog box, click the Browse button next to the File to unpack box.

  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.

  5. When you are returned to 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 include special characters (such as #, @, %, and ') in the name. Do not name your site "Commerce."
    IIS Web site Select the name of the IIS Web site where the applications(s) will be installed.
    SQL Server computer Type the name of the SQL Server that will contain the databases for the site.
    SQL user name Type the SQL login name for the databases.
    SQL password Type the SQL login password.

  7. If the Data Warehouse dialog box appears, 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 online analytical processing (OLAP) computer.
    Database Type the name of the Analysis (OLAP) database to use.

  8. Click Next.

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

  10. Click Next.

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

  12. Click Next.

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

  14. To close Site Packager, click Finish.

Use the following procedure if you are adding this Web server to an existing application, or you want to specify that more than one database server will be used with the site.

To unpack a site, specifying all settings yourself

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

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

  3. In the Unpack dialog box, click the Browse button next to the File to unpack box.

  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.

  5. When you are returned to the Unpack dialog box, select Custom unpack, and then click Next.

  6. In the Unpack Method dialog box, select the appropriate option, and then click Next.

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

Ee811762.note(en-US,CS.10).gif Notes

  - 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 overwriting of your OLAP database the next time you unpack a site.

  1. In the Select Applications or Select Resources dialog box, select the items you want to install, and then click Next.

    Ee811762.note(en-US,CS.10).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.

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

    You use this dialog box to map to existing global resources or to create new ones.

  3. In the Database Connection Strings dialog box, Site Packager lists the databases it will create and the servers on which it will create them. Verify that the databases are correct, and then click Next.

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

  5. In the Select IIS Web Sites and Virtual Directories dialog box, verify that the IIS Web sites and application paths are correct, and then click Next.

    Notes

    • To avoid IIS errors, you should not include special characters (such as #, @, %, and ') in your 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.

  6. If the Data Warehouse dialog box appears, 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.

  7. Click Next.

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

  9. Click Next.

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

  11. Click Next.

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

  13. To close Site Packager, click Finish.

Ee811762.note(en-US,CS.10).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.

  • If you create and use an unpack.vbs script file when you unpack a non-Commerce Server Business Desk application, make sure you delete or secure the file immediately after unpacking. The file exists in the root directory, and can be accessed by anonymous users. Unauthorized use of this script could lead to denial of service or the breaking of site settings.

See Also

About Site Packager

Packaging a Site

Example A: Installing on a Four-Computer Clustered Configuration

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

Running Site Packager from the Command Line

Troubleshooting Site Packager


All rights reserved.