+

Search Tips   |   Advanced Search

Cross version syndication

Cross version syndication is the preferred method of refreshing web content after an initial migration. The portal migration process is used to migrate web content, however after the initial migration is complete, syndication is used to keep the migrated system synchronized with the older system.

Cross-version syndication is supported between the following releases. Syndication from a newer release to an older release is not supported:

  • WebSphere Portal version 7.0.0.2 with CF26 or higher.
  • WebSphere Portal 8.0.0.1 with CF09 or higher.
  • WebSphere Portal 8.5 or higher.

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.


Fix-pack upgrades

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.

    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. Syndicating from an older fix-pack to a newer level is not supported.


Migrate only Web content

Instead of migrating an entire system, it is possible to syndicate only web content from supported versions of Web Content Manager 7.0.0.2 to a new installation of Web Content Manager 8.0.0.1 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 Migrate from Web Content Manager version 7.0x or 8.0.x