To make your product catalog available for searching, the Oracle ATG Web Commerce platform must transform the data into the appropriate format, and then submit this data to Oracle Endeca Commerce for indexing.
The process of indexing ATG product catalog data in Oracle Endeca Commerce works like this:
ATG components transform the catalog repository data into Endeca records that represent Endeca properties, dimensions, and schema:
Properties of ATG products and SKUs are used to create Endeca properties and non-hierarchical dimensions.
The ATG category hierarchy is used to create a hierarchical category dimension in Oracle Endeca Commerce. The hierarchy of repository item types in the product catalog is used to create another hierarchical Endeca dimension.
An Endeca schema is created by examining the set of ATG properties to be indexed.
The generated records are submitted to Endeca CAS data, dimension value, and schema record stores.
The Endeca EAC is invoked, which creates Forge processes that process the record stores and invoke indexing.
This chapter provides an overview of the classes and components that perform these steps, and the user interface provided for managing the process. Other chapters of this book provide more detail about configuring and using these and other classes and components to work with the product catalog in your Oracle ATG Web Commerce environment.
