CatalogMaintenanceService Is Not Automatically Triggering After CA Asset Deployment
(Doc ID 2073479.1)
Last updated on OCTOBER 18, 2019
Applies to:
Oracle Commerce Platform - Version 10.2 and laterInformation in this document applies to any platform.
Symptoms
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 .
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |