Restore the previous deployment manager configuration

Before you begin

Back up the current deployment manager compute grid configuration

About this task

Step 7 towards the goal: Migrating Compute Grid or Feature Pack for Modern Batch using the command-line tools

To restore the previous deployment manager configuration that you saved in the migration backup directory, run the WASPostUpgrade command from the new deployment manager profile bin directory. If you use the options that are shown in the following example, all the ports will be carried forward, the old deployment manager will be shut down and disabled, and all applications will be 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:
    [AIX Solaris HP-UX Linux Windows]
    /opt/WebSphereV85/bin/WASPostUpgrade.sh /mybackup/Dmgr01 -profileName 
    Dmgr01 -oldProfile 70dmgr01 -replacePorts TRUE -backupConfig TRUE 
    -includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE 
    -username myuser -password mypass
    When creating profiles, only one profile per installation is considered the default.

    The WASPostUpgrade command migrates the default profile for the source and the target installations if the -oldProfile or the -profileName parameters are not specified.

    The default profiles can be identified by looking in the profileRegistry.xml file in the WAS_HOME/properties directory. The source profileRegistry.xml is copied to the migration backup directory as part of the WASPreUpgrade command.
    Avoid trouble Avoid trouble:
    • Always specify the -oldProfile and -profileName parameters when you run the WASPostUpgrade command.
    • The script compatibility flag on your deployment manager must be the same as the flag that you use on your nodes. Save the value of the script compatibility flag for later use.
    gotcha
  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 migration_backup_dir/logs/WASPostUpgrade.target_profile_name.timestamp.log and migration_backup_dir/logs/WASPostUpgrade.target_profile_name.trace log files for any warnings or errors. 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.

What to do next

Update existing system applications and data
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_computegrid_migrating_cg_step7
File name: tmig_computegrid_migrating_cg_step7.html