To create a Guided Search EAC application to integrate with the Oracle Commerce Platform, use the CAS-based deployment template described in the Oracle Commerce Guided Search Administrator’s Guide. (If your Oracle Commerce Platform environment is based on Oracle Commerce Reference Store, you can use the CAS-based deployment template that is included with it.) The deployment template includes a script that creates CAS (Content Acquisition System) record stores that the Guided Search integration submits records to. The naming convention for these record stores is:

applicationName-recordStoreType

For an application named ATGen that indexes GSA repository data, the record stores are:

The Guided Search integration includes classes and components that create records and write them to these records stores. In addition, the integration includes classes and components that create schema records, convert them to Configuration Import API objects, and submit these objects to the Endeca Configuration Repository.

Note that there is also an ATGen-prules record store, which is used to create Guided Search 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 Guided Search. See the Guided Search documentation for information about creating precedence rules.