Best Practices for Using Site Packager
This topic provides important information about packaging your Commerce Server site.
Do not run Site Packager on a production site.
If Site Packager is run on a production site, the site might not respond correctly to clients.
Do not run more than one instance of Site Packager on a computer at a time.
Do not use Site Packager to unpack sites remotely. You should only run Site Packager on the local computer.
To unpack a site onto an Internet Information Services (IIS) Web site other than the default, use the Custom mode of Site Packager.
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 must 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, the CSharp, on separate Web servers, you must add one of the Web servers to the other application.
For example, if the CSharp site is installed on Computer A and SiteB is on Computer B, you can run Site Packager on Computer B to add it as a Web server for the CSharp site. Then you can package SiteB from Computer B. (Conversely, you could add Computer A to SiteB, and package the site there.) For more information, see How to Add a Web Server to an Application.