If you experience a problem performing a migration
upgrade, you may need to correct the problem and completely redo the
migration upgrade to complete the migration process.
To prevent error messages resulting from the previous upgrade, follow
these steps.
- Uninstall any EAR files that were been installed by the Migration
upgrade.
- Manually delete the corresponding file from the
installableApps directory.
- Remove any application servers that had been created (do not remove
the Default Server).
- Remove any data sources and JDBC drivers. Do not remove the Sample DB
Driver or Admin DB driver and configured data sources.
- Remove any virtual hosts if created and any virtual host aliases that
were added.
- Cleanup the backup directory. To clean up the backup directory, first
make a backup copy of the directory, then delete everything in the
directory except the following:
Do not delete these directories:
websphere_3x_backup.programFiles
websphere_3x_backup.userFiles
Do not delete these files:
websphere_3x_backup.xml
WASPreUpgrade trace and log files
- Ensure that the AdminServer is started, then, execute the
WASPostUpgrade script. Refer to the WebSphere Application Server
InfoCenter for WASPostUpgrade script syntax:
http://www-4.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/
As an alternative to cleaning up your WebSphere environment you can
uninstall and reinstallWebSphere, as follows:
- Ensure that you have backed up your migration backup directory.
- Clean up the backup directory as described above.
- Uninstall WebSphere 4.X.
- Delete the WebSphere 4.X directories.
- Drop and create the WebSphere Repository DB.
- Install WebSphere 4.X.
- Upgrade to the latest Fix Pack. This is optional but highly
recommended.
- Start the WebSphere AdminServer.
- Verify that you have a good install.
- Execute the WASPostUpgrade script.
Refer to Recommended
fixes for WebSphere Application Server for more information. |