Packaging a Site

  • Article

When you package a site, you save your applications and settings in a single package file. For a list of the IIS properties that are included in the package, see IIS Properties That Are Packaged.

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

To package a site

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2002, and then click Commerce Site Packager.
  2. In the Welcome to Commerce Server Site Packager dialog box, select Package an existing site, and then click Next.
  3. In the Package Site dialog box, do the following:
    Use this To do this
    Site to package Select the site you want to package from the list of available sites.
    Package file to create Type the name of the package file you want to create, or click Browse.

    If you clicked Browse, in the Save As dialog box, navigate to the folder that contains the package file you want to create, select the file, and then click Save.
  4. When you are returned to the Package Site dialog box, click Next.
  5. If the Profiles resource was added to the site you are packaging, the Profiling System dialog box appears. In the Profiling System dialog box, do the following:
    Use this To do this
    Schema definition scripts To pack the profile definitions, use SQL Server Enterprise Manager to export the definitions (schema) from the SQL database to a .sql file, and then specify the name of that file here.

    When you unpack your site, you will specify this file so the definitions will be unpacked into the Profiles tables in the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.).

    For more information, see Packaging Extended Profile Schema.
    Data population scripts To pack the profile data stored in the Profiles database, use Enterprise Manager to export the profile data from the SQL database to a .sql file, and then specify the name of that file here.

    When you unpack your site, you will specify that .sql file to populate your Profiles tables in the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.).

    To view a sample data population script, 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.
  6. Click OK.
  7. In the Packaging is complete! dialog box, to review the list of events in the Site Packager log file, click View Log File.
  8. To close Site Packager, click Finish.

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

  • If you package a Commerce Server application whose IIS virtual directory contains child IIS applications, Site Packager will package the folders and files of the child applications. If you do not want the folders and files of the child applications included in the package, you will have to delete them after you unpack the parent Commerce Server application.
  • Site Packager does not package files in child virtual directories of the IIS application. If you need to package files in child virtual directories, move the folders and files to child physical folders of the root folder of the IIS application before packaging your site.
  • Before you can package a site that has applications (for example, Retail and RetailBusinessDesk) on separate Web servers, you must add one of the Web servers to the other application. For example, if Retail is installed on Computer A and RetailBizDesk is on Computer B, you can run Site Packager on Computer B to add it as a Web server for Retail. Then you can package the site from Computer B. (Conversely, you could add Computer A to RetailBizDesk, and package the site there.) For more information, see Adding a Web Server to an Application.

See Also

IIS Properties That Are Packaged

Unpacking a Site

Running Site Packager from the Command Line

Packaging Other Data

Copyright © 2005 Microsoft Corporation.
All rights reserved.