WebSphere Message Brokers
File: ah61102_
Writer: Kate Hostler Task topic This build: July 31, 2007 21:30:48
Planning for migration from Version 6.0
Plan the order and extent of the migration
of components and resources to Version 6.1.
This section explains how to plan your migration.
Complete the following steps:
Decide how you want to migrate the WebSphere®Message BrokerVersion 6.0 product components:
Find out what is new in Version 6.1 and
learn about new and changed function. These changes might affect how you want
to use your migrated components in the future.
Check the requirements for other products on which Version 6.1 components
might have dependencies. You can find details of prerequisite and other optional
products in both the Installation Guide and in the Installation reference
section.
If your installation includes a component on a 64-bit platform,
or you plan to move one or more components to a 64-bit platform, read the
advice provided in Considerations for 64-bit platforms.
Decide where you want to migrate the product components. Migrate
them to a different location on the same computer or to a second computer.
For example, you might want to migrate components to another location to maintain
availability during the migration.
The following topics describe
different migration scenarios:
Decide when you want to migrate the product components. You
might want to preserve some components at the Version 6.0 level
for now, and migrate them later.
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 need to migrate components in a particular order. A
typical order might be:
Install a Version 6.1 toolkit.
Create a Version 6.1 broker, or migrate
an existing broker to Version 6.1.
Migrate the Configuration Manager.
Migrate further brokers and toolkits.
Coexistence with previous versions and other products shows you how WebSphere Message Broker Version
6.1 can
coexist on the same computer with previous versions of the product, and how Version 6.1 components can operate with components
from previous versions.
Decide how you want to use your existing resources with WebSphere Message Broker Version
6.1.
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, XML Schema files, and broker archive files. You can start
using these resources with WebSphere Message Broker Version
6.1 immediately.
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 Version 6.0 level
that you backed up before you started the migration, and any post-migration
changes to these resources would be lost. Migrating your development and test
domains before migrating your production domain allows you to identify problems
like this and develop a strategy for dealing with further problems.
Optional: When you are ready to migrate, run the mqsimigratecomponents command
with the -c parameter. This form of the command
performs a pre-migration check against the Version 6.0 components
to ensure that they can be migrated. The pre-migration check identifies potential
problems and allows you to correct them before proceeding with migration.