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.
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 federated 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 disk space
requirements.
- The deployment manager that manages the managed node that you
intend to migrate has already been migrated to the newer version of WebSphere ESB, and
is running.
Note: Migrating a
WebSphere ESB version 6.0.x or 6.1.x managed
node to a
version 6.2 managed
node requires that you first migrate the
version 6.0.x or 6.1.x deployment
manager to a
version 6.2 deployment
manager. See
Migrating a deployment manager for instructions.
Complete the migration of the deployment manager before you proceed
with the instructions in this topic.
Make sure that you have completed the following tasks before
you start the migration process:
- Back up the databases that support version 6.0.x or 6.1.x WebSphere ESB components.
About this task
After you migrate an older version deployment
manager to a newer version of WebSphere ESB, the
newer version deployment manager runs in compatibility mode by default,
where it can manage both older and newer versions of WebSphere ESB. For
example, after migration, a version 6.2 deployment
manager can manage both version 6.1.x and version 6.2 nodes.
The managed nodes of the previous version 6.1.x deployment
manager are now running as version 6.1.x managed
nodes in the version 6.2 deployment
manager.
Over time, migrate each
version 6.1.x WebSphere ESB managed
node (server managed by a
version 6.2 deployment
manager) to a
version 6.2 managed
node.
After migrating all theversion 6.1.x managed
nodes, use the convertScriptCompatibility script
to change the deployment manager from supporting compatibility of version 6.1.x administration
scripts to supporting compatibility of only version 6.1.x and version 6.2 administration
scripts. See the
convertScriptCompatibility command.
Note: When
following the directions at this link to use the convertScriptCompatibility command,
use the WBIPostUpgrade command rather than the WASPostUpgrade command.
For
help in troubleshooting problems when migrating, see Troubleshooting version-to-version migration.
What to do next
Verify that the migration has been successful.