WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate WAS ND configurations

Migrate to v8.0 dmgrs on remote machines

Use the migration tools to migrate from v6.x to a v8.0 dmgr on a remote machine.

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

The WASPreUpgrade command saves the existing v6.x configuration into a migration-specific backup directory. The WASPostUpgrade command uses this directory to add the old configuration settings to the new v8.0 environment.

Procedure

1. Verify WAS system requirements. If your OS is not supported for migration to v8.0, read Migrate dmgrs from unsupported operating systems.

2. Run backupConfig on old system.

3. 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.

4. Save the current configuration using the WASPreUpgrade script from the migration/bin directory of the WAS v8.0 utilities disk, which mount on the v6.x machine.

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

   ./WASPreUpgrade.sh /filepath/migration_specific_backup /opt/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.

5. Copy the migration_specific_backup directory from the WAS Version 6.x machine to the v8.0 machine.

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

6. Install WAS v8.0 on the new machine.

   Install the same features as the earlier release.

7. Use the Profile Management Tool or the manageprofiles command to create a WAS v8.0 profile.

   The v8.0 dmgr profile must have the same cell name as the v6.x profile that is being migrated.

8. Add the WAS Version 6.x configuration to the v8.0 configuration.

   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 v6.x installation on the same machine as the v8.0 installation.

   Use the WASPostUpgrade command in...

   WAS_HOME/bin

   of the v8.0 installation to add the v6.x configuration to the v8.0 configuration.
   ./WASPostUpgrade.sh /filepath/migration_specific_backup -keepDmgrEnabled true

   The WASPostUpgrade tool records information specific to each enterprise bean it deploys in the migration_specific_backup/WASPostUpgrade.log file.

9. Modify the configuration using the WAS v8.0 administrative console.
   1. Change user IDs and passwords to match security requirements.

      If you make any changes to the security configuration, then resynchronize all federated nodes in the configuration. If you fail to do so, the nodes will not be able to communicate with the dmgr 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 v6.x 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.

10. Use the syncNode command to manually synchronize all federated nodes with the migrated dmgr.

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

Results

You have migrated WAS from v6.x to a remote v8.0 machine.

Related

Migrate product configurations
Migrate product configurations with migration tools
Troubleshoot migration.
WASPreUpgrade command
WASPostUpgrade command
syncNode command

+

Search Tips   |   Advanced Search