The indexing process for Commerce sites is configured through the /atg/commerce/search/ProductCatalogOutputConfig component and other related components described in the ATG-Endeca Integration Guide. These components are configured to create Endeca data, dimension value, and schema records, which are submitted to Oracle Endeca Commerce for indexing.

The XML definition file used for the ProductCatalogOutputConfig component in Commerce Reference Store is an XML combination of the definition files included in the DCS.Endeca.Index module, the DCS.Endeca.Index.SKUIndexing module, and Commerce Reference Store-specific extensions added in the Store.Endeca.Index module. The Commerce Reference Store extensions add Commerce Reference Store-specific catalog properties to the index. For internationalized sites, the Store.Endeca.International.Index module also adds configuration for including content in multiple languages.

Each product and SKU in the Commerce Reference Store catalog repository has a siteIds property whose value is a Set of the sites the item appears on. Certain products appear only on CRS Store US and CRS Store Germany, other products appear only on CRS Home, and some products appear on all three sites.

The records generated for a SKU include a separate sku.siteId property value for each site listed in the siteIds property. For example, the records for a SKU found on both CRS Store US and CRS Store Germany include:

<PROP NAME="sku.siteId">
  <PVAL>
    storeSiteUS
  </PVAL>
</PROP>
<PROP NAME="sku.siteId">
  <PVAL>
    storeSiteDE
  </PVAL>
</PROP>

This information is used to determine which results to return when a query is issued from a site, as discussed in Multisite Search.