Before you begin
Note: The migration wizard cannot run in a non-graphical
environment. Examples of non-graphical environments include the i5/OS® platform or telnet sessions.
If you want to run migration in a non-graphical environment, use the WBIPreUpgrade and WBIPostUpgrade commands.
Note: The migration wizard supports only WebSphere ESB profiles.
If you have WebSphere Application Server profiles,
you must use the migration commands.
Note: Migrate the
WebSphere ESB version 6.0.x or 6.1.x deployment
manager to
version 6.2 before
migrating the managed nodes that comprise the cell. The deployment
manager must always be at the highest release and fix level within
a cell in order for it to manage all nodes in the cell.
A version 6.2 deployment
manager can manage version 6.1.x and version 6.2 managed
nodes. For migrations from version 6.1.x,
this allows a cell to be upgraded to a new release one node at a time,
with minimal impact to the applications that are running within the
cell. For migrations from version 6.0.2.x,
to keep the cell running with minimal down time, you must migrate
to version 6.2 in
two stages: first from version 6.0.2.x to version 6.1.x,
and then from version 6.1.x to version 6.2. Alternatively
you can shut down the entire cell and migrate in a single step, directly
from version 6.0.2.x to version 6.2. Members
of a cluster cannot be running different versions (6.0.2.x, 6.1.x,
6.2) of WebSphere ESB.
If you have configured a cluster containing servers running different
versions, all the members running earlier versions of WebSphere ESB must
be stopped before you start the first version 6.2 cluster member.
Also, once you start a version 6.2 cluster member, do not start any version 6.1.x or 6.0.2.x cluster
members in that cluster.
Restrictions exist on using mixed-release
cells. For more information see "Restriction on using mixed-release cells"
in the WebSphere Process
Server information center.
Make sure that the
following conditions are met before you start the migration process:
- Your system meets all the hardware and software requirements for
the new version of WebSphere ESB.
- You have installed the new version of WebSphere ESB side-by-side
the previous version on the same system.
- A deployment manager profile, created with the older WebSphere ESB version,
resides on the same system.
- Sufficient disk space is available for the migrated profile and
its backup. See Premigration considerations for WebSphere ESB for details
about disk space requirements.
Make sure that you have completed the following tasks before
you start the migration process:
- Back up the databases that support version 6.0.2.x or version 6.1.x WebSphere ESB components.
What to do next
Verify that the migration has been successful.