If you are not already familiar with the Commerce Reference Store architecture, see the Commerce Reference Store documentation, particularly the Commerce Reference Store Overview, Commerce Reference Store Installation and Configuration Guide, and the ATG-Endeca Integration Guide.

Since CRS-M is based almost entirely on the existing Commerce Reference Store application, we will not provide details here, but rather explain how CRS-M sits logically on top of Commerce Reference Store, as an extension to it, and the details of those extensions that CRS-M applies to the existing Commerce Reference Store application.

CRS-M makes extensive use of configuration layering to extend existing Commerce Reference Store classes, a practice that is extremely common in ATG applications. It then provides a set of new Mobile-optimized JSPs on top of the extended Commerce Reference Store backend.

The CRS-M Store.Mobile module provides an example of how to set up a dedicated mobile site so that you can separately manage your mobile site through Site Administration. If you are unfamiliar with multisite, see the Multisite Administration Guide. CRS-M creates pairs of sites, for example, a desktop ATG Home site, and its mobile ATG Home counterpart.