You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere Application Server Version 6.1 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
Best practice: When migrating a Version
5.x or 6.0.x managed node, the best practice is to perform the following
actions if you want to be able to roll it back to its previous state after
migration:
- Back up your existing configuration using the backupConfig command
or your own preferred backup utility.
- 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.1 deployment manager configuration as it was before you
migrated the Version 5.x or 6.0.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 migrate another managed node.
Procedure
- Stop all of the servers that are currently running in the Version
6.1 environment.
- Restore your previous configuration.
- Run the restoreConfig command or your
own preferred utility to restore the Version 6.1 deployment manager configuration.
Important: Make sure that you restore the same backed-up
configuration that you created just before you migrated the managed node.
- Perform one of the following actions to restore the Version
5.x or 6.0.x configuration for the managed node.
- Start the Version 6.1 deployment manager.
- Synchronize the managed node.
- If you chose to keep the installed applications in the same location
as the prior release during migration to Version 6.1 and any of the Version
6.1 applications are not compatible with the prior release, install applications
that are compatible.
Delete the Version 6.1 managed profile.
- Start the rolled-back managed node in the Version 6.1 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.