You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere® Application Server
Version 7.0 federated node to the state that it was in before migration.
For each federated node that you want to roll back, you must roll
back the federated node itself and the corresponding changes made
to the primary repository located on the deployment manager.
Before you begin
Best practice: When migrating
a Version 5.1.x or Version 6.x federated 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.
- Run the backupConfig command or your own preferred
utility to back up the Version 7.0 deployment manager configuration.
Important: Make sure that you note the exact name and location
of this backed-up configuration.
Read the "backupConfig command"
article in the information center for more information.
- Run the backupConfig command or your own preferred
utility to back up the Version 5.1.x or Version 6.x federated node
configuration.
Important: Make sure that you note the exact
name and location of this backed-up configuration.
Read the
"backupConfig command" article in the information center for more
information.
- Migrate the federated node.
- If necessary, you can now roll back the federated node that you
just migrated.
Important: If you do not have a backup copy
of your Version 7.0 deployment manager configuration as it was before
you migrated the Version 5.1.x or Version 6.x federated 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 WebSphere Application Server, Network Deployment cell.
About this task
You must perform all of the backup and rollback actions
for each migrated federated node before you proceed to migrate another
federated node.
Procedure
- Run the backupConfig command or your
own preferred utility to back up the Version 7.0 deployment manager
configuration at the current state.
Important: Make
sure that you note the exact name and location of this backed-up configuration.
Read
the "backupConfig command" article in the information center for more
information.
- Stop all servers and the node agent on the Version 7.0
federated node that you want to roll back.
- Restore your previous configuration.
- Run the restoreConfig command or
your own preferred utility to restore the previous Version 7.0 deployment
manager configuration.
Important:
- Make sure that you restore the same backed-up configuration that
you created just before you migrated the federated node.
- If you have made changes to your environment (application or configuration
changes for example), these changes are rolled back at the same time
and cause the other nodes to force synchronization with the deployment
manager.
Read the "restoreConfig command" article in the information
center for more information.
- Perform one of the following actions to restore the
Version 5.1.x or Version 6.x configuration for the federated node.
- Run the restoreConfig command or your own preferred
utility to restore the Version 5.1.x or Version 6.x configuration.
Important: Make sure that you restore the same backed-up configuration
that you created just before you migrated this federated node.
Read
the "restoreConfig command" article in the information center for
more information.
- Use the wsadmin command to run
the migrationDisablementReversal.jacl script
from the Version 5.1.x or Version 6.x WAS_HOME/bin directory
of the federated node that you need to roll back from Version 7.0.
Use
the following parameters:
./wsadmin.sh -f migrationDisablementReversal.jacl -conntype NONE
Tip: If you have trouble running the
migrationDisablementReversal.jacl script,
try to manually perform the steps in the script.
- Go to the following directory:
profile_root/config/cells/cell_name/nodes/node_name
where node_name is the name of the federated
node that you want to roll back.
- If you see a serverindex.xml_disabled file
in this directory, perform the following actions:
- Delete or rename the serverindex.xml file.
- Rename the serverindex.xml_disabled file
to serverindex.xml.
- Start the Version 7.0 deployment manager.
- Perform any application maintenance that is required.
- Synchronize the Version 5.1.x or Version 6.x federated
node with the deployment manager.
Read the "Synchronizing
nodes with the wsadmin tool" article in the information center for
more information.
- If you chose to keep the installed applications in the
same location as the prior release during migration to Version 7.0
and any of the Version 7.0 applications are not compatible with the
prior release, install applications that are compatible.
- Start the rolled-back Version 5.1.x or Version 6.x federated
node and servers.
- Validate that the configuration is satisfactory.
This
is the last chance to undo the rollback action by restoring the deployment-manager
configuration that you backed up in the first step.
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.