Migrating to a Version 7.0 deployment manager

Use the migration tools to migrate from a WebSphere® Application Server, Network Deployment Version 5.1.x or Version 6.x deployment manager to a Version 7.0 deployment manager.

Before you begin

Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

Mixed-version environment Mixed-version environment: Migrate the WebSphere Application Server Version 5.1.x or Version 6.x deployment manager to Version 7.0 before migrating the federated nodes that comprise the cell. The deployment manager must always be at the highest release and fix level within a cell for it to manage all nodes in the cell. The Version 7.0 deployment manager can manage Version 5.1.x, Version 6.x, and Version 7.0 nodes. This allows a cell to be upgraded to a new release one node at a time, with minimal impact to the applications that are running within the cell. Read Coexistence support for information on restrictions on using mixed-release cells.mixv
Tip: Before migrating a WebSphere Application Server Version 5.1.x or Version 6.x deployment manager, use the backupConfig command or your own preferred backup utility to back up your existing configuration if you want to be able to restore it to its previous state after migration. Read the "backupConfig command" article in the information center for more information. Make sure that you note the exact name and location of this backed-up configuration.

For help in troubleshooting problems when migrating, read Troubleshooting migration.

Procedure

  1. Stop the Version 5.1.x or Version 6.x deployment manager.

    Use the stopManager command from the app_server_root/bin directory.

    For example:

    Read the "stopManager command" article in the information center for more information.

    If you have security enabled, specify the -user and -password parameters of the command.

    You can migrate a Version 5.1.x or Version 6.x deployment manager whether it is running or stopped. The migration tools can retrieve all the configuration data either way. You must stop the Version 5.1.x or Version 6.x deployment manager before you can start the Version 7.0 deployment manager that you are installing, however, so it makes sense to stop it now.

  2. Use the migration tools to migrate the Version 5.1.x or Version 6.x configuration to Version 7.0.

    The Migration wizard, which is the graphical interface to the Version 7.0 command-line migration tools (WASPreUpgrade and WASPostUpgradeF), is the recommended migration tool. For instructions and information on the Migration wizard, read Migrating product configurations with the migration wizard.

    1. Install the Version 7.0 product on the same machine as the Version 5.1.x or Version 6.x deployment manager.

      Read the "Installing the product and additional software" article in the information center for more information.

    2. Determine the cell name of the Version 5.1.x or Version 6.x WebSphere Application Server, Network Deployment cell.
      Note: For a deployment manager migration, the Version 7.0 cell name must match the name in the Version 5.1.x or Version 6.x configuration.
    3. Optional: Create a new Version 7.0 deployment manager profile with the same cell name as the Version 5.1.x or Version 6.x cell.
      Restrictions for a deployment manager migration:
      • The Version 7.0 cell name must match the cell name in the Version 5.1.x or Version 6.x configuration.

        If you create a profile with a new cell name, the migration will fail.

      • Either one or the other of the following options must be true:
        • The Version 7.0 deployment manager node name must be the same as the Version 5.1.x or Version 6.x deployment manager node name.
        • The Version 7.0 deployment manager node name must be different from every node name in the Version 5.1.x or Version 6.x configuration.
        Otherwise, the migration fails with the following message:
        MIGR0488E: The deployment manager node name in 
        the new configuration ({0}) cannot be the same 
        as a nodeagent node in the old configuration.

      Read the "manageprofiles command" article in the information center for more information.

      If you also use the same node name that you used for the Version 5.1.x or Version 6.x cell, the node agents will still work after migration without being restarted.

    4. Stop the Version 7.0 deployment manager.
    5. Use the Migration wizard to migrate the deployment manager to Version 7.0.

      For more information, read Migrating to a Version 7.0 deployment manager using the Migration wizard.

    6. Start the Version 7.0 deployment manager.
    7. Optional: Uninstall the Version 5.1.x or Version 6.x deployment manager.

      Read the "Uninstalling the product" article in the information center for more information.

      Perform this step only after you are certain that you have successfully migrated the configuration of the deployment manager that you intend to delete.

    8. Read Migrating a Version 5.1.x or Version 6.x federated node for information on iteratively migrating each federated node to Version 7.0.

Results

After the deployment manager is upgraded to Version 7.0, each node in the cell can be upgraded incrementally, one at a time. Read Migrating a Version 5.1.x or Version 6.x federated node for more information.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

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