Resetting the web content event log

From time to time you may need to reset the web content event log. The event log can be reset only on a syndicator server. Any changes made by resetting the event log are then syndicated to its corresponding subscribers. In most cases you reset the event log on the server you have imported or migrated data onto, or on a syndicator to troubleshoot syndication problems in a syndication relationship.

Before you begin

You must first enable the reset event log module by adding the following parameters to the WCM WCMConfigService service using the WebSphere® Integrated Solutions Console:

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

About this task

You should 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.

Note:

Before resetting the web content event log you should edit the wkplc_dbtype.properties file and ensure the DbSafeMode property is set to false. This is located under wp_profile_root/ConfigEngine/properties
In clustered environments, you should only reset the event log on the primary node.
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. To clean up purged items on a subscriber, you will need to go the subscriber and manually delete them.

For Windows, UNIX and IBM® i.

Run the run-wcm-admin-task-reset-event-log task from the wp_profile_root/ConfigEngine directory.

Windows: ConfigEngine.bat run-wcm-admin-task-reset-event-log -Dlibrary="library_name" -Dfix=true
UNIX: ./ConfigEngine.sh run-wcm-admin-task-reset-event-log -Dlibrary="library_name" -Dfix=true
IBM i: ConfigEngine.sh run-wcm-admin-task-reset-event-log -Dlibrary="library_name" -Dfix=true

Note: If -Dfix=true is omitted, then the task will run 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 that has been configured with the defaultLibrary property in the WCM WCMConfigService service is used.

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

For z/OS®:

Submit the EJPSWCMR job to reset the event log. This job is created when you create the jobs for installing the product with the Customization Dialog.

Parent topic: Maintaining web content