WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate stand-alone application servers


Migrate stand-alone application servers from unsupported operating systems

Use the migration tools to migrate an earlier WAS v6.x stand-alone application server that is running on an operating system that v8.0 does not support.

Supported configurations:

This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

Tip: Before migrating from WAS v6.x, 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. Read the "backupConfig command" article in the information center for more information. Make sure that you note the exact name and location of this backed-up configuration.

For help, read Troubleshoot migration.


Procedure

  1. Obtain the WAS v8.0 utilities disk.

    This disk contains the migration/bin directory. This directory contains a special environment that you can use to run the WASPreUpgrade command without installing v8.0.

  2. Save the current configuration using the WASPreUpgrade script from the migration/bin directory of the WAS v8.0 utilities disk.

    Read WASPreUpgrade command for more information.

    Save the configuration in the migration_specific_backup directory. If the WASPreUpgrade command fails because the Java Development Kit (JDK) on the v8.0 utilities disk is not supported on the operating system that you are attempting to migrate, perform the following actions:

    1. Create a migration directory on your local system.

    2. Install an IBM certified JDK that is at the highest level that will run on your operating system.

      Your JDK must be version 1.6 or later if you want to use the migration tools.

      The JDK directory should be in the same directory as the migration directory that you created on your local system in the last step, or you should have a working symlink that allows Java to be invoked from that path. 

      <directory>   - migration directory   - JDK/jre.pak/repository/package.java.jre/java/jre/bin/java
    3. Copy the WASPreUpgrade.bat (or WASPreUpgrade.sh) and the setupCmdLine.bat (or setupCmdLine.sh) files from the migration/bin directory of the WAS v8.0 utilities disk to the migration directory that you created on your local system.
    4. Edit the setupCmdLine.bat or setupCmdLine.sh file in your new migration directory.

      • Change WAS_HOME to point to the fully qualified path to the migration directory that you created
      • Change JAVA_HOME to point to the fully qualified path to your IBM Developer Kit or Java directory.

    5. Ensure that the executable bit is on for the setupCmdLine.sh and WASPreUpgrade.sh files in the migration directory that you created.
    6. Run the command from the migration directory that you created.

      Identify the backup directory and the location of the configuration files. 

      migration_directory\WASPreUpgrade migration_specific_backup_directory
file_path\WebSphere\AppServer node_name

  3. Shut down the WAS v6.x release by stopping all server nodes in the configuration.
  4. Tar or zip the migration_specific_backup directory, and FTP it to another system.

  5. Install the new operating system, keeping the same host name.

    If possible, keep the system name and passwords the same as on the old system. Place any database files related to applications that you are migrating in the same path as on the previous system. In general, try to keep paths the same. If you do change paths and names, refer to Migrate to a v8.0 stand-alone application server on a remote machine. Make any changes before running the WASPostUpgrade command as described in a later step.

  6. FTP the migration_specific_backup directory from the other system, and extract it.

  7. Install WAS v8.0.

    Read the "Installing the product and additional software" article in the information center for more information.

  8. Use the Profile Management tool or the manageprofiles command to create a WAS v8.0 profile.

    Read the "Creating profiles using the graphical user interface" article or the "manageprofiles command" article in the information center for more information.

  9. Run the WASPostUpgrade command from the v8.0 WAS_HOME/bin directory.

    Specify the migration_specific_backup directory that you extracted in an earlier step.

    Read WASPostUpgrade command for the proper command syntax.


Configuration mapping during product-configuration migration
Migrate product configurations
Migrate product configurations with migration tools

+

Search Tips   |   Advanced Search