Use the Migration wizard to migrate from a WebSphere® Application Server Version 5.1.x or Version 6.x federated application server.
Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.
Read the "backupConfig command" article in the information center for more information.
Read the "backupConfig command" article in the information center for more information.
Read Rolling back a federated node for more information.
The Migration wizard was introduced in WebSphere Application Server Version 6.0. The wizard is the graphical interface to the primary Version 7.0 command-line migration tools, which are the WASPreUpgrade command and the WASPostUpgrade command.
For help in troubleshooting problems when migrating, see Troubleshooting migration.
Read WASPreUpgrade command and WASPostUpgrade command for descriptions of the parameters related to the information that you need to collect.
You can first use the Profile Management tool or the manageprofiles command to create a valid new target Version 7.0 application server profile if one does not already exist, or you can create a target profile later using the Migration wizard. Read the "Creating profiles using the graphical user interface" article in the information center for more information.
For migration to be successful, you must use the same node names and cell names for each node that you migrate from Version 5.1.x or Version 6.x to Version 7.0.
Select the check box and enter the location of the previous installation if it does not display in the selection list.
Select the check box to create a backup copy of the target profile's configuration before migrating the source profile. If you select the check box, the backup copy of the target profile will be written to profile_root/temp/MigrationBackup.time_stamp.zip. You can use the restoreConfig command to restore the configuration after migration if necessary.
The directory is created if it does not already exist. If the directory exists, it should be empty because the backup operation might overwrite existing backup files.
Scripts that can be used to install these applications are generated and saved in the migration backup directory. You can then run these files at any point and in any combination after the migration. You can also reorganize and combine these files for better applications installation efficiency if you want.
By default, a port conflict is resolved by incrementing the port number by one until an unused port number is found. Instead, you can specify a starting port number to be used when a conflict is detected. If the starting port number is in use, it will be incremented by one until an unused port number is found.
Select this option in order to minimize impacts to existing administration scripts. If you have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the Version 5.1.x or Version 6.x configuration definitions, for example, you might want to select this option during migration.
Read convertScriptCompatibility command for more information.
This panel displays only if you are migrating from Version 6.1.x.
This panel only displays if security is enabled and if the server user identity is not stored in the repository.
This panel displays only if you selected the option to create a new target profile.
If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.
If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.
If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.
If the process is not successful, the wizard displays a failure panel. If the migration is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.
Read the "Lightweight Third Party Authentication" article in the information center for more information.
If Version 7.0 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.
Read the "Java virtual machine settings" article in the information center for more information.
If you have used a smaller heap size in the past, you can use the default heap size of 50.
For example, you can configure WebSphere Application Server to use DB2®.
Read Migrating IBM Cloudscape or Apache Derby databases for more information.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |