WAS v8.5 > End-to-end paths

Scenario 1: Migrate a cell to v8.5


This task describes how to use the command line tools to migrate a cell from a previous version of WAS to v8.5. The cell configuration consists of a deployment manager with one or more nodes, a web server, and an application client. All ports are migrated forward into the new configuration. This scenario covers migrating cells on the same host. To migrate cells to a different host, see Scenario 2: Migrating cells across operating systems using the command-line tools. command.

  1. Make backup of current dmgr and nodes.

    On dmgr host...

      cd /opt/WAS7/profiles/vv70Dmgr01/bin/
      ./backupConfig.sh /path/to/before_mig_dmgr.zip -username myuser -password mypass -nostop

    For each node in the configuration...

      cd /opt/WAS7/profiles/v70node01/bin/
      ./backupConfig.sh /path/to/before_mig_profile.zip -username myuser -password mypass -nostop

  2. Install WebSphere Application Server v8.5 onto each target host in a new directory.

  3. Create the target deployment manager profile

      cd /opt/WAS85/bin/
      ./manageprofiles.sh -create -profileName v85Dmgr01 -templatePath /opt/WAS85/profileTemplates/management -serverType DEPLOYMENT_MANAGER -nodeName currentDmgrNodeName -cellName currentCellName -hostName dmgr.company.com

    The v8.5 profile nodeName and cellName must match the previous v7.0 or above nodeName and cellName. If the v8.5 deployment manager cellName or nodeName are different, the migration will fail.

  4. Save the current deployment manager configuration information to a migration backup directory...

      cd /opt/WAS85/bin/
      ./WASPreUpgrade.sh /tmp/backupdir /opt/WAS7 -oldProfile v70Dmgr01

    The WASPreUpgrade command does not make any changes to the v7.0 or above configuration. If we are migrating from v8.0 to v8.5, and your profile is a deployment manager, the v8.0 profile is stopped during WASPreUpgrade and then restarted.

    If WASPreUpgrade console output throws "Failed with errors" or "Completed with warnings", review...

    • WASPreUpgrade.oldProfile.timestamp.log
    • WASPreUpgrade.trace

  5. Restore the saved deployment manager configuration into the new v8.5 deployment manager profile...

      cd /opt/WAS85/bin/
      ./WASPostUpgrade.sh /tmp/backupdir -profileName v85Dmgr01 -oldProfile v70Dmgr01 -replacePorts TRUE -backupConfig TRUE -includeApps TRUE -scriptCompatibility TRUE -keepDmgrEnabled FALSE -username myuser -password mypass

    All the ports will be carried forward, the old deployment manager will be shutdown and disabled, and all applications will be installed.

    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...

      WAS_HOME/properties/profileRegistry.xml

    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 WASPostUpgrade.
    • The script compatibility flag on the dmgr must be the same as the flag used on your nodes. Save the value of the script compatibility flag for later use.

    If console output shows "Failed with errors" or "Completed with warnings", check logs...

    • migration_backupdir/logs/WASPostUpgrade.target_profile.timestamp.log
    • migration_backupdir/logs/WASPostUpgrade.target_profile.trace

  6. Save the v8.5 migrated deployment manager configuration to a file.

    If there are any node migration failures, the cell configuration can be restored to the point prior to the failure, remedial actions can be applied, and the node migration can be attempted again.

      cd /opt/WAS85/profiles/v85Dmgr01/bin/
      ./backupConfig.sh /mybackupdir/v85Dmgr01backupMigratedDmgrOnly.zip -username myuser -password mypass

  7. Stop the previous version of the deployment manager.

  8. Start the new v8.5 DMGR

      cd /opt/WAS85/profiles/v85Dmgr01/bin/
      ./startManager

  9. Review SystemOut.log file for warnings or errors.

  10. Review nodeagent and application server logs.

    If "Automatic synchronization" is enabled, then allow the node to synchronize, allow the applications to restart, and then check the logs for new warnings or errors.

  11. Upgrade the version of the web server plugin used in the cell.

  12. Migrate client resources to v8.5 level resources.

    1. Install the WebSphere v8.5 Application client.

    2. Run clientUpgrade on application client ear files.

    3. Save the Application client security settings to a migration backup directory...

        cd /opt/AppClientV85/bin
        ./WASPreUpgrade.sh /mybackup/v70clientTov85 /opt/AppClientV70

    4. Restore the Application client security settings to the new v8.5 client...

  13. Migrate nodes to v8.5...

    1. Create the target node profile.

        cd /opt/WAS85/ ./manageprofiles.sh -create -profileName node1 -templatePath /opt/WAS85/profileTemplates/managed -nodeName currentNode1Name -cellName currentCellName -hostName mynode1host.company.com

      For the migration to be successful, use the same source node name and cell name for each node that you migrate to v8.5.

    2. Save the current node configuration information...

      Choose a new directory for the backup files.

        cd /opt/WAS85/bin
        ./WASPreUpgrade.sh /mybackup/v70tov85node1 /opt/WAS7 -oldProfile 70node1

    3. If command completes with "Failed with errors" or "Completed with warnings", check logs...

      • migration_backupdir/logs/WASPreUpgrade.oldProfile.timestamp.log
      • migration_backupdir/logs/WASPreUpgrade.trace

    4. Stop the node agent.

    5. Restore the saved node configuration into the new v8.5 managed profile.

        cd /opt/WAS85/bin/
        ./WASPostUpgrade.sh /mybackup/v70tov85node1 -profileName v70tov85node1 -oldProfile 70node1 -replacePorts TRUE -backupConfig TRUE -scriptCompatibility TRUE -username myuser -password mypass

      The script compatibility flag on your deployment manager must be the same as the flag that we use on your nodes.

      If console output throws "Failed with errors" or "Completed with warnings", review...

      • /path/to/mig/backupdir/logs/WASPostUpgrade.target_profile.timestamp.log
      • /path/to/mig/backupdir/logs/WASPostUpgrade.< target profile name >.trace

      If the WASPostUpgrade command fails, you may have to restore the v8.5 deployment manager from the backupConfig file. If the WASPostUpgrade processing executed the syncNode command, then the deployment manager is aware the node has been migrated. The node cannot be migrated again until the deployment manager has been restored to the state before the node migration.

    6. Check the v8.5 deployment manager SystemOut.log for warnings or errors.

    7. Start the migrated v8.5 node agent.

    8. Check the v8.5 deployment manager and node SystemOut.log for warnings or errors.

    9. Synchronize the cell.

    10. Stop all the application servers on the v8.5 migrated node.

    11. Start the appropriate application servers on the v8.5 migrated node.

  14. Run the backupConfig command with the appropriate parameters and save the v8.5 profile configuration to a file.

      cd /opt/WAS85/profiles/v70tov85node1/bin/
      ./backupConfig.sh /mybackupdir/v70tov85node1.zip -username myuser -password mypass -nostop

    Each time you run the backupConfig command, use a new backup file name.

  15. Save the Deployment Manager configuration.

    From v8.5 Deployment Manager host.

      cd /opt/WAS85/profiles/v85Dmgr01/bin/
      ./backupConfig.sh /mybackupdir/v85Dmgr01backupMigratedDmgrPlusNodeX.zip -username myuser -password mypass

    If we 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.

    For each node migrated, backup the v8.5 Deployment Manager configuration to a new backup file.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


+

Search Tips   |   Advanced Search