Previous Step   Previous Step Next Step   Next Step

Migrate nodes

Map Step 13 towards the goal: Scenario 1: Migrating a cell using the command line tools

About this task

Ensure that the Version 7.0 deployment manager is running. Use the migration tooling to migrate the previous versions of the nodes in the configuration to Version 7.0. For each node that you plan to migrate to Version 7.0, perform the following steps:
Avoid trouble Avoid trouble: For the migration to be successful, you must use the same source node name and cell name for each node that you migrate to Version 7.0. gotcha

Before you begin

Run a migration on application client installations

Procedure

  1. Create the target node profile. Run the manageprofiles command with the appropriate parameters to create a new managed profile. For example:
    /QIBM/ProdData/WebSphere/AppServer/V7/ND/bin/manageprofiles -create -profileName currentNode1Name -templatePath /QIBM/ProdData/WebSphere/AppServer/V7/ND/profileTemplates/managed -nodeName currentNode1Name -cellName currentCellName -hostName mynode1host.company.com
  2. Run the WASPreUpgrade command to save the current node X configuration information to a migration backup directory. Choose a new directory for the backup files. For example:
    /QIBM/ProdData/WebSphere/AppServer/V7/ND/bin/WASPreUpgrade /mybackup/v61tov7node1 /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/currentNode1Name -traceString *=all=enabled -summaryLogName /mybackup/v61tov7node1/logs/WASPreMigrationSummary.log
  3. If you intend to change the machine, add the -machineChange true parameter.
  4. If the WASPreUpgrade command completed with Success, then checking the logs for errors or warnings is not necessary.
  5. Check the WASPreUpgrade console output for the following messages: "Failed with errors" or "Completed with warnings".
  6. Look in the following logs for warnings or errors:
    • <migration backupdir>/logs/WASPreMigrationSummary.log
    • WASPreUpgrade.< timestamp >.log
    • WASPreUpgrade.trace
  7. Run the WASPostUpgrade command to restore the saved node X configuration into the new Version 7.0 managed profile. For example:
    /QIBM/ProdData/WebSphere/AppServer/V7/ND/bin/WASPostUpgrade /mybackup/v61tov7node1 -profileName currentNode1Name -traceString *=all=enabled -summaryLogName /mybackup/v61tov7node1/logs/WASPostMigrationSummary.log -replacePorts TRUE -backupConfig TRUE -includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE -username myuser -password mypass
  8. If the command completed with Success, then checking the logs for errors or warnings is not necessary.
  9. Check the WASPostUpgrade console output for the following messages: "Failed with errors" or "Completed with warnings".
  10. Look in the following logs for errors or warnings:
    • <migration backupdir>/logs/WASPostMigrationSummary.log
    • WASPostUpgrade. <target profile>.< timestamp >.log
    • WASPostUpgrade.< target profile name >.trace
    Note: If the WASPostUpgrade command fails, you may have to restore the Version 7.0 deployment manager from the backupConfig file. If the WASPostUpgrade processing executed the syncNode command, then the deployment manager is aware that the node X has been migrated. The node X cannot be migrated again until the deployment manager has been restored to the state before the node X migration.
  11. Check the Version 7.0 deployment manager SystemOut.log for warnings or errors.
  12. Start the migrated Version 7.0 node X agent.
  13. Check the Version 7.0 deployment manager and node X SystemOut.log for warnings or errors.
  14. Synchronize the cell.
  15. Stop all the application servers on the Version 7.0 migrated node X.
  16. Start the appropriate application servers on the Version 7.0 migrated node X.
  17. Run the backupConfig command with the appropriate parameters and save the Version 7.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V7/profiles/v61tov7node1/bin/backupConfig /mybackupdir/v61tov7node1.zip -username myuser -password mypass -nostop  
    Each time you run the backupConfig command, use a new backup file name.
  18. Save the Deployment Manager configuration using the backupConfig command. On the Version 7.0 Deployment Manager host, change to the <deployment manager profile root>/bin directory. Run the backupConfig command with the appropriate parameters and save the Version 7.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V7/profiles/currentDmgrName/bin/backupConfig.sh /mybackupdir/v61tov7dmgr01backupMigratedDmgrPlusNodeX.zip -username myuser -password mypass
    Note: For each node migrated, backup the Version 7.0 Deployment Manager configuration to a new backup file.

Supporting information (generally applicable)

What to do next

Troubleshooting

Previous Step   Previous Step Next Step   Next Step


Terms and conditions for information centers | Feedback

Last updated: Feb 6, 2014 2:51:05 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=tmig_migrate_cells_commandline_step13
File name: tmig_migrate_cells_commandline_step13.html