+

Search Tips   |   Advanced Search

Syndication overview

Use syndication to replicate WCM data from a web content library on one server to a web content library on another server. A syndicator defines a connection to the subscriber and indicates which libraries are to be replicated to the subscriber. A subscriber defines a connection to the syndicator, and receives the data replicated from the libraries specified by the syndicator. Syndicators can syndicate libraries to multiple subscribers, and subscribers can subscribe to libraries from multiple syndicators.

First-time syndication to an existing library is not supported. If you attempt to syndicate a library to a subscriber that already has a library with the same name, an error results.

For two-way syndication, first establish the relationship from syndicator to subscriber. After the libraries have been replicated to subscriber, set up the relationship between subscriber and syndicator.

Items in the authoring environment, including templates, components, and content items, are stored in web content libraries. Syndication between applications occurs on a library by library basis.


Portal versions

Syndication is supported between different versions of the same release. Syndication is generally not supported between different releases.


Syndication methods

If you move a draft item from a library using "all item" syndication to a library using "live item" syndication, the draft item will also be moved on the subscriber because the action occurred on the library using "all item" syndication. This behavior allows for some draft items to be included in a subscriber library even though "live item" syndication is being used.


Web content libraries and syndication relationships

If we are using a single authoring server to develop content for two delivery servers, a standard approach is to use two web content libraries, one for each, and set up a distinct syndication relationship for each delivery server. We could also divide content into three libraries, with one library containing data common to both sites, and the other two libraries containing site-specific content.

Information about a Library is only syndicated the first time syndication occurs and not on subsequent updates and rebuilds. If a library is renamed or library user access is changed, this information is not syndicated to the Subscriber. If you change the name of a library or change user access to a library, manually make the same changes to any subscriber libraries if you want the same settings on all the syndicated libraries.

If content from library A uses an item from library B, include both libraries in the syndicator. If we add a new library to a syndicator after the initial syndication, click Update to force the new library to be syndicated immediately.


Access control

Access control settings for libraries are not included as part of syndication. Both servers should be configured to use the same user repository. If different user repositories are used, syndication will occur but there will be errors in the subscriber log indicating missing users. If virtual users and groups, such as "All authenticated" and "Anonymous Users", using the same user repository is not required.

When syndicating for the first time, manually set access permissions on the subscriber's library. The settings on the subscriber library do not have to match those on the syndicator library.


Parent: Administer syndication