There are two scenarios for building the subscriber environment:
- Separate migration of two servers
- Migrate one server and duplicate it to build the second server
Separate migrations are preferred when a system has separate applications and pages, or when distinct application server settings must be retained after migration. Building a new server is preferred when there are minimal differences between systems or when all settings must be configured to match the new system topography and infrastructure.
Before syndication commences you must copy the JCR domain from the syndicator to the subscriber. This step reduces the time required for the initial syndication and reduces the possibility of duplicate drafts or versions that can occur if this step is omitted.
Separate migrations of two servers
In this scenario, both servers are migrated. After migration, the JCR domain is copied from the syndicator to the subscriber. Syndication is then enabled.
Migrate one server
In this scenario only one server is migrated. Secondary systems are built from fresh installations. Applications and pages are duplicated using Release Builder and web content is syndicated. The JCR domain can be copied to accelerate syndication, however it is not required.
Secondary systems have extra requirements for virtual portals and managed pages. For more information, see Managed pages migration
If a post migration data update is required it must only occur on the primary system. Syndication should be used to propagate changes to the secondary servers in the system. After the data update has completed the JCR database is copied to the downstream servers before syndication occurs to ensure that all content is refreshed.
Parent topic: Migrating from Web Content Manager version 6.1