The Admin Traceability feature enables the logging of changes made to objects in the PCD or to portal related configurations. This includes changes made in the administration environment, as well as changes made via the Transport mechanism and the Generic Creator service (which automates content creation via XML). Changes made by users (for example, using Web Page Composer) are also logged. The Admin Traceability service writes its entries to the change log of the Java engine.
You can log all PCD objects, or select a specific set of object classes to log. You can also specify, for each debug severity level, a set of object paths to log. The following types of changes to PCD objects are logged:
Creating an object
Deleting an object
Renaming an object
Sorting the child list of an object
Redefining the target of a delta link
Importing a unit object
Changing permissions of an object
Deploying to GPAL applications that are already used by objects in the portal
Changes related to critical portal configurations are also written to the change log. The following are examples of portal configurations that are logged:
Changes to portal applications or to service configurations. For example, changing a property of a portal service.
Enabling, disabling, or clearing the navigation cache or the OBN cache.
Changes to the Desktop Rule Collection.
Only objects in the PCD data namespace are logged. No personalization changes are logged.
The following topics are described:
Configuring general log file properties.
For more information, see Configuring Log File Properties .
The default location of the log file and configuring a custom location.
For more information, see Configuring the Log File Location .
Determining which PCD objects to include in the change log.
For more information, see Configuring the Objects to Log .
Viewing log messages and understanding the information they include.
For more information, see Viewing Log Messages .