CatalogMaintenanceService Is Not Automatically Triggering After CA Asset Deployment
Last updated on MARCH 02, 2017
Applies to:Oracle Commerce Platform - Version 10.2 and later
Information in this document applies to any platform.
After enabling the CatalogMaintenanceHelper on an Agent, then adding the Agent to the CA Topology, the CatalogMaintenanceService is not automatically triggering after CA deployment.
When manually triggering /atg/commerce/catalog/CatalogMaintenanceService via dyn/admin it is executing properly.
1) Commerce Administration
2) Basic Maintenance
3) Repository "/atg/commerce/catalog/ProductCatalog"
In the Agent side startup log and where the CatalogMaintenanceService is properly initialized .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms