The main Guided Search integration modules are:
Module | Description |
|---|---|
| Includes the necessary classes for exporting data to CAS record stores and triggering indexing via the EAC, along with associated configuration. |
| Adds configuration for running on an ATG Content Administration instance. This module adds basic record generation configuration for ATG Content Administration servers, including a deployment listener. |
| Contains classes and configuration for creating an Assembler instance that has access to the data in your application’s MDEX engines. Also provides classes for querying the Assembler for data and managing the content returned. |
| Configures components for creating CAS data records from products in the catalog repository and dimension-value records from the category hierarchy. |
| Modifies configuration so that CAS data records are generated based on SKUs rather than products. |
| Adds Commerce-specific configuration for running on an ATG Content Administration instance. |
| Contains Commerce-specific configuration for query-related components. |
Additional modules for indexing Web content in the content management repository are described in the Indexing the Content Management Repository chapter.
Note that when you assemble an application that includes any of the modules listed in the table above, other modules they have dependencies on, such as DAF.Endeca.Base or DAF.Search.Index, are automatically included in the EAR file as well. In addition, some of the Guided Search-specific modules pull in classes from other search modules (without including the modules in their entirety) through the ATG-Class-Path entries in their manifest files.
