Reset the web content event log

Reset the web content event log if...

• The contents of the repository are modified through an external mechanism such as a JCR import or some other custom application.
• As a post migration step during migration before syndication.
• To troubleshoot syndication problems such as items on the syndicator not being sent.

The event log can be reset only on a syndicator server. Changes made by resetting the event log are syndicated to its corresponding subscribers. In most cases, we reset the event log on the server we imported or migrated data onto, or on a syndicator to troubleshoot syndication problems in a syndication relationship.

• Before resetting the web content event log, edit wp_profile_root/ConfigEngine/properties/wkplc_dbtype.properties and ensure the DbSafeMode property is set to false.

• In clustered environments, reset the event log only primary node.

• Objects were purged on the syndicator since the last syndication are not purged on the subscriber. Purged objects are lost since the event log does not maintain records of objects that were deleted. To clean up purged items on a subscriber, we need to go the subscriber and manually delete them.

To reset:

cd wp_profile_root/ConfigEngine.
./ConfigEngine.sh run-wcm-admin-task-reset-event-log -Dlibrary="library_name" -Dfix=true -Dlibrary="library_name" -Dfix=true

Note: If -Dfix=true is omitted, then the task runs in report-mode only.

Note: The library specified in the command is the library to be scanned by the reset event log task. If the query parameter "library" is omitted, the default library configured with the defaultLibrary property in the WCM WCMConfigService service is used.

Note: When running this task on a virtual portal, add either -DVirtualPortalHostName=name or -DVirtualPortalContext=virtual_portal_context to the command.

Parent topic: Web content administration tools

• Export and import web content libraries

References: