This topic applies only on the i5/OS operating system.

Migrating from Network Deployment to Network Deployment Version 6.1

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

Before you begin

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

See Checking for the product-configuration migration prerequisites to determine the currently installed product level of WebSphere Application Server.

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

Before following these instructions, perform the actions in Preparing for product-configuration migration.

Migration of a WebSphere Application Server Network Deployment Version 5.x or 6.0.x deployment manager and associated federated nodes can be performed in stages.
  1. Migrate the WebSphere Application Server Version 5.x or 6.0.x deployment manager to a Version 6.1 deployment manager.

    After you migrate the Version 5.x or 6.0.x deployment manager to a Version 6.1 deployment manager, you are no longer able to use the Version 5.x or 6.0.x deployment manager. You are only able to use the Version 6.1 deployment manager.

    The Version 5.x or 6.0.x nodes can run in a Version 6.1 deployment cell.

    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.
  2. Migrate each WebSphere Application Server Version 5.x or 6.0.x node to a Version 6.1 federated node.

    After you migrate the Version 5.x or 6.0.x node to a Version 6.1 node, you are no longer able to use the Version 5.x or 6.0.x node. You are only able to use the Version 6.1 node.

    Tip: When migrating a WebSphere Application Server Version 5.x or 6.0.x federated node, you must perform the following actions if you want to be able to roll it back to its previous state after migration:
    1. Back up your existing configuration using the backupConfig command or your own preferred backup utility.
      • Run the backupConfig command or your own preferred utility to back up the Version 6.1 deployment manager configuration.
        Important: Make sure that you note the exact name and location of this backed-up configuration.
      • Run the backupConfig command or your own preferred utility to back up the Version 5.x or 6.0.x federated node configuration.
        Important: Make sure that you note the exact name and location of this backed-up configuration.
    2. Migrate the federated node.

    If necessary, you can now roll back the federated node that you just migrated. See Rolling back a managed node.

Procedure

  1. Create a WebSphere Application Server Version 6.1 deployment manager profile to receive the Version 5.x or 6.0.x deployment manager configuration.

    This step can be skipped if you are migrating to the Version 6.1 default profile.

    1. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    2. Run the dspwasinst script to display the current port settings for the Version 5.x or 6.0.x deployment manager profile.
      Use the following parameters:
      app_server_root/bin/dspwasinst
       -instance 5.x_or_6.0.x_profile_name
      where
      • app_server_root is the location of the Version 5.x or 6.0.x installation that contains the deployment manager to be migrated
      • 5.x_or_6.0.x_profile_name is the name of the Version 5.x or 6.0.x deployment manager profile that is to be migrated

      Make note of the Name service port setting in the Additional ports section. This setting will be used as the starting point when you create the new Version 6.1 deployment manager profile in the next step.

    3. Run the manageprofiles command.
      Use the following parameters:
      app_server_root/bin/manageprofiles
       -create
       -profileName 61ND_profile_name
       -startingPort starting_port_number
      where
      • app_server_root is the location where Version 6.1 is installed
      • 61ND_profile_name is the name of your Version 6.1 deployment manager profile
      • starting_port_number is the first of a block of 10 consecutive ports
  2. Save the WebSphere Application Server Version 5.x or 6.0.x deployment manager configuration.
    1. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    2. Run the WASPreUpgrade script.
      Use the following parameters:
      app_server_root/bin/WASPreUpgrade 
       backup_directory_name
       old_profile_root
      where
      • app_server_root is the location where Version 6.1 is installed
      • backup_directory_name (required parameter) is the fully qualified path to the integrated file system directory where the WASPreUpgrade migration tool stores the saved configuration and files

        The directory is created if it does not already exist. Additionally, the tool writes a log file called WASPreUpgrade.log that chronicles the steps taken by the WASPreUpgrade command.

      • old_profile_root (required parameter) is the path to the Version 5.x or 6.0.x instance or profile to be migrated

      For a full explanation of the WASPreUpgrade command and its parameters, see WASPreUpgrade command.

  3. Restore the WebSphere Application Server Version 5.x or 6.0.x deployment manager configuration into the Version 6.1 deployment manager profile.
    1. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    2. Run the WASPostUpgrade script.
      Use the following parameters:
      app_server_root/bin/WASPostUpgrade
       backup_directory_name
       -profileName 61ND_profile_name
       -replacePorts true
      where
      • app_server_root is the location where Version 6.1 is installed
      • backup_directory_name (required parameter) is the fully qualified path to the integrated file system directory that the WASPreUpgrade migration tool previously used to save the Version 5.x or 6.0.x deployment manager configuration
      • 61ND_profile_name (required parameter) is the name of the Version 6.1 deployment manager profile to which the script migrates your configuration
      • -replacePorts true replaces all virtual host alias port and transport settings in the Version 6.1 profile with the settings from the Version 5.x or 6.0.x instance or profile during migration

      For a full explanation of the WASPostUpgrade command and its parameters, see WASPostUpgrade command.

  4. Start the WebSphere Application Server Version 6.1 deployment manager profile.
    1. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    2. Verify that the Version 5.x or 6.0.x deployment manager, node agent, and federated nodes are stopped for the Version 5.x or 6.0.x deployment manager that was migrated.
    3. If the QWAS61 subsystem has not been started, start the default profile.
      Enter the following command on a command line:
      STRSBS QWAS61/QWAS61
    4. Start the Version 6.1 deployment manager using the startManager script.
      Use the following parameters:
      app_server_root/bin/startManager
       -profileName 61ND_profile_name
      where
      • app_server_root is the location where Version 6.1 is installed
      • 61ND_profile_name is the name of the Version 6.1 deployment manager profile
    5. Start the Version 5.x or 6.0.x node agent and federated nodes.
      1. Start the Version 5.x or 6.0.x node agent using the startNode script.
        Use the following parameters:
        app_server_root/bin/startNode
         -instance 5.x_or_6.0.x_profile_name
        where
        • app_server_root is the location of the Version 5.x or 6.0.x installation that contains the federated node
        • 5.x_or_6.0.x_profile_name is the name of the Version 5.x or 6.0.x instance or profile for the federated node
      2. Start the Version 5.x or 6.0.x federated node using the startServer script.
        Use the following parameters:
        app_server_root/bin/startServer
         -instance 5.x_or_6.0.x_profile_name 
         5.x_or_6.0.x_application_server_name
        where
        • app_server_root is the location of the Version 5.x or 6.0.x installation that contains the federated node
        • 5.x_or_6.0.x_profile_name is the name of the Version 5.x or 6.0.x instance or profile for the federated node
        • 5.x_or_6.0.x_application_server_name is the name of the Version 5.x or 6.0.x application server
  5. Migrate the WebSphere Application Server Version 5.x or 6.0.x federated nodes to Version 6.1.
    1. Verify that the Version 5.x or 6.0.x node agent and federated node are stopped for the federated profile that is to be migrated to Version 6.1.
    2. Verify that the Version 6.1 deployment manager is running.
    3. Complete the instructions in Migrating to a Version 6.1 standalone application server profile for each Version 5.x or 6.0.x federated node that is to be migrated to a Version 6.1 federated node.
      Tip: If you make any cell-level changes to the new Version 6.1 node before migration, such as changes to virtual-host information, these changes will be lost during migration. Therefore, you should wait until after the node has been migrated before making any such changes. Otherwise, you will have to manually remake all of the changes, such as any changes to the virtual-host and host-alias information, to the new cell after migration using the administrative console running on the deployment manager. This tip is reflected in message MIGR0444W.

      Skip the instruction that tells you to start the Version 6.1 profile that receives the WebSphere Application Server Version 5.x or 6.0.x configuration.

      Specify -replacePorts true when you run the WASPostUpgrade script. This allows the Version 6.1 federated node to use the same virtual host ports and transport ports as the Version 5.x or 6.0.x federated node.

  6. Start the WebSphere Application Server Version 6.1 node agent and federated node.
    1. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    2. Start the Version 6.1 node agent using the startNode script.
      Use the following parameters:
      app_server_root/bin/startNode
       -profileName 6.1_profile_name
      where
      • app_server_root is the location where Version 6.1 is installed
      • 6.1_profile_name is the name of the Version 6.1 profile for the federated node
    3. Start the Version 6.1 federated node using the startServer script.
      Use the following parameters:
      app_server_root/bin/startServer
       -profileName 6.1_profile_name
       6.1_application_server_name
      where
      • app_server_root is the location where Version 6.1 is installed
      • 6.1_profile_name is the name of the Version 6.1 profile for the federated node
      • 6.1_application_server_name is the name of the Version 6.1 application server
Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tmig_is_to61nd
File name: tmig_is_to61nd.html