Use the migration tools to migrate WebSphere Application Server product configurations.
If you use an earlier version of WebSphere Application Server, the system administrator might have fine-tuned various application and server settings for your environment. It is important to have a strategy for migrating these settings with maximum efficiency and minimal loss.
Before using the migration tools, consult the Version 6.0 release notes to understand what fixes you must apply to earlier versions. Applying fixes to an earlier version might also apply fixes to files that have a role in the migration. Apply any fixes to ensure the most effective migration of configurations and applications possible.
The migration tools in WebSphere Application Server Version 6.0.x support migration from WebSphere Application Server Version 4.0.x, Version 5.0.x, and Version 5.1.x.
IBM provides a set of migration tools for migrating administrative configurations from WebSphere Application Server Version 4.0.x, 5.0.x, or 5.1.x to the Version 6.0.x base product.
You can migrate your product configurations using the Migration wizard or the command-line migration tools.
You can perform incremental migration of Version 4.0.x or Version 5.x nodes by calling the migration tools multiple times, each time specifying a different configuration file. Various reasons exist for having multiple configuration files. Whatever the reason, migrating one configuration file at a time lets you test applications incrementally before continuing to the next configuration file.
The Migration wizard calls the WASPostUpgrade command. The WASPostUpgrade command uses the backupConfig command to save the existing Version 6.0.x configuration before performing migration. The results are stored in the profile_name/temp directory. You can use the restoreConfig command to restore the backup if required.
In this information ... | IBM Redbooks, demos, education, and more(Index) |