To create an Endeca application to integrate with ATG, use the Endeca deployment template designed to work with product catalog data. (See the Endeca Deployment Template Module for Product Catalog Integration Usage Guide for details.) This deployment template has a script that creates various Endeca CAS (Content Acquisition System) record stores that the ATG-Endeca integration writes to. The naming convention for these record stores is:
application-name_language-code_record-store-type
So for an application named ATGen that indexes ATG product catalog data in English, the record stores are:
ATGen_en_data-- Holds data records representing SKUs or products.ATGen_en_dimvals-- Holds dimension value records generated from the category hierarchy and from the hierarchy of repository item types.ATGen_en_schema-- Holds records representing property and dimension definitions generated from the set of ATG properties being indexed.
The ATG-Endeca integration includes classes and components that write to these records stores. Note that there is also an ATGen_en_prules record store, which is used to create Endeca precedence rules. The integration does not provide a way to create precedence rules or write to this record store, but you can create precedence rules directly in Oracle Endeca Commerce. See the Oracle Endeca Commerce documentation for information about creating precedence rules.
