E-mail
Here is a procedure that we received from IBM that helped us repair the web content syndication between two WebSphere Portal Servers. Syndication was not working for us and we tried just about everything (updating the syndicator, doing a full rebuild, recreating the pair, etc.)
I call this a last-ditch procedure since I think all the obvious stuff should always be tried first. In the end, this procedure did save us, so I am noting it for when we have to do it again.
- Stop Portal (synicator and subscriber) and clear the contents of the following directories:
- <Profile Root>/tranlog
- <Profile Root>/temp
- <Profile Root>/wstemp
- Reset event-log using ./ConfigEngine.sh wcm-reset-event-log
- See Resetting the Web content event log
in the WebSphere Portal 6.1 InfoCenter for more information
- See Resetting the Web content event log
- Check WcmConfigServices.properties file on syndicator for:
- connect.moduleconfig.syndication.inittasks=true
- deployment.subscriberOnly=false
- and on the subscriber check:
- connect.moduleconfig.syndication.inittasks=true
- deployment.subscriberOnly=true
- You may wish to clear the contents of the Portal server logs directory
- Start Portal
- Recreate synd/sub pair
If things aren't working after that, you probably need to enable syndication tracing and collect up some logs for the guys and gals at IBM.
 | While doing this process, we noticed that our .properties file somehow got renamed to .propertie (without the s). Not sure how it happened. It could be a bug in the script. In any case, renaming the file (adding the s back) and restarting Portal worked. |
Labels: