Configure syndication



Overview

Syndication is used to synchronize web content between servers. You can configure when syndication is run, and how often it is run.

Syndication frequency can only be set per server (not by syndicator)

Manual Syndication can only be enabled per server (not by syndicator)

You cannot syndicate to a pre-existing library with the same name as the source library. This is one to watch out, particularly because a Web Content library is created in each server by default. Although the libraries have the same name, they have different UUIDs. That means that in order to syndicate the .Web Content. library from one server to another, the library must be either deleted or renamed on the subscriber server.

Search Collections are not syndicated which means they have to be created on both servers first before syndication.

An item will fail to syndicate if the item it references has been deleted, but not purged, on the subscriber machine. To fix, purge the deletion and rebuild the subscription.

An item will fail to syndicate if an item with the same name and same site path has been created on the subscriber machine (the items will have different ids). Delete or rename the duplicate item on the subscriber machine JSP files used by Workplace Web Content Management JSP components aren't syndicated, so you need to ensure that they manually copied to any Subscriber servers.

When performing two-way Syndication, both Syndicator's must syndicate all Libraries using the "All Items" scope or else Syndication will not work correctly.


Syndication between clusters and high availability

If manual Syndication is required, then set...

in...

Once in manual mode, syndication is only possible by manually initiating it from the Syndicator and Subscriber Administration Portlets. Manual Syndication can only be set on a server-wide level.

When syndicating between clusters, only one Syndicator/Subscriber pair (that can be created using any node) is required. Additionally, when configuring the Syndicator/Subscriber pairs, utilise the web server address of each cluster in the Syndicator and Subscriber dialogs to ensure proper fail over occurs.

If a subscriber node is in the middle of syndicating some changes and it goes down, then the current syndication cycle will be considered failed and will be re-tried by the next subscriber node (once the syndication interval "deployment.itemChangedTaskDelay" is reached).

If a syndicator node goes down during syndication, then the syndication will continue using the next available syndicator node.

To ensure dynacache replication is enabled, edit...

and verify that the 'enable' setting is set to 'true'...


See

  1. Syndication concepts
  2. Work with syndicators and subscribers
  3. Syndication properties
  4. Disable automatic syndication
  5. Change the syndication interval
  6. Web Content Management syndication FAQ


Configure Web Content Manager


+

Search Tips   |   Advanced Search