Previous Step   Previous Step Next Step   Next Step

Migrate nodes

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

About this task

Ensure that the Version 8.0 deployment manager is running. Use the migration tooling to migrate the previous versions of the nodes in the configuration to Version 8.0. For each node that you plan to migrate to Version 8.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 8.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/V8/ND/bin/manageprofiles -create 
    -profileName currentNode1Name -templatePath /QIBM/ProdData/WebSphere/AppServer
    /V8/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/V8/ND/bin/WASPreUpgrade /mybackup/
    v61tov8node1 /QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/currentNode1Name  
  3. If the WASPreUpgrade command completed with Success, then checking the logs for errors or warnings is not necessary.
  4. Check the WASPreUpgrade console output for the following messages: "Failed with errors" or "Completed with warnings".
  5. Look in the following logs for warnings or errors:
    • <migration backupdir>/logs/WASPreUpgrade.< oldProfile >< timestamp >.log
    • <migration backupdir>/logs/WASPreUpgrade.trace
  6. Stop the node agent. If you have Version 6.x nodes running during a migration to Version 8.0, you must stop the node agent on the node being migrated. If you do not stop the node agent, you might encounter corruption problems.
  7. Run the WASPostUpgrade command to restore the saved node X configuration into the new Version 8.0 managed profile. For example:
    /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/WASPostUpgrade /mybackup/
    v61tov8node1 -profileName currentNode1Name -replacePorts TRUE -backupConfig 
    TRUE -scriptCompatibility TRUE -username myuser -password mypass
    Avoid trouble Avoid trouble: The script compatibility flag on your deployment manager must be the same as the flag that you use on your nodes.gotcha
  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/WASPostUpgrade.<target profile>.< timestamp >.log
    • <migration backupdir>/logs/WASPostUpgrade.< target profile name >.trace
    Note: If the WASPostUpgrade command fails, you may have to restore the Version 8.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 8.0 deployment manager SystemOut.log for warnings or errors.
    New feature New feature: This topic references one or more of the application server log files. Beginning in WebSphere Application Server Version 8.0 you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.newfeat
  12. Start the migrated Version 8.0 node X agent.
  13. Check the Version 8.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 8.0 migrated node X.
  16. Start the appropriate application servers on the Version 8.0 migrated node X.
  17. Run the backupConfig command with the appropriate parameters and save the Version 8.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V8/profiles/v61tov8node1/bin/backupConfig 
    /mybackupdir/v61tov8node1.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 8 Deployment Manager host, change to the <deployment manager profile root>/bin directory. Run the backupConfig command with the appropriate parameters and save the Version 8.0 profile configuration to a file. For example:
    /QIBM/UserData/WebSphere/AppServer/V8/profiles/currentDmgrName/bin/
    backupConfig.sh /mybackupdir/v61tov8dmgr01backupMigratedDmgrPlusNodeX.zip 
    -username myuser -password mypass
    Note: If you are migrating a node to a different host, refer to these steps in Scenario 2: Migrating cells across operating systems using the command-line tools.
    Note: For each node migrated, backup the Version 8 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 of Use | Feedback

Last updated: Sep 20, 2011 12:59:05 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-iseries&topic=tmig_migrate_cells_commandline_step12
File name: tmig_migrate_cells_commandline_step12.html