Previous | Next


Run the WASPostUpgrade command from the new dmgr profile bin directory

 


Step 6: Scenario 1: Migrating a cell using the command line tools

Use the WASPostUpgrade command to restore the previous dmgr configuration that you saved in the migration backup directory. If you use the options shown in the example, all the ports will be carried forward, the old dmgr will be shutdown and disabled, and all applications will be installed.


Procedure

  1. Run the WASPostUpgrade command to restore the saved dmgr configuration into the new v8.0 dmgr profile. For example: 
    /opt/WASv8/bin/WASPostUpgrade.sh /mybackup/v61v8dmgr01 -profileName
v61v8dmgr01 -oldProfile 61dmgr01 -replacePorts TRUE -backupConfig TRUE
-includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE
-username myuser -password mypass
    When creating profiles, only one profile is considered the default per installation.

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

    The default profiles can be identified by looking in the profileRegistry.xml file found in...

    WAS_HOME/properties
    The source profileRegistry.xml is copied to the migration backup directory as part of the WASPreUpgrade command.

    • The -oldProfile and -profileName parameters should always be specified when running the WASPostUpgrade command.

    • The script compatibility flag on your dmgr must be the same as the flag that you use on your nodes. Save the value of the script compatibility flag for later use.


Support information (generally applicable)


What to do next

Verify the logs for success




+

Search Tips   |   Advanced Search