You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere® ESB version 6.2 managed
node to the state that it was in before migration. For each managed
node that you want to roll back, you must roll back the managed node
itself and the corresponding changes made to the master repository
located on the deployment manager.
Before you begin
When you migrate a
version 6.0.x or 6.1.x managed
node, you must complete the following if you want to be able to roll
it back to its previous state after migration:
- Back up the databases that support WebSphere ESB components.
- Back up your existing configuration using the backupConfig command
or your own preferred backup utility.
- Run the backupConfig command or your
own preferred utility to back up the version 6.0.x or 6.1.x deployment
manager configuration..
Important: Make sure that you note
the exact name and location of this backed-up configuration.
See
the backupConfig command in
the WebSphere Application Server information
center.
- Run the backupConfig command or your
own preferred utility to back up the version 6.0.x or 6.1.x managed
node configuration.
Important: Make sure that you note
the exact name and location of this backed-up configuration.
See
the backupConfig command in
the WebSphere Application Server information
center.
- Migrate the managed node.
If necessary, you can now roll back the managed node that
you just migrated.
Important: If you do not have a
backup copy of your
version 6.2 deployment
manager configuration as it was before you migrated the
version 6.0.x or 6.1.x managed
node that you want to roll back, you cannot use the procedure described
in this article and you must roll back your whole cell as described
in
Rolling back a deployment cell.
About this task
You must perform all of the backup and rollback actions
for each migrated managed node before you proceed to roll back another
managed node.
Procedure
- Roll back your databases. (For
any databases that support WebSphere ESB components
that were upgraded, either automatically with the migration tools
or manually, restore the backups that you made before you started
the migration process.)
- Stop all of the servers that are currently running in the version 6.2 environment.
- Restore your previous configuration.
- Run the restoreConfig command
or your own preferred utility to restore the version 6.2 deployment
manager configuration.
Important: Make sure
that you restore the same backed-up configuration that you created
just before you migrated the managed node.
See the restoreConfig command in the WebSphere Application Server Information
Center.
- Perform one of the following actions to restore the version 6.0.x or 6.1.x configuration
for the managed node.
- Start the version 6.2 deployment
manager.
- Synchronize the managed node.
See Synchronizing nodes with the wsadmin tool in
the WebSphere Application Server information
center.
- If you chose to keep the installed applications in the
same location as the prior release during migration to version 6.2 and any
of the version 6.2 applications
are not compatible with the prior release, install applications that
are compatible.
- Start the rolled-back managed node in the version 6.2 environment.
Results
The configuration should now be returned to the state that
it was in before migration.
What to do next
You can now restart the migration process if you want to
do so.