You can use the restoreConfig and wsadmin commands
to roll back a migrated WebSphere® Application Server
Version 7.0 standalone application server to the state that it was
in before migration.
Before you begin
Best practice: When migrating
a Version 5.1.x or Version 6.x standalone application server, 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:
- Run the backupConfig command or your own preferred
utility to back up the Version 5.1.x or Version 6.x standalone application
server 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 standalone application server.
- If necessary, you can now roll back the standalone application
server that you just migrated.
Procedure
- Stop all of the servers that are currently running in the
Version 7.0 environment.
- Perform one of the following actions to restore the Version
5.1.x or Version 6.x configuration for the standalone application
server.
- 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 standalone application
server.
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 profile_root/bin directory
of the standalone application server.
Use the following parameters:
app_server_root/bin/wsadmin -instance instance -conntype NONE
-f profile_root/bin/migrationDisablementReversal.jacl
- 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.
- Delete the Version 7.0 profile
for the standalone application server.
Read the "Deleting
a profile" article in the information center for more information.
- Start the rolled-back standalone application server in
the Version 7.0 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.