Previous Step   Next Step

Migrate nodes

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

About this task

These steps apply to cross operating system migrations only. If you are not completing a cross operating system migration of a node, see Scenario 1: Migrating a cell using the command-line tools. Ensure that the Version 7.0 deployment manager is running. Use the migration tools to migrate the previous versions of the nodes in the configuration to Version 7.0 Fix Pack 7 or later. For each node that you plan to migrate to Version 7.0 Fix Pack 7 or later, perform the following steps:
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 Fix pack 7 or later.gotcha

Before you begin

Run a migration on application client installations

Procedure

  1. Install WebSphere® Application Server Version 7.0 Install the correct version (Network Deployment, Base, Express) of WebSphere® Application Server onto each target host. For more information, see How do I install an application serving environment?
  2. 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
  3. Use the updated supplemental CD you created to run the WASPreUpgrade command. For more information, see Step 3 of the overall scenario on upgrading the WebSphere Application Server Version 7.0 supplemental CD to the desired fix pack level.
  4. 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_old_host/v61tov7node1 /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/currentNode1Name -traceString *=all=enabled -summaryLogName /mybackup_old_host/v61tov7node1/logs/WASPreMigrationSummary.log -machineChange true
  5. Check the WASPreUpgrade console output for error and warning messages. You might find the following messages: "Failed with errors" or "Completed with warnings". Also, look in the following log files for error or warning messages:
    • myback_old_host/v61tov7node1/logs/WASPreMigrationSummary.log
    • myback_old_host/v61tov7node1/logs/WASPreUpgrade.< timestamp >.log
    • myback_old_host/v61tov7node1/logs/WASPreUpgrade.trace

    If the WASPreUpgrade command is successful, you do not need to check the log files for error or warning messages.

  6. Use the archive tool of your choice to create a compressed file of the backup directory that was created by the WASPreUpgrade command. For example:
    /QIBM/ProdData/WebSphere/AppServer/V7/ND/bin/WASPreUpgrade /mybackup_old_host/v61tov7node1 /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/currentNode1Name -traceString *=all=enabled -summaryLogName /mybackup_old_host/v61tov7node1/logs/WASPreMigrationSummary.log
  7. Move the archived file to the target machine.
  8. Create a directory on the target machine and extract the archived file to the new directory. For example:
    mkdir /mybackup_new_host
    cd /mybackup_new_host
    /opt/WebSphereV7/java/bin/jar -xf v61tov7dmgr01.jar
    where mybackup_new_host is the directory to which you are migrating your files.
  9. Stop the application servers on the old node, then stop the node agent on the old node.
  10. Stop and disable the deployment manager on the old host. Ensure that you do not use the deployment manager on the old host. To disable this deployment manager, you must rename the associated serverindex.xml file as indicated in the following information:
    Old name
    $PROFILE_ROOT/config/cells/cell_name/nodes/node_X/serverindex.xml
    New name
    $PROFILE_ROOT/config/cells/cell_name/nodes/node_X/serverindex.xml_disabled
  11. 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_new_host/v61tov7node1 -profileName currentNode1Name -traceString *=all=enabled -summaryLogName /mybackup_new_host/v61tov7node1/logs/WASPostMigrationSummary.log -replacePorts TRUE -backupConfig TRUE -includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE -username myuser -password mypass
  12. Check the WASPostUpgrade console output for the following messages. You might find the following messages: "Failed with errors" or "Completed with warnings". Also, look in the following log files for errors or warning messages:
    • mybackup_new_host/v61tov7node1/logs/WASPostMigrationSummary.log
    • mybackup_new_host/v61tov7node1/logs/WASPostUpgrade. <target profile>.< timestamp >.log
    • mybackup_new_host/v61tov7node1/logs/WASPostUpgrade.< target profile name >.trace
    Note: If the WASPostUpgrade command fails, you might need to restore the Version 7.0 deployment manager from the backup configuration file. If the WASPostUpgrade command processing ran 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.
  13. Check the Version 7.0 deployment manager SystemOut.log file for error or warning messages.
  14. Start the migrated Version 7.0 node X agent.
  15. Check the Version 7.0 deployment manager and node X SystemOut.log for error or warning messages.
  16. Synchronize the cell if the auto synchronization process is not enabled.
  17. Start the appropriate application servers on Version 7.0 migrated node X.
  18. Run the backupConfig command and save the Version 7.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V7/profiles/v61tov7node1/bin/backupConfig /mybackup_new_host/v61tov7node1.zip -username myuser -password mypass -nostop  
    Each time you run the backupConfig command on a specific node, use a new backup file name.
  19. Save the deployment manager configuration using the backupConfig command. On the Version 7 deployment manager host, change to the deployment_manager_profile_root/bin directory. Run the backupConfig command and save the Version 7.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V7/profiles/currentDmgrName/bin/backupConfig.sh /mybackup_new_host/v61tov7dmgr01backupMigratedDmgrPlusNodeX.zip -username myuser -password mypass
    Note: For each node that you migrate, backup the Version 7 Deployment Manager configuration to a new backup file.
  20. Repeat the previous steps for additional nodes.

What to do next

Troubleshoot

  Previous Step   Next Step