Cross version syndication is supported on these versions:
- From Web Content Manager version 184.108.40.206 with CF26 or higher.
- To Web Content Manager version 220.127.116.11 with CF09 or higher.
On supported versions, syndication is the preferred method of refreshing web content after an initial migration. Syndication replaces the post migration data update process, which is no longer supported on these versions.
There are no special steps required to configure syndication between releases. The procedure to enable syndication is the same no matter if the versions differ or not. When an existing subscriber is migrated, the existing pair will continue to function normally. There are no additional limits to the kind of items or changes that can be updated between versions, although care must be taken whenever changes are made directly to the subscriber since this carries the risk of creating a conflict that can block items from syndicating.
Cross version syndication can also be used when applying cumulative fix-packs. It is important to understand the difference in strategy between a fix-pack upgrade and a migration.
In migration, an older release syndicates to newer release. The migration strategy is to migrate the subscriber first then subscribe to the older system to receive updates.Fix-pack upgrade
Syndicators can run a newer fix-pack level than subscribers. Therefore the strategy is to upgrade the syndicator first. This provides the opportunity to test the process and evaluate any new features without committing to an upgrade in production.
Migrating only Web content
Instead of migrating an entire system, it is possible to syndicate only web content from supported versions of Web Content Manager 18.104.22.168 to a new installation of Web Content Manager 22.214.171.124 with CF09 installed. For large content repositories this will be slower than a full migration, that updates the data directly in the database rather than exporting, streaming, and importing everything. It is not possible to accelerate syndication between versions by copying the JCR domain.
Parent topic: Migrating from Web Content Manager version 7.0