What is new for migration
WebSphere® Application Server Version 9.0 introduces several key enhancements to the migration tools.
- Rather than specifying individual parameters on migration commands such as WASPreUpgrade and WASPostUpgrade, you can specify the -properties file_name.properties parameter to input a properties file. The properties file contains the following properties:
A template migration.properties file is located in the app_server_root/properties directory. The template contains instructions and examples for defining properties. After you copy the file to a new location, modify the file to suit your migration. You can use the same file for all profile and migration types because any properties that do not apply are ignored.
For more information about using the properties file, see Defining your migration through properties.
The WASPostUpgrade -replacePorts and -portBlock parameters were replaced by the -setPorts and -resolvePortConflicts parameters respectively. These new parameters provide better clarity and flexibility to how the migration tools assign port values in the new configuration.
With the -setPorts parameter, you can choose from the following options:With the -resolvePortConflicts parameter, you can choose to resolve port conflicts by incrementing from the conflicting value or from a value that you specify.
The default port value for any new endpoint address is retrieved from a profile template and is checked for conflicts.
For more information, see WASPostUpgrade command.
- In previous versions, the source instance or profile root directory was specified when you ran
the WASPreUpgrade command. In Version 9.0, you can now specify the installation
root directory as the currentWebSphereDirectory and specify the profile name on
the -oldProfile parameter. This change makes migrating on the IBM i operating
system more consistent with other platforms.
For more information, see WASPreUpgrade command.
You can use the WASMigrationAppInstaller command to migrate applications from your previous release into the new release. The tool is intended to replace the install_all_apps.jy script.
The WASPostUpgrade command also attempts to migrate your applications to the new release. If the only problems that occur when you run the WASPostUpgrade command were with installing applications, run the WASMigrationAppInstaller command instead of rerunning the WASPostUpgrade command.
The tool installs only applications that are not already installed, so you can run the tool as many times as needed.
For more information, see WASMigrationAppInstaller command.
Changes in the Version 9.0 release include many deprecated, stabilized, or removed features, as well as some change in default value and behavior. These changes might affect your WebSphere Application Server environment and require modifications.
For a list of these changes, see What has changed in WebSphere Application Server.