Commerce Server Deployment Concepts and Terms

Commerce Server 2009

This topic provides conceptual information about the objects and entities that Commerce Server 2009 installs. The topic includes information about the following:

A Commerce Server 2009 deployment includes one or more physical installations of Commerce Server 2009 that share a single Commerce Server MSCS_Admin administration database. Commerce Server creates the MSCS_Admin database when you run the Configuration Wizard.

An enterprise deployment consists of four Commerce Server 2009 deployments, one each for the following environments:

  • Development environment

  • Integration build and test environment

  • Staging environment

  • Production environment

A Commerce Server 2009 site includes a collection of site resources and .NET-connected applications that use the site resources through the Commerce Server 2009 object model. With a Commerce Server 2009 site, you can administer the applications in the site as a group. Be aware that a Commerce Server 2009 site does not map to the concept of a Web site in Microsoft Internet Information Services (IIS).

Sites can be packaged and unpacked in a PuP file by using Site Packager. You package your Commerce Server 2009 site (including the IIS metabase settings), site files from the file system, resources from the Administration database, and SQL Server databases into a single file. You also use Site Packager to unpack the Commerce Server 2009 site (or sections of it) onto other computers.

A Commerce Server 2009 resource is an entity that provides functionality to the applications in a Commerce Server 2009 site and that contains properties that you can configure by using Commerce Server 2009 Manager. The two types of resources are global resources and site resources.

Global Resources

Global resources are resources that you can share across Commerce Server 2009 sites. Commerce Server 2009 installs the following global resources when unpacking a package file or during Commerce Server 2009 configuration:

  • CS Authentication. Configures the authentication and identification method for your Commerce Server 2009 site when you use AuthManager or AuthFilter methods. These methods are deprecated in Commerce Server 2009. We recommend instead that you use the Commerce Server 2009 membership provider method for authenticating users. For more information about how to implement authentication, see Authentication Concepts and Tasks. When you use the Commerce Server 2009 membership provider for authenticating users, the CS Authentication resource is not used.

  • Data Warehouse. Imports and manages Web site data from Web log files, Commerce Server 2009 databases, and other data sources. This is an optional global resource that is installed when you unpack the DW.pup package.

  • Direct Mailer. Sends personalized or non-personalized mailings to large groups of recipients. This is an optional global resource that you can install and configure by using the Installation Wizard and the Configuration Wizard.

  • Profiles. Creates data sources for storing profile data, and creates and stores profile definitions and properties. Commerce Server 2009 installs this resource when you unpack a site.

Site Resources

Site resources are resources that you cannot share across Commerce Server 2009 sites. Commerce Server 2009 installs site resources when you unpack a site and create the associated databases. The default site resources that are available when you unpack a site are as follows:

  • Inventory. Manages the connection to the Inventory System database that Commerce Server 2009 uses to store inventory schema and inventory SKU data. Inventory data is stored in the product catalog site database.

  • Marketing. Manages the connection to the Marketing System and the Mailing List Management site databases that Commerce Server 2009 uses to store data about campaigns, ads, discounts, direct mail, and user lists.

  • Product Catalog. Manages the connection to the product catalog site database that Commerce Server 2009 uses to store catalog schema and product data.

  • Transactions. Manages the connection to the Orders System Transactions site database that Commerce Server 2009 uses to store data such as order numbers, order groups, and baskets.

  • Transaction Config. Manages the connection to the Orders System Transactions Configuration site database that Commerce Server 2009 uses to store data such as region codes, tax rates, order status codes, and shipping methods.

A Commerce Server 2009 application is a logical representation of a Web application in IIS. It appears in both the Commerce Server 2009 Manager and IIS management console trees. In the IIS management console tree, a Commerce Server 2009 application is either at the root directory level of the Web site or at a subdirectory level of the Web site. Commerce Server 2009 applications are also referred to as Web services.

When you unpack a site, a Commerce Server 2009 Web application is created. Customers use their browser to access this application. Web applications typically involve purchasing or ordering products that customers browse online, put in a basket, and ultimately acquire through the check-out process.

Depending on the components you select to install, as many as four additional Web applications (Web services) are created when you unpack a site:

  • Catalog Web Service

  • Marketing Web Service

  • Orders Web Service

  • Profiles Web Service

These applications are not counted against the Commerce Server 2009 Standard Edition limit of one Commerce Server 2009 application per site.

In Commerce Server 2009, a Web server is a computer on which IIS is installed. The Web server contains the virtual directories, files, and subfolders for a Commerce Server 2009 site. A Commerce Server 2009 deployment can have multiple Web servers that together form a Web farm.

A Web site is an IIS Web site that is running on a specific TCP port number. Examples are the "Default Web site" or "Administration" Web site. By default, these sites are installed with IIS.