When you use Merchandising with ATG Content Administration, you must configure the Catalog Maintenance Service, and if you have custom catalogs, the Catalog Completion Service, for each agent server in a cluster that will receive deployed Merchandising content, perform the following tasks:
Specify the
DCS.PublishingAgentmodule during application assembly and startup, to ensure that the Catalog Maintenance Service runs as expected.Set the
enabledproperty of the/atg/commerce/catalog/custom/CatalogCompletionServicecomponent totrue, to ensure that asset properties are recalculated automatically after changes to the property values on which they depend.For Staging and Production targets: During
.earfile creation on the ATG Content Administration side, include the–layer stagingflag. When you use this flag, you can use the standard staging and production server repository configurations on the ATG Content Administration side, without modifying the workflow.
In addition, you must configure one agent server in the target site cluster to run the Catalog Maintenance Service (CMS). If more than one agent server is configured to do this, only one will run the CMS after a successful deployment. See the chapter Using the Catalog Maintenance System in the Core Commerce Programming Guide.
Additional configuration is required for one-off targets that accept trial deployments, which are outside the constraints of workflows. For more information about target servers, see the Content Administration Programming Guide.
