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 the Configuration and Installation Manager (CIM), it assembles separate EAR files for your publishing server and your production server. 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:





Runs the storefront web applications.



Runs Commerce Fulfillment with Commerce Reference Store extensions.

Production (or separate instance)


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



Enables Fluoroscope, a tool for viewing site HTML pages that reveals key JSP elements involved in rendering those pages.

Production (in a development environment only)


Enables integration with Oracle Recommendations on Demand.



Enables use of Oracle Endeca Commerce.

Publishing and Production


Enables querying of the Endeca Assembler.

Publishing and Production


Enables use of Oracle Endeca Commerce on an internationalized site.

Publishing and Production


Contains the back-end classes for Commerce Reference Store.

Publishing and Production


Enables use of versioned repositories.



Enables ATG Store Germany and ability to view ATG Store US and ATG Home in Spanish.

Publishing and Production

If Your Environment Does Not Include Content Administration

In an environment that includes 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 Commerce Reference Store storefronts. This process ensures that file-based assets are managed properly through Content Administration’s versioned file store.

This means, however, that if you run the Commerce Reference Store storefronts in an environment that does not include CA, the file-based assets will not 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 Business Control Center and cannot be easily removed from the site. Therefore, you should not use this option if your environment does include CA.

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved. Legal Notices