Managing Site Packages
For the latest version of Commerce Server 2007 Help, see the Microsoft Web site.
Microsoft Commerce Server Site Packager is a tool that has two primary uses. You use it to package your Commerce Server site into a single site package file, and you use it to unpack the site onto other servers. When you package the file, Commerce Server includes Internet Information Services (IIS) settings (metabase), the files and resources from the Administration database, and Microsoft SQL Server databases. Site packages make it easy for you to deploy sites and applications between different servers. The site package, known as a PuP package, is a specially formatted Commerce Server file. Each package is identified with a .pup file name extension.
Note
PuP packages from Commerce Server 2002 may have applications that contain unpack.vbs scripts that perform additional processing. These scripts may use Commerce Server classes and methods that are not supported in Commerce Server 2007, for example, the Commerce.ACL and Commerce.DataFunctions objects. Therefore, when unpacking a site that was created from a previous version of Commerce Server, you may see errors in the .pup log that result from the use of these objects being referenced from the unpack.vbs file.
For information about how to use the SiteConfig Object and GlobalConfig Object to perform similar functionality to Site Packager, see Configuration Objects.
Note
The SiteConfig and GlobalConfig objects are deprecated in Commerce Server 2007. For more information about their replacement objects, see Removed or Deprecated Features.