[AIX HP-UX Linux Solaris Windows]

Migrating to a Version 6.1 deployment manager

Use the migration tools to migrate from a WebSphere Application Server Network Deployment Version 5.x or 6.0.x deployment manager to a Version 6.1 deployment manager.

Before you begin

See Overview of migration, coexistence, and interoperability and Premigration considerations.

Mixed-version environment Mixed-version environment: Migrate the WebSphere Application Server Version 5.x or 6.0.x deployment manager to Version 6.1 before migrating the managed nodes that comprise the cell. The deployment manager must always be at the highest release and fix level within a cell in order for it to manage all nodes in the cell. In Version 6.1, the deployment manager can manage Version 5.x, Version 6.0.2, and Version 6.1 release 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. See Coexistence support for information on restrictions on using mixed-release cells.mixv
Restriction: Migrating to a Version 6.1 deployment manager on a remote machine is not supported.

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

Tip: Before migrating a WebSphere Application Server Version 5.x or 6.0.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. Make sure that you note the exact name and location of this backed-up configuration.

Procedure

  1. Stop the Version 5.x or 6.0.x deployment manager.

    Use the stopManager command from the app_server_root/bin directory.

    For example, use the following command on a Linux platform:
    ./stopManager.sh

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

    You can migrate a Version 5.x or 6.0.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.x or 6.0.x deployment manager before you can start the Version 6.1 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.x or 6.0.x configuration to Version 6.1.

    The Migration wizard, which is the graphical interface to the Version 6.1 command-line migration tools (WASPreUpgrade command and WASPostUpgrade command), is the recommended migration tool. For detailed instructions and information on the Migration wizard, see Using the Migration wizard to migrate product configurations.

    1. Install the Version 6.1 product on the same machine as the Version 5.x or 6.0.x deployment manager.
    2. Determine the cell name of the Version 5.x or 6.0.x deployment cell.
    3. Optional: Create a new Version 6.1 deployment manager profile with the same cell name as the Version 5.x or 6.0.x cell.
      Restrictions for a deployment manager migration:
      • The Version 6.1 cell name must match the cell name in the Version 5.x or 6.0.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 6.1 deployment manager node name must be the same as the Version 5.x or 6.0.x deployment manager node name.
        • The Version 6.1 deployment manager node name must be different from every node name in the Version 5.x or 6.0.x configuration.
        Otherwise, the migration fails with the following message:
        MIGR0378E: The node name of the new configuration must be the same as the old configuration: {0} for this environment.

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

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

      See Migrating to a Version 6.1 deployment manager using the Migration wizard.

    6. Start the Version 6.1 deployment manager.
    7. Optional: Uninstall the Version 5.x or 6.0.x deployment manager.

      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. See Migrating to a Version 6.1 managed application server for information on iteratively migrating each federated node to Version 6.1.

Results

After the deployment manager is upgraded to Version 6.1, each node in the cell can then be upgraded incrementally, one at a time. See Migrating to a Version 6.1 managed application server. The following diagram illustrates a mixed-release cell containing a Version 6.1 deployment manager with both Version 5.x and Version 6.1 managed nodes:

Migrating Version 5.x-managed nodes to a Version 6.1 dmgr




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: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tmig_to61dm
File name: tmig_to61dm.html