+

Search Tips   |   Advanced Search

Save the current deployment manager configuration to the migration backup directory

Create the target dmgr profile

Parent

Migrate cells using the command-line tools

To save the current deployment manager configuration to the migration backup directory, run the WASPreUpgrade command from the new dmgr profile bin directory. The WASPreUpgrade command does not change the Version 7.0 or above configuration.

If we are migrating from Version 8.0 to v8.5 and the profile is a deployment manager, the Version 8.0 profile is stopped when you run the WASPreUpgrade command. 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.

  1. Run the WASPreUpgrade command. For example:
    (dist)

      /opt/WebSphereV85/bin/WASPreUpgrade.sh /mybackup/v70tov85dmgr01 /opt/WebSphereV70 -oldProfile 70dmgr01


    (iseries)

      /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin/WASPreUpgrade /mybackup/v70tov85dmgr01 /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/myCurrentDmgrProfile

  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 WASPreUpgrade.old_Profile.timestamp.log and WASPreUpgrade.trace log files for any warnings or errors. 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 v8.5.

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


What to do next

Restore the previous deployment manager configuration


Subtopics

  • WASPreUpgrade command