Previous Step   Next Step

Run the WASPostUpgrade command from the new deployment manager profile bin directory

 Step 8 towards the goal: Scenario 2: Migrating cells across operating systems using the command-line tools

About this task

Use the WASPostUpgrade command 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 the ports are carried forward, and all applications are installed.

Before you begin

Archive the backup directory created by the WASPreUpgrade command

Procedure

  1. Run the WASPostUpgrade command to restore the saved deployment manager configuration into the new Version 7.0 deployment manager profile. For example:
    /QIBM/ProdData/WebSphere/AppServer/V7/ND/bin/WASPostUpgrade /mybackup_new_host/v61tov7dmgr01 -profileName myCurrentDmgrProfile -traceString *=all=enabled -summaryLogName /mybackup_new_host/v61tov7dmgr01/logs/WASPostMigrationSummary.log -oldProfile myCurrentDmgrProfile -replacePorts TRUE -backupConfig TRUE -includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE -username myuser -password mypass
    where mybackup_new_host is the directory to which you are migrating your files.

Results

Avoid trouble: 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

Supporting information (generally applicable)

What to do next

Verify the logs for success

  Previous Step   Next Step