Syndication overview


Syndication is the method used by IBM Web Content Manager to replicate data from a web content library on one server to a web content library on another server.

To enable syndication, a syndicator and a subscriber must be defined:

The relationship between a syndicator and a subscriber can be either a one-way or two-way relationship.

Example: One-way syndication

Example: Two-way syndication

When enabling two-way syndication, first establish the syndication relationship from Application 1 to Application 2. Once the libraries have been replicated to Application 2, you can set up the syndication relationship between Application 2 and Application 1.

Although it is possible to set up more than one syndication relationship between the same two applications, there is no reason to do so. The additional syndication relationships are not required because once a syndication relationship has been established between two applications, no further relationships are established.

Syndicators can syndicate libraries to multiple subscribers, and subscribers can subscribe to libraries from multiple syndicators.

Example: Multiple syndication relationships


Syndication methods

There are three syndication methods available when configuring a syndication relationship:

Live items:

Live and projects:

All items:

Switching from "all item" syndication to "live item" syndication: When you switch from "all item" syndication to "live and projects" syndication or "live item" syndication, any drafts previously syndicated to the subscriber are not removed.

Move draft items between libraries: 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.


Version consistency

All servers participating in syndication must be of the same version for syndication to work as expected and to be in a supported state. Syndication is not supported between versions.

For example:

It is also recommended to keep environments consistent across all servers in system. For example, the same version of WAS must be used on all servers in system to ensure successful syndication.


Web content libraries and syndication relationships

All the items you work with as part of Web Content Manager authoring environment (templates, components, content items, and so on) are stored in web content libraries. When you syndicate data between applications, you do so on a library by library basis. As part of the definition of a syndicator or subscriber, you specify which web content libraries are to be included during syndication.

Because syndication is performed by library, it is important to consider how to organize content between libraries to support Web Content Manager environment. For example, suppose you are using a single authoring server to develop content for two delivery servers, an intranet site providing Human Resources information intended for internal employees of a company and an external Internet site providing marketing material intended for customers and others outside the company. A basic approach to support this environment would be to use two web content libraries, one for content specific to each site. You would then set up two syndication relationships with each going from the authoring server to the appropriate delivery server.

For easier management, you might divide content further into three libraries, where one library contains data common to both the intranet and Internet sites and the other two libraries contain site-specific content. The following example demonstrates this configuration, with the addition of two other authoring portlets so that the content of each library is maintained by a different authoring portlet.

In this case you might set up several syndication relationships between the authoring server and the delivery servers:

Web Content Manager provides flexibility in how you set up syndication relationships. If you need to syndicate multiple libraries from one server to another, you can choose to use one syndication relationship that includes all the libraries, or you can choose to use separate syndication relationships for each library, or even a combination of both approaches, depending on how many libraries you are syndicating. The best approach for situation depends not only on how many libraries are involved but also on how the libraries are related to one another. For example, you use a single syndication relationship for libraries that reference each other, as when one library contains design items like templates that are used by content in the other library. However, if the libraries are independent of one another and you think you might want to suspend syndication of one library but not the other, separate syndication relationships for each library can provide that.

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.

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 syndicated libraries.

If content from one library (Library A) uses an item from another library (Library B), include both libraries in the syndicator to ensure that all items are syndicated successfully. If you only include Library A in the syndicator, any items in Library A that reference items in Library B are not syndicated, and syndication errors are generated.

If you add a new library to a syndicator after the initial syndication, you click Update to force the new library to be syndicated immediately.


Access control when syndicating

Although syndication can be used to keep data current between libraries on different servers, access control settings for the libraries are not included as part of syndication. Depending on how environment is set up and what policies you have in place for library access, there are additional considerations for access control when using syndication.

User consistency

First time syndication on a new library


Syndication concepts

Related

Syndication tuning

Work with syndicators and subscribers

December 14, 2011
   

 


+

Search Tips   |   Advanced Search