Table of contents | Next | Previous

Syndication Limitations

The following article highlights limitations which need to be taken into account when configuring and working with syndication.

• Syndication requires that both the Syndicator WCM instance and the Subscriber WCM instance are at the same WebSphere Portal and WCM build level with the same level of fixes.
  
• Syndication interval can only be set globally at the server level and not with each syndicator-subscriber relationship. Similarly automatic syndication can only be disabled globally at the server level.
  
• You cannot syndicate to a pre-existing library (on the Subscriber) with the same name as the Syndicator library. Even though the two libraries might have the same name, they have different unique ID's. The default Web Content library which is created with every WCM instance is an example of this scenario and hence it is recommended not to use the default Web Content library.
  
• Search Collections are not syndicated which means they have to be created on both servers.
  
• JSP files used by WCM JSP components aren't syndicated, so you need to ensure that they manually copied to any Subscriber servers.
  
• It is expected that the Syndicator and the Subscriber should share the same user repository if they use automatic syndication. If this is not the case, disable automatic syndication and perform manual syndication. The latter should be followed by executing the MemberFixer module.
  
• Library access control settings are not part of syndication, and hence you must manually set access permissions on the subscriber's library when syndicating for the first time.