Using cross-version syndication to migrate from Web Content Manager version 7.0Added by IBM on December 20, 2013 | Version 1 (Original)
|These are the migration options available when migrating from Web Content Manager version 7.0.
Planning for changes to web content when migrating from Web Content Manager version 7.0
Migration projects require careful planning to synchronize changes from the old production system with the new system. Content creation can still continue on the old system while the new system is installed. A typical migration plan includes time for provisioning, configuring, testing, and tuning infrastructure and software. Custom or third-party applications require their own migration procedures.
Cross version syndication
Cross version syndication is a feature that supports zero downtime migrations. Syndication from a newer release to an older release is not supported. 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.
Managed pages migration
Managed pages is automatically disabled during migration. It is recommended to enable managed pages after migration to take advantage of new features, such as syndication and versioning of pages, and the ability to manage pages in projects. When migrating systems that access web content from virtual portals there are additional steps to perform after enabling managed pages.
Library export and import and migration
Web content libraries can be exported from one system and imported onto another. This tool can be used as part of a migration, but there are some limitations to the use of this tool.