Use the migration tools to migrate from a WebSphere® Application Server
Version 7.0 or later stand-alone application server profile to a Version 9.0 stand-alone application server.
Before you begin
Supported configurations: This article is about profile configuration migration. To
migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit. For more information, see the Migration
Toolkit on WASdev.
sptcfg
See Overview of migration, coexistence, and interoperability and Migration considerations.
Tip: Before migrating a WebSphere Application Server
Version 7.0 or later stand-alone application server, use the
backupConfig command or your own preferred backup utility to back up your
existing configuration if you want to be able to restore it to its previous state after migration.
For more information, see backupConfig command. Make sure that you note the exact name
and location of this backed-up configuration.
Rather than specifying individual parameters on migration commands, you can specify the
-properties file_name.properties parameter to input a properties
file. For more information, see Defining your migration through properties.
About this task
If you want to migrate a WebSphere Application Server
Version 7.0 or later configuration on one machine to Version 9.0 on another machine, use the alternate procedure
described in Migrating to a Version 9.0 stand-alone application server on a remote machine.
For transitioning users: The following products previously required separate migration tools but are
now migrated as part of the standard migration procedures:
- WebSphere Extended Deployment Compute Grid or
Feature Pack for Modern Batch
- WebSphere Virtual Enterprise or
Intelligent Management
For more information about these changes, see
What is new for migration.
trns
For help, read Troubleshooting migration.
Procedure
- Stop all of the WebSphere Application Server
Version 7.0 or later application servers that are running on the
node.
Use the stopServer command from the
app_server_root/bin directory. See stopServer
command for more information.
![[Linux]](../images/linux.gif)
For example, issue the following commands to stop server1 and server2 on the Linux operating
system:
./stopServer.sh server1
./stopServer.sh server2
If security is enabled, specify the -user and -password
parameters on the stopServer command.
You can migrate a WebSphere Application Server
Version 7.0 or later node without stopping it; however, you must stop
the node before you can start the Version 9.0 node that you are
installing. It is not necessary to have the node running to migrate its configuration. The migration
tools can retrieve all the configuration data while the node is stopped.
- Install WebSphere Application Server
Version 9.0.
See Installing and configuring your application serving environment
for more information.
- Create a WebSphere Application Server
Version 9.0 profile by using the Profile Management Tool or the
manageprofiles command.
See Managing profiles using the graphical user interface or manageprofiles
command for more information.
- Save the configuration for your source installation by running the
WASPreUpgrade command, specifying the migration backup directory name and the Version 7.0 or later installation root directory.
/opt/WebSphereV90/bin/WASPreUpgrade.sh /mybackup/v70toV90server1 /opt/WebSphereV70
-oldProfile current70Server
For more information and additional parameters, see WASPreUpgrade command.
The
WASPreUpgrade tool saves from the following directories to the specified directory.
- bin
- config
- installableApps
- installedApps (or an alternate directory specified by the user)
- properties
- Restore the configuration from your source environment to the Version 9.0 profile by running the
WASPostUpgrade command, specifying the migration backup directory.
/opt/WebSphereV90/bin/WASPostUpgrade.sh /mybackup/v70toV90server1
-oldProfile current70Server -profileName 90ProfileName -resolvePortConflicts incrementCurrent
-backupConfig TRUE -username myuser -password mypass
For more information and additional parameters, see WASPostUpgrade command.
The WASPostUpgrade tool copies the environment in the backup directory to the
WebSphere Application Server
Version 9.0 stand-alone application server installation.
Note: When migrating a stand-alone application server from Version 7.0 or later to Version 9.0,
you can choose a stand-alone application server node that is already registered with an
administrative agent as the target of the migration.
- Verify that your configuration and applications were migrated correctly.
If the configuration was migrated correctly but any applications were not installed, you can run
the WASMigrationAppInstaller command to install only the applications that were
not migrated. For more information, see WASMigrationAppInstaller command.
For Compute Grid or Feature Pack for Modern Batch applications, also verify that the job
scheduler was migrated correctly and that you can dispatch jobs to the servers that host your batch
applications.
To verify the job scheduler migration, restart the application server where the job scheduler is
configured. After the server restarts, access the job management console through a web browser.
To verify that the servers that host your batch applications work correctly:
- Verify that the batch applications on the migrated server are started. Examine the server logs
for any errors.
- Verify that you can dispatch batch jobs to the migrated server by submitting a job from the
migrated job scheduler server. You can submit the job by using the Job Management Console, the
WSGrid utility, the EJB interface, or the web services interface.