Before you begin
Note: When you migrate using the command-line
tools, you can migrate either a WebSphere ESB profile
or a WebSphere Application Server profile.
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.
- If you are migrating on the same physical computer system on which
the older version of WebSphere ESB resides,
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 a
version 6.0.2.x 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.0.2.x and
version 6.2 nodes.
In other words,
version 6.0.2.x managed
nodes can run with the
version 6.2 deployment
manager. Over time, you can migrate each
version 6.0.2.x WebSphere ESB managed
node (server managed by a
version 6.2 deployment
manager) to a
version 6.2 managed
node. After migrating all
version 6.0.2.x managed
nodes, you use the
convertScriptCompatibility script
to convert their configurations from a mode that supports compatibility
of
version 6.0.2.x administration
scripts to a mode that is fully in a configuration
version 6.2 model.
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.
What to do next
Complete the cluster migration by completing
steps 6-9 in
Migrating a cluster or steps
7-12 in
Migrating a cluster with minimal down time.