Syndication Issues : Updated WCM Content not getting syndicated from one environment to another
Root Cause:
Event log records which track the changes of WCM contents were corrupted.
Fix applied
First enable the reset event log module by adding the following parameters to the WCM WCMConfigService service using the WebSphere® Integrated Solutions Console:
Restarted Portal Server.
Ran the command ConfigEngine.bat wcm-reset-event-log to delete all change records.
http://infolib.lotus.com/resources/portal/8.0.0/doc/en_us/PT800ACD004/wcm/wcm_config_reset_event_log.html
Event log records which track the changes of WCM contents were corrupted.
Fix applied
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
Restarted Portal Server.
Ran the command ConfigEngine.bat wcm-reset-event-log to delete all change records.
http://infolib.lotus.com/resources/portal/8.0.0/doc/en_us/PT800ACD004/wcm/wcm_config_reset_event_log.html
No comments:
Post a Comment