Packages

A package is a specially formatted Commerce Server file. Each package is identified with a .pup file name extension. A package always contains a single site, which includes the resources, their data, and applications of a Commerce Server Web site.

In addition to site resources, applications, and the Internet Information Services (IIS) 5.0 or later settings that are needed to recreate the Web server configurations, Commerce Server Site Packager also includes the property values from the Administration database. For example, when you package the App Default Config resource, all of the current property values are also packaged. When you unpack the App Default Config resource, the property values are unpacked into the Administration database.

The package includes global resource pointers, but not the global resources themselves. The package recognizes the connection strings that exist in the application, but does not contain the actual data in the connection string.

Note

• Connection strings that contain a computer name are not packaged.

During the application packaging process, Site Packager searches the IIS metabase on your local computer and finds the physical directory that is the root for that application. It then starts at that root directory and packages all the subdirectories below into a new file with a .pup file name extension. Site Packager preserves certain settings in IIS, such as authorizations and access permissions. For a list of which IIS properties are packaged, see IIS Properties That Are Packaged.

Site Packager does not package properties that are computer specific. For example, Web server properties and some application properties that are set in Commerce Server Manager are not packaged. For a list of data that is packaged for each resource, see Where Resources and Data Are Unpacked.

See Also

IIS Properties That Are Packaged

Unpacking a Site

Packaging a Site

Copyright © 2005 Microsoft Corporation.
All rights reserved.