For a CAS-based deployment template, an application’s schema definition is created as Configuration Import API objects, which are submitted to the Endeca Configuration Repository. These objects are created and submitted by the /atg/endeca/index/ConfigImportDocumentSubmitter component. The documentSubmitter property of components of class atg.endeca.index.schema.SchemaExporter (including the SchemaExporter, ArticleSchemaExporter, and MediaContentSchemaExport components) is set by default to:

documentSubmitter=/atg/endeca/index/ConfigImportDocumentSubmitter

For a Forge-based deployment template, an application’s schema definition is created as schema records, which are written to the schema record store. To configure this behavior, change the value of each SchemaExporter component’s documentSubmitter property to:

documentSubmitter=/atg/endeca/index/SchemaDocumentSubmitter