Start of change

Planning for migration

This section explains what considerations you need to take into account to plan your migration. Complete the following steps:
  1. Decide how you want to migrate the product components:
    1. Decide where you want to migrate the product components to. You can migrate your components at the same location, or to a different location on the same system or on a second system. For example, you might want to migrate components to another location to maintain availability during the migration.
    2. Decide when you want to migrate the product components. You might want to preserve some components at the Version 5.0 level of code for now, and migrate them later.
    3. Decide the order in which you want to migrate your components. You can migrate components in any order, but your specific circumstances might mean that you want to migrate components in a particular order.

    See Coexistence with previous versions and other products for information about how WebSphere Business Integration Message Broker Version 6.0 can coexist on the same system with previous versions of the product, and how Version 6.0 components can operate with components from previous versions.

    See also the other topics in this section for more information about different migration scenarios:
  2. Decide how you want to use your existing resources with WebSphere Business Integration Message Broker Version 6.0.

    Except for user-defined extensions, you do not need to perform any tasks to migrate your development and deployment resources, such as message flow files, message set definition files, ESQL files, mapping files, XML Schema files, and broker archive files. You can just start using these resources with WebSphere Business Integration Message Broker Version 6.0.

    After you start using your resources in Message Brokers Toolkit Version 6.0, there are restrictions to using these same resources again with Message Brokers Toolkit Version 5.0 or Version 5.1. For more information, see Conditions for using migrated resources with previous versions of the Message Brokers Toolkit

  3. Decide whether you need to carry out any testing to ensure a successful migration.

    The purpose of testing your migration is to identify any problems that might arise during migration. For example, if problems arise you might need to restore some migrated resources to the level that you backed up before you started the migration, and any post-migration changes to these resources would be lost. Testing the migration allows you to identify problems like this and develop a strategy for dealing with further problems.

    See the other topics in this section for more information about different migration scenarios:

You do not need to change the configuration of a queue manager that is preserved during migration.

Related tasks
Migrating from Version 5.0 products


End of change