Restore the previous deployment manager configuration

Before you begin

Archive the backup directory created by the WASPreUpgrade command

About this task

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

Run the WASPostUpgrade command from the new deployment manager profile bin directory to restore the previous deployment manager configuration that you saved in the migration backup directory. If you use the options shown in the example, all ports are carried forward, and all applications are installed.

Procedure

  1. Run the WASPostUpgrade command to restore the saved deployment manager configuration into the new Version 8.5 deployment manager profile. For example:
    [Windows]
    version_8.5_install_root\bin\WASPostUpgrade.bat \
    mybackup_new_host\v70tov85dmgr01 -profileName v70tov85dmgr01 -oldProfile 
    70dmgr01 -replacePorts TRUE -backupConfig TRUE -scriptCompatibility TRUE 
    -keepDmgrEnabled TRUE -username myuser -password mypass
    [AIX][HP-UX][Linux][Solaris]
    version_8.5_install_root/bin/WASPostUpgrade.sh /
    mybackup_new_host/v70tov85dmgr01 -profileName v70tov85dmgr01 -oldProfile
     70dmgr01 -replacePorts TRUE -backupConfig TRUE -scriptCompatibility TRUE 
    -keepDmgrEnabled TRUE -username myuser -password mypass
    where mybackup_new_host is the directory from which the source profile configuration files are migrated.
  2. Review warnings or errors in the console output and WASPostUpgrade logs. After the WASPostUpgrade 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_new_host/v70tov85dmgr01/logs/WASPostMigrationSummary.log
    • mybackup_new_host/v70tov85dmgr01/logs/WASPostUpgrade.target profile name.timestamp.log
    • mybackup_new_host/v70tov85dmgr01/logs/WASPostUpgrade.target profile name.trace

    If there are errors, fix the errors and run the WASPostUpgrade 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.

Results

Avoid trouble Avoid trouble:
  • The script compatibility flag on your deployment manager must be the same as the flag that you use on your clients. Save the value of the script compatibility flag for later use.
  • After the WASPostUpgrade command completes successfully, do not start the new deployment manager. You must complete a few more steps before starting the new deployment manager.
gotcha

What to do next

Save the Version 8.5 migrated deployment manager configuration to a file
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_step7
File name: tmig_migrate_remote_commandline_step7.html