Component: /atg/commerce/catalog/CatalogMaintenanceService

The CatalogMaintenanceService component is a container for the AncestorGeneratorService and the CatalogVerificationService (note, however, that the CatalogVerificationService is disabled by default); it provides a single point of access to those services and a consolidated view of their processing results.

The history log for each of the registered services can be viewed from the Dynamo Admin UI. This log is maintained only in memory and is discarded after a redeployment of Oracle ATG Web Commerce. The Oracle ATG Web Commerce platform logs can be used as a historical reference to the service logs.

You can execute or schedule any functions for either the AncestorGeneratorService or the CatalogVerificationService from the CatalogMaintenanceService. Therefore, this service can be scheduled to sequentially execute other services it contains, as opposed to scheduling each service individually.

CatalogMaintenanceService includes the following properties as well as the properties listed at the beginning of the Batch Services section:




An array of Nucleus paths to each contained service component. Each component is resolved by path and added to the servicesMap property.


A consolidated list of all the availableFunctions provided by the contained services.


Configures a default set of function names that are executed when none are provided, such as in schedule mode, or through the Java API. It can be any of the function names exposed by the availableFunctions property.

The CatalogMaintenanceService has a related /atg/epub/CatalogMaintenanceHelper component. This component is used by installations that use ATG Content Administration to manage their catalogs; it listens for ATG Content Administration deployments and runs catalog maintenance services automatically. For Oracle ATG Web Commerce purposes, the component’s important property is extraTriggeringAffectedItemDescriptors. By default, the CatalogMaintenanceHelper listens for changes to catalog items such as catalog, category, categoryInfo, product, productInfo, sku, and skuInfo. If you have created custom subtypes based on these item types, you can add them to this property, so that changes to these item types can also trigger catalog maintenance services. For example:


For general information on ATG Content Administration, see the ATG Content Administration Programming Guide.

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved. Legal Notices