Save the current deployment manager configuration to the migration backup directory

Before you begin

Create the target deployment manager profile

About this task

Step 5 towards the goal: Migrating cell configurations to new host machines using the command-line tool

To save the current deployment manager configuration to the migration backup directory, run the WASPreUpgrade command. The WASPreUpgrade command does not change the old configuration.

Procedure

  1. Run the WASPreUpgrade command with the -machineChange true parameter to save the current deployment manager configuration to a migration backup directory. For example:
    [Windows]
    <path to remote migration jar>\migration\bin\WASPreUpgrade.bat \mybackup_old_host\v70tov85dmgr01 
    \opt\WebSphereV70 -oldProfile 70dmgr01 -machineChange true
    [AIX][HP-UX][Linux][Solaris]
    <path to remote migration jar>/migration/bin/WASPreUpgrade.sh /mybackup_old_host/v70tov85dmgr01 
    /opt/WebSphereV70 -oldProfile 70dmgr01 -machineChange true
    where mybackup_old_host is the directory to which the profile configuration files are copied in preparation for the migration to the new host.

    If you are migrating from Version 8.0 to Version 8.5 and your profile is a deployment manager, Version 8.0 profile is stopped when WASPreUpgrade runs. The deployment manager is only started before WASPreUpgrade completes if you provide -keepDmgrEnabled true on the command line or specify the corresponding option in the Migration wizard.

    Avoid trouble Avoid trouble: If you specify -machineChange true, you must update the job manager URL for all resources (such as other deployment managers or application servers) that are managed by the job manager function of the Version 8.0 deployment manager after the migration. gotcha
  2. Review warnings or errors in the console output and WASPreUpgrade logs. After the WASPreUpgrade command is complete, check the console output for Failed with errors or Completed with warnings messages. Then, check the following log files for any warnings or errors:
    • mybackup_old_host/v70tov85dmgr01/logs/WASPreMigrationSummary.log
    • mybackup_old_host/v70tov85dmgr01/logs/WASPreUpgrade.timestamp.log
    • mybackup_old_host/v70tov85dmgr01/logs/WASPreUpgrade.trace

    If there are errors, fix the errors and run the WASPreUpgrade command again. Check whether the warnings affect any other migration or runtime activities on Version 8.5.

    If the command completed successfully, it is not necessary to check the logs for errors or warnings.

What to do next

Archive the backup directory created by the WASPreUpgrade command
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_migrate_remote_commandline_step5
File name: tmig_migrate_remote_commandline_step5.html