This guide addresses only certain basic configuration options for IndexingOutputConfig components. See the ATG Search Administration Guide for detailed information on this component. By default Oracle ATG Web Commerce Search includes an instance of this component called ProductCatalogOutputConfig, which is intended for use in indexing Oracle ATG Web Commerce catalogs.
To ensure that this component is started automatically, you must add your ProductCatalogOutputConfig to the list of exported services in the /atg/dynamo/server/RmiServer.properties file (if you are using CIM, this step is done automatically). For example:
exportedServices+=/atg/commerce/search/ProductCatalogOutputConfig
Additional configuration depends on your system architecture:
Architecture | IndexingOutputConfig Component Configuration Required |
|---|---|
Indexing production repository from the asset management instance | None |
Indexing production repository from the production instance | On the asset management instance, configure the following:
The |
Indexing production and staging repositories from the asset management instance | None |
Indexing production and staging repositories from the asset management instance | On the asset management instance, configure the following:
The On the asset management server, configure the following:
The |
For all servers, make sure that your IndexingOutputConfig component is started automatically (if you are using CIM, this step is done automatically). You can do this by adding it to the initialServices list as shown:
/atg/commerce/Initial:
initialServices+=\
/atg/commerce/search/ProductCatalogOutputConfig_staging
If you are using a staging server, you must also add the ProductCatalogOutputConfig_staging component to the /atg/search/repository/IndexingDeploymentListener on the asset management server in order for synchronized indexing (see Synchronizing Versioned Repository Deployment and Indexing) to work on that instance.
indexingOutputConfigs+=\
/atg/commerce/search/ProductCatalogOutputConfig_staging
