Start of change

Migrating a large domain

Before you start

This task is part of the following larger task: See the larger task to understand the context of this task and what you must do before you start this task.
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 more than when migrating a small domain. For example, the order of migration might be as follows:
  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 in 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 Message Brokers Toolkit Version 5.0 after they have been saved using Message Brokers Toolkit Version 6.0. See Coexistence with previous versions and other products for more information.

Related concepts
Coexistence with previous versions and other products
Related tasks
Planning for migration
Migrating a small domain
Migrating multiple domains
Migrating a high availability domain


End of change