A common setup is to use ATG Content Administration to manage a versioned repository (such as a product catalog), and then to index the corresponding deployment (nonversioned) repository on your staging or production environment. In this setup, when a repository is modified and deployed, the incremental indexing system needs to be notified about the changes so they can be reflected in the next incremental index.
To ensure that this happens, an IndexingOutputConfig
component needs to be running in the ATG Content Administration environment and listening for change events on the deployment repository. To configure this IndexingOutputConfig
component, set the targetName
property to the name of the deployment target.