If you are using incremental indexing of your versioned content, whenever you modify and redeploy your content, the incremental loading system needs to be notified about the changes in order to reflect them in the next incremental index. Therefore, an IndexingOutputConfig component (IOC) must run in the ATG Content Administration environment (asset management server) and listen for change events on the deployment repository (production server).
You can actually load the content using an IOC running on either server. If you want to load content on the production server, configure the targetName property of the IOC on the management server to the name of the Content Administration deployment target. However, if you are loading content on the asset management server, you must not configure this property, or loading will not work.
If you are using a secure product catalog (for instance, as part of a B2B Commerce installation), you must change the indexing configuration on the asset management server, so that it can listen for change events on the on the deployment target repository. By default, this is configured to point to the non-secure catalog repository. To do this, in the /atg/commerce/search/IndexedItemsGroup.properties file, change the following property:
repository=/atg/commerce/catalog/ProductCatalog_production
The new value should be as shown:
repository=/atg/commerce/catalog/SecureProductCatalog
