Migrating to a Version 9.0 stand-alone application server on a remote machine

Use the migration tools to migrate from a Version 7.0 or later to a Version 9.0 stand-alone application server on a remote machine.

Before you begin

Supported configurations 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
Read Overview of migration, coexistence, and interoperability and Migration considerations.

To ensure that your operating system is supported by WebSphere Application Server Version 9.0, visit the following site for the most current list of supported hardware and software: WebSphere Application Server system requirements.

Tip: Before migrating a WebSphere Application Server Version 7.0 or later stand-alone application server on a remote machine, 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. Make sure that you note the exact name and location of this backed-up configuration. For more information, see backupConfig command.

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.

For help in troubleshooting problems when migrating, see Troubleshooting migration.

About this task

Typically, you can use the WASPreUpgrade and the WASPostUpgrade migration tools to upgrade from Version 7.0 or later to Version 9.0 on the same machine. However, some scenarios require that you migrate the Version 7.0 or later configuration on one machine to Version 9.0 on a different machine. One of these scenarios is when you install new machines for your Version 9.0 environment but need to migrate your existing Version 7.0 or later configuration from other machines.

The WASPreUpgrade command saves the existing Version 7.0 or later configuration into a migration-specific backup directory. The WASPostUpgrade command uses this directory to add the old configuration settings to the new Version 9.0 environment.

For transitioning users For transitioning users: WebSphere Virtual Enterprise and Intelligent Management previously required separate migration tools but are now migrated as part of the standard migration procedures.trns

Procedure

  1. Install WebSphere Application Server Version 9.0 on the target machine. Install the same features as the earlier release if they are available. For more information, see Installing and configuring your application serving environment.
  2. Create the remote migration .jar file. This .jar file contains the files necessary to run the WASPreUpgrade command on a system which does not have WebSphere Application Server Version 9.0 installed.
    Avoid trouble Avoid trouble: You must create the remote migration .jar file on the same operating system and architecture as you installed the source. Because the archive that is generated contains operating system specific code, it only executes on this architecture.gotcha
    1. Identify the operating system and architecture of the source profile. If the operating system and architecture of the source profile is different from the operation system or the architecture of the target profile, then you must install WebSphere Application Server Version 9.0 on a system that matches the source profile before creating the remote migration jar. Once you have generated the remote migration jar, it will work on any system which matches the operating system and architecture.
    2. Create the remote migration .jar.
      1. In the command prompt, enter: cd $WAS_HOME/bin/migration/bin
      2. To create the .jar file, run: createRemoteMigrJar.bat(sh) -targetDir <dir_for_the_remote_migration_jar> . This creates the following file: WAS_V90_OS.arch_RemoteMigrSupport.jar. For example: WAS_V90_windows.amd64_RemoteMigrSupport.jar
    3. Prepare the remote system for the WASPreUpgrade command.
      1. Send the .jar file to the system where your source profile resides.
      2. Extract the file to a temporary location.
      3. Change directories to the bin directory in the temporary location.

      You are now ready to run the WASPreUpgrade command against the source profile. However, do not issue this command until you are told to do so in a later step.

  3. Save the current deployment manager configuration by running the WASPreUpgrade command on the source host. See the steps about saving and archiving the configuration data in Migrating cells across operating systems using the command-line tools.
  4. Copy the migration_specific_backup directory from the WebSphere Application Server Version 7.0 or later machine to the Version 9.0 machine.

    Use the ftp command, shared storage, or some other mechanism to copy the directory to the new machine.

  5. Use the Profile Management tool or the manageprofiles command to create a WebSphere Application Server Version 9.0 profile.

    For more information, see manageprofiles command.

  6. Add the WebSphere Application Server Version 7.0 or later configuration to the Version 9.0 configuration.

    Use the WASPostUpgrade command in the app_server_root/bin directory of the Version 9.0 installation to add the Version 7.0 or later configuration to the Version 9.0 configuration.

    [AIX][HP-UX][Linux][Solaris]
    ./WASPostUpgrade.sh /filepath/migration_specific_backup
    [Windows]
    WASPostUpgrade C:\filepath\migration_specific_backup

    See WASPostUpgrade command for more information.

    The WASPostUpgrade tool records information specific to each enterprise bean it deploys in the migration_specific_backup/WASPostUpgrade.log file.
  7. 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.

  8. Modify the configuration using the WebSphere Application Server Version 9.0 administrative console.
    1. Change user IDs and passwords to match security requirements.

      You might have to change user IDs and passwords if they are not identical to those in use on the Version 7.0 or later machine.

    2. Change other machine-specific information.

      The configuration might refer to other software products or configurations that do not exist on the new machine. For example, the old machine might have a database. Modify the data source to point to the database on the old machine.

Results

You have migrated WebSphere Application Server from Version 7.0 or later to a remote Version 9.0 machine.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 6, 2017 0:01
File name: tmig_to70sasr.html