Planning to migrate a large domain

This topic explains how to plan to migrate a large domain.

If you are using the Version 5.1 Message Brokers Toolkit, replace all references in this topic to "Version 5.0" with "Version 5.1".

On a large domain, it might not be possible to migrate all components at the same time. In this situation, the migration of the components might need to be split up. For example, the order of migration might be:
  1. Migrate a test Message Brokers Toolkit and a test Configuration Manager
  2. Migrate a test broker
  3. Migrate more instances of the Message Brokers Toolkit
  4. Migrate more brokers
  5. Migrate remaining components
The migration order is flexible because Version 6.0 components can coexist with Version 5.0 components within a single domain. However, there are restrictions on coexistence. In particular, these will affect you if you plan to stagger the migration of several instances of the Message Brokers Toolkit, as some files cannot be read using the Version 5.0 Message Brokers Toolkit after they have been saved using the Version 6.0 Message Brokers Toolkit. See Coexistence with previous versions and other products for more information.

Before you start to perform migration, back up your resources.

Related concepts
Coexistence with previous versions and other products
Related tasks
Planning for migration from Version 5.0
Planning to migrate a small domain
Planning to migrate multiple domains
Planning to migrate a high-availability domain