Migrating a Version 5.x deployment manager configuration instance to a Version 6.0.x deployment manager profile

Use the migration tools to migrate a Version 5.x deployment manager configuration instance to a Version 6.0.x deployment manager profile.

Before you begin

Migrate WebSphere Application Server Network Deployment Version 5.x to Version 6.0.x before migrating the base nodes that comprise the cell. The Network Deployment node must always be at the highest release and fix level within a cell, to allow it to manage all nodes in the cell. Starting with Version 6.0, the deployment manager has the capability to manage both Version 6.0.x and Version 5.x 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.

If you have a Web services gateway running on a Version 5.x application server that is part of a Network Deployment cell, and you want to migrate the cell from a Version 5.x to a Version 6.0.x deployment manager, you must first preserve the gateway configuration.

About this task

Use the following procedure to migrate the deployment manager instance.

Procedure

  1. Stop the Version 5.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 deployment manager without stopping it, but it is not necessary for it to be running for you to migrate its configuration. The migration tools can retrieve all the configuration data while the deployment manager is either running or stopped. However, you must stop the Version 5.x deployment manager before you can start the Version 6.0.x deployment manager that you are installing, so it makes sense to stop it now.

  2. Use the migration tools to migrate the Version 5.x configuration to Version 6.0.x. The Migration wizard, which is the graphical interface to the Version 6.0.x command-line migration tools (WASPreUpgrade command and WASPostUpgrade command), is the recommended migration tool. For detailed instructions and information on the new Migration wizard, see Using the Migration wizard. The instructions below describe migration using the command-line migration tools.
    1. Install the Version 6.0.x product on the same machine as the Version 5.x deployment manager.
    2. Create a new deployment manager profile with the same node name, host name, and cell name as the Version 5.x cell. Also, ensure that the port numbers for the new Version 6.0.x deployment manager match the port numbers used by the Version 5.x deployment manager.
    3. Verify the installation of the Version 6.0.x deployment manager. Use the First Steps tool when it opens at the end of installing the product, or run the installation verification test yourself, if the First Steps tool does not appear for some reason.
    4. Stop the Version 6.0.x deployment manager.
    5. Run the WASPreUpgrade script.

      From the Version 6.0.x deployment manager's profile_name/bin directory, run the following command:

      Linux:
      ./WASPreUpgrade.sh backupDmgrDir V5_location
      Windows:
       WASPreUpgrade.bat backupDmgrDir V5_location
      where backupDmgrDir is the name of the directory you want the output of WASPreUpgrade to be stored, and V5_location is the location where the Version 5.x deployment manager is installed.
    6. Run the WASPostUpgrade script.

      From the Version 6.0.x deployment manager's profile_name/bin directory, run the following command:

      Linux:
      ./WASPostUpgrade.sh backupDmgrDir -oldProfile host_instance_name -profileName dmgr_profile_name
      Windows:
      WASPostUpgrade.bat backupDmgrDir -oldProfile host_instance_name -profileName dmgr_profile_name
      where backupDmgrDir is the same directory you specified in WASPreUpgrade, and dmgr_profile_name is the name of the Version 6.0.x deployment manager profile. (See WASPostUpgrade command for more information on the WASPostUpgrade command.)
    7. Start the Version 6.0.x deployment manager.
    8. Optional: Uninstall the Version 5.x node. Perform this step only after you are certain that you have successfully migrated the configuration of the deployment manager you intend to delete. During migration processing, the Version 5.x Network Deployment environment will be disabled. This is done to prevent an unsupported scenario, such as a node being managed by two different cells, from occurring. The Version 5.x Network Deployment environment can be enabled by running the following JACL script from the Version 5.x Network Deployment/bin directory:
      migrationDisablementReversal.jacl

Results

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

Migrating Version 5-managed nodes to a Version 6 dmgr

The migration tools migrate Version 5.x samples to the Version 6.0.x Network Deployment node, to support cell members at the Version 5.x level. If the migration did not migrate the Version 5.x samples, a synchronization would remove the samples from the Version 5.x nodes. After migrating all federated nodes to Version 6.0.x, the Version 5.x samples remain in the configuration. You can remove the Version 5.x samples at that time or replace them with the Version 6.0.x samples.

What to do next

Return to Migrating configuration data to continue.



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    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tins_migdmgrinstance
File name: tins_migdmgrinstance.html