Planning to migrate a small domain

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

It is likely that on a small domain, many or all components are installed on a single computer. In this situation, the simplest approach is to migrate all the components on that single computer at the same time. If this is not possible, install WebSphere Event Broker Version 6.0 at a different location on the same computer, or on a second computer, and migrate each component separately, because Version 5.0 components can coexist with Version 6.0 components within a single domain. See Coexistence with previous versions and other products for more information.

Migrate components in the order that best suits your environment. For example, a typical order in which to migrate the three major components might be as follows:
  1. Instances of the Message Brokers Toolkit
  2. Configuration Manager
  3. Brokers
If you migrate instances of the Message Brokers Toolkit first, you can begin to develop message flows that use features that are new in WebSphere Event Broker Version 6.0. If you migrate the Configuration Manager, administrators can prepare your Version 6.0 broker domain for deployment. Finally, when you migrate the brokers, you can run your new message flows.

Depending on the goals of migration, the order in which you migrate components can be different. For example, if the primary reason for migration is to make use of new broker functions, you might want to migrate the brokers first. Or, for example, if you plan to move your Configuration Manager to a new operating system, you might want to migrate the Configuration Manager first to discover any operating system or environment issues early on.

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 large domain
Planning to migrate multiple domains
Planning to migrate a high-availability domain