Reset the web content event log

Overview

For debugging, we can reset the web content event log on a syndicator server. Changes are syndicated to corresponding subscribers.

Enable the reset event log module by adding the following parameters to the WCM WCMConfigService service:

• connect.businesslogic.module.reseteventlog.class=com.ibm.workplace.wcm.services.eventlog.ResetEventLogModule
• connect.businesslogic.module.reseteventlog.remoteaccess=true
• connect.businesslogic.module.reseteventlog.autoload=false

Reset the web content event log under these circumstances:

• The contents of the repository have been modified through an external mechanism such as a JCR import or some other custom application.

• As a post migration step during migration prior to syndication.

• In order to troubleshoot syndication problems such as items on the syndicator not being sent.

Reset the event log

1. Verify the property DbSafeMode is set to false in...

   WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

2. Manually delete any purged items on the subscriber

   Any objects that were "purged" on the syndicator since the last syndication will not be purged on the subscriber. Purged objects are lost since the event log does not maintain records of objects that were deleted.

3. On the primary node only, run...

   cd WP_PROFILE/ConfigEngine

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

   If -Dfix=true is omitted, then the task will run in report-mode only.

Parent

Additional configuration options

Previous

Export and import a web content library

+

Search Tips   |   Advanced Search