Migration support consists of tools that are included with WebSphere® Application Server. These tools primarily provide support for saving
the configuration and applications from a previous version of the product into a migration-specific
backup directory and then importing that configuration into the latest version of the application
server.
Supported configurations:
This topic is about profile configuration migration. To migrate your applications
to the latest version, use the WebSphere Application
Server Migration Toolkit.
Read Overview of migration, coexistence, and interoperability and Migration considerations. For resources to help
you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.
Important: Use the migration tools for the version of WebSphere Application Server that you are installing. The tools change over time.
If you use migration tools from an earlier release of WebSphere Application Server, you are likely to encounter a problem with the
migration.
The migration scripts are located in the
app_server_root/bin directory after installation.
You can use the WASPreUpgrade command to store the
configuration of an existing release before you migrate to the Version 9.0 product.
Select the appropriate migration tools to migrate your product configurations.
- Migration wizard
- You use the Migration wizard to migrate an earlier supported version of WebSphere Application Server to Version 9.0.
The wizard is the graphical interface to the primary Version 9.0 migration tools, the WASPreUpgrade
and the WASPostUpgrade commands.
The Migration wizard cannot run in a
non-graphical environment. Examples of non-graphical environments include telnet sessions. If you
want to run migration in a non-graphical environment, use the WASPreUpgrade and
WASPostUpgrade commands.
- Migration properties file
- Rather than specifying individual parameters on migration commands, you can specify the
-properties file_name.properties parameter to input a properties
file that contains properties that define your migration. By defining your migration settings in a
properties file, you can make your migration process easily repeatable.A template
migration.properties file is located in the
app_server_root/properties directory. The template contains
instructions and examples for defining properties. For more information, see Defining your migration through properties.
- WASPreUpgrade command
- You use the WASPreUpgrade command to save the applications and configuration
data from a previous installation of WebSphere Application Server to a backup
directory.
The WASPostUpgrade command restores the configuration data from the
directory to the new installation.
The Migration wizard calls the WASPreUpgrade command during
migration. You can also use the command to perform a manual migration after installing the new
version.
Read WASPreUpgrade command for more information.
- WASPostUpgrade command
- You use the WASPostUpgrade command to restore the configuration data from a
previous release.
The WASPostUpgrade command reads the data from the backup
directory where the WASPreUpgrade command stored the data.
The Migration wizard calls the WASPostUpgrade command during
migration. You can also use the command to perform a manual migration after installing the new
version.
Read WASPostUpgrade command for more information.
- WASMigrationAppInstaller command
- You use the WASMigrationAppInstaller command to migrate applications from
your previous release into the new release.
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 only installs
applications that are not already installed, so you can run the tool as many times as
needed.
Read WASMigrationAppInstaller command for more information.
- createRemoteMigrJar command
- For remote migrations, you can use the createRemoteMigrJar command to create
a .jar file that enables you to run the WASPreUpgrade command on a system that
does not have WebSphere Application Server installed. The resulting
WAS_ver_OS.arch_RemoteMigrSupport.jar
file collects files from the target installation, including files to run the
WASPreUpgrade command and Java™.
Avoid trouble: Because the command collects files and information from the
target installation, the JAR file can only be used if the operating systems and architectures on the
source and target installations are the same. If either of these differ, you must install WebSphere Application Server on the source machine.
For more
information, see createRemoteMigrJar command.
- convertSelfSignedCertificatesToChained task
- Chained certificates are the default certificate type in WebSphere Application Server
Version 9.0. Administrators can use the
convertSelfSignedCertificatesToChained task with the wsadmin
tool to convert self-signed certificates to chained certificates.
Read the
SSLMigrationCommands command group for the AdminTask object article for more
information.
What to do next
Use the selected tools to migrate your product configuration.