As described above, each component that generates records has a documentSubmitter property that is set by default to a component of a class that implements the atg.repository.search.indexing.DocumentSubmitter interface. These components perform two main functions:
Converting the output from the formats used by the older Forge-based deployment template to the formats used by the CAS-based deployment template.
Submitting the data to Guided Search for indexing.
The Guided Search integration includes several DocumentSubmitter components:
The
/atg/endeca/index/DataDocumentSubmitterand/atg/endeca/index/DimensionDocumentSubmittercomponents are of classatg.endeca.index.RecordStoreDocumentSubmitter. This class submits records to CAS using the Record Store API. TheDimensionDocumentSubmittercomponent is configured to rename the dimension value properties in the submitted records to reflect the naming conventions used with CAS-based deployment templatesThe
/atg/endeca/index/ConfigImportDocumentSubmittercomponent is of classatg.endeca.index.ConfigImportDocumentSubmitter. This component converts schema records to the format used by Endeca Configuration Repository and submits the schema configuration to it using the Configuration Import API.
In addition, the Guided Search integration includes the atg.repository.search.indexing.submitter.FileDocumentSubmitter class, which you can use to submit records to files for debugging purposes.
This section discusses the various document submitter classes and components.
