The following are the modules you’re most likely to use with ATG Merchandising:
Module | Description |
|---|---|
| Contains submodules that contain HTML UIs for ATG Commerce applications running on ATG Content Administration. Specifying this module causes |
| Contains an HTML UI informally called ATG Merchandising UI, in which merchandising activities are performed. This module accesses ATG Content Administration ( This module makes ATG Merchandising and ATG Content Administration available to a single instance. |
| Contains an HTML UI used by Search Merchandising and Dynamic Search and Navigation, which are ATG Search add-on features of ATG Merchandising. This module accesses the core Commerce parts of the ATG Search integration framework ( |
| Contains code that supports versioned core Commerce extensions to the ATG Search integration framework. If you use ATG Search, ATG Content Administration and ATG Commerce, you must specify this module. |
| Contains code that supports versioned custom catalogs extensions to Commerce Search. If you use ATG Search, ATG Content Administration and either Business Commerce or custom catalogs with Consumer Commerce, you must specify this module. |
| Contains ATG Content Administration extensions to the Business Commerce product. |
| Contains ATG Content Administration extensions to the Consumer Commerce product. |
| Contains ATG Business Control Center components. You must use this module when you want to access the ATG Business Control Center. |
In general, the modules you use for your development environment, which is the environment in which ATG Merchandising runs are nearly identical to those used in production. If the production environment uses the B2BCommerce module, the development environment uses the B2BCommerce.Versioned module, indicating the Business Commerce with support for versioning (Content Administration).
When you build your application, the ATG Commerce module you use indicates the type of Commerce product (Consumer Commerce or Business Commerce) or the type of catalogs (standard or custom) your site implements as well as other optional Commerce features. Web applications that use custom catalogs must specify the DCS.DynamicCustomCatalogs.Versioned module when running ATG Merchandising. Note that non-dynamic custom catalogs are not supported in ATG Merchandising. When you use B2Bcommerce.Versioned, you use the dynamic custom catalogs automatically.
For a list of modules, see the Appendix A: ATG Modules in the ATG Programming Guide.
