[AIX Solaris HP-UX Linux Windows]

Migrating to Version 8.5 deployment managers on remote machines

Use the migration tools to migrate from an earlier version of the application server to a Version 8.5 deployment manager on a remote machine.

Before you begin

Supported configurations Supported configurations:

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

sptcfg
Restriction: Remote migration on IBM® i is NOT supported.

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

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

To ensure that your operating system is supported by WebSphere Application Server Version 8.5, see WebSphere Application Server system requirements for the most current list of supported hardware and software.

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

Tip: Before migrating a WebSphere Application Server Version 6.1 deployment manager 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. For more information, see backupConfig command. Make sure that you note the exact name and location of this backed-up configuration.

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

Procedure

  1. Create the remote migration .jar file This .jar file contains the files necessary to run the WASPreUpgrade command on a system that does not have WebSphere Application Server installed.
    Avoid trouble Avoid trouble: The generated archive contains operating system specific code, and will only execute on the same architecture the archive was created on.gotcha
    1. Create the remote migration .jar file.
      1. In the command prompt, run the following command:
        cd <app_install_root>/bin/migration/bin 
        For more information about directory conventions, see Directory conventions
      2. To create the .jar file, run the following command:
        createRemoteMigrJar.bat(sh) -targetDir <dir for the remote migration jar> 
        This creates a file with the following name structure: WAS_V8_OS.arch_RemoteMigrSupport.zip. For example: WAS_V8_windows.x86_RemoteMigrSupport.zip
    2. 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 to the bin directory in the temporary location.
      4. Run the WASPreUpgrade command against the source profile to be migrated using the -machineChange true parameter. For more information, see WASPreUpgrade command.
  2. Save the current configuration using the WASPreUpgrade script from the path_to_remote_migration_jar/bin/migration/bin directory.

    Read WASPreUpgrade command for more information.

    Specify -machineChange true when you run the WASPreUpgrade command. Save the configuration in the migration_specific_backup directory on the Version 6.1 machine.

    [Linux]
    ./WASPreUpgrade.sh /filepath/migration_specific_backup /opt/WebSphere/AppServer -machineChange true
    [Windows]
    WASPreUpgrade C:\filepath\migration_specific_backup C:\Program Files\WebSphere\AppServer -machineChange true
    The WASPreUpgrade command provides status to the screen and to log files in the migration_specific_backup directory. ASCII log file names start with the text WASPreUpgrade and include a date and timestamp.
  3. Copy the migration_specific_backup directory from the machine with the earlier version of the application server to the Version 8.5 machine.

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

  4. Install WebSphere Application Server Version 8.5 on the new machine. Install the same features as the earlier release.

    For more information, see How do I install an application serving environment?.

  5. Use the Profile Management Tool graphical user interface (GUI) for WebSphere Application Server Version 8.5. For more information, see Managing profiles using the graphical user interface.

    The Version 8.5 deployment manager profile must have the same cell name as the profile from the earlier version that is being migrated.

  6. Add the WebSphere Application Server Version 6.1 configuration to the Version 8.5 configuration. See WASPostUpgrade command for more information.

    Specify -keepDmgrEnabled true when you run the WASPostUpgrade command in a remote deployment-manager migration. If you fail to do so, the WASPostUpgrade command will fail when it is unable to locate the earlier installation of the application server on the same machine as the Version 8.5 installation.

    Use the WASPostUpgrade command in the app_server_root/bin directory of the Version 8.5 installation to add the earlier configuration to the Version 8.5 configuration.

    [Linux]
    ./WASPostUpgrade.sh /filepath/migration_specific_backup 
    -keepDmgrEnabled true

    [Windows]
    WASPostUpgrade C:\filepath\migration_specific_backup
    -keepDmgrEnabled true
    The WASPostUpgrade command records information specific to each enterprise bean it deploys in the migration_specific_backup/WASPostUpgrade.log file.
  7. Modify the configuration using the WebSphere Application Server Version 8.5 administrative console.
    1. Change user IDs and passwords to match security requirements.

      If you make any changes to the security configuration, you must then resynchronize all federated nodes in the configuration. If you fail to do so, the nodes will not be able to communicate with the deployment manager and migration will not be able to upgrade the federated nodes.

      You might have to change user IDs and passwords if they are not identical to those in use on the machine with the earlier version of application server installed.

    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.

  8. Use the syncNode command to manually synchronize all federated nodes with the migrated deployment manager.

    If you fail to do so, the nodes will not be able to communicate with the deployment manager and migration will not be able to upgrade the federated nodes.

Results

You have migrated WebSphere Application Server from an earlier version of the application server to a remote Version 8.5 machine.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 10:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=tmig_to70ndr
File name: tmig_to70ndr.html