ATG Commerce Reference Store includes all of the code, data, and configuration necessary for setting up a complete multi-server environment. When you set up Commerce Reference Store using CIM, it assembles separate EAR files for your ATG Content Administration (publishing) server and your storefront (production) server. Depending on the options you specify, these environments may include support for ATG Search, internationalization, or both. See the ATG Commerce Reference Store Installation and Configuration Guide for more information.

If you reassemble your EAR files, you should be sure to specify the modules for the options you want to include. The following table describes the main Commerce Reference Store application modules and indicates which servers each module should be run on:

Module

Description

Server

Store.Storefront

Runs the ATG Store web application.

Production

Store.Fulfillment

Runs ATG Commerce Fulfillment with CRS extensions.

Production (or separate ATG instance)

Store.DCS-CSR

Adds configuration to ATG Commerce Service Center for working with ATG Store.

Agent-facing

Store.Search

Enables use of ATG Search.

Publishing and Production

Store.Estore

Contains the back-end classes for ATG Commerce Reference Store.

Publishing and Production

Store.Estore.Versioned

Enables use of versioned repositories.

Publishing

Store.Estore.Switching

Enables use of switching datasources.

Production

Store.Estore.International

Enables German ATG Store.

Publishing and Production

Store.Estore.International.Search

Enables German ATG Store with ATG Search.

Publishing and Production

If Your Environment Does Not Include ATG Content Administration

In an environment that includes ATG Content Administration, assets are imported into the publishing server during the installation process. These assets include both repository-based assets such as the product catalog, and file-based assets such as targeters and scenarios. These assets are subsequently deployed to the production server for use on the ATG Store site. This process ensures that file-based assets are managed properly through CA’s versioned file store.

This means, however, that if you run the ATG Store site in an environment that does not include CA, the file-based assets won’t be present and the site will not function properly. Therefore, Commerce Reference Store includes a special Store.Storefront.NoPublishing module, which adds the file-based assets to the production server. Include this module when you assemble your production EAR file. Note that the file-based assets in this module are not accessible through the ATG Business Control Center and cannot be easily removed from the site. Therefore, you should not use this option if your environment does include CA.

 
loading table of contents...