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

Migrating a standalone application server to a Version 6.1 federated node

Use the migration tools to migrate from WebSphere Application Server Version 5.x or 6.0.x standalone application server to a new Network Deployment Version 6.1 federated node.

Before you begin

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

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

Before following these instructions, take the steps in Preparing for product-configuration migration.

Procedure

  1. Migrate the WebSphere Application Server Version 5.x or 6.0.x standalone application server to a Version 6.1 standalone application server profile.

    Complete the instructions in Migrating to a Version 6.1 standalone application server profile.

  2. Create a 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. Run the manageprofiles command.
      Use the following parameters:
      app_server_root/bin/manageprofiles 
       -create
       -profileName 61ND_profile_name
       -startingPort starting_port_number
       -templatePath app_server_root/profileTemplates/dmgr
      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
  3. Add the WebSphere Application Server Version 6.1 standalone application server node to the Version 6.1 deployment.
    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 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 your Version 6.1 deployment manager profile
    3. Run the addNode script.
      Use the following parameters:
      app_server_root/bin/addNode
       -profileName 6.1_profile 
       host 
       soap_port 
       -includeapps
      where
      • app_server_root is the location where Version 6.1 is installed
      • 6.1_profile is the Version 6.1 standalone application server profile to which the Version 5.x or 6.0.x profile was migrated
      • host is the host name of the system on which the Version 6.1 deployment manager is running
      • soap_port is the SOAP port for the Version 6.1 deployment manager

      If you have already used addNode to add a default profile to the deployment cell, specify -startingport port_value (where port_value is the first port in a block of unused ports).

  4. Add migrated resources to the WebSphere Application Server Version 6.1 deployment.
    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
      
      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 stored the saved Version 5.x or 6.0.x configuration and files

        This is also the directory where the WASPreUpgrade migration tool wrote a log file called WASPreUpgrade.log that chronicled the steps taken by the WASPreUpgrade command.

      • 61ND_profile_name is the name of the Version 6.1 deployment manager to which the script migrates your configuration

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

  5. Start the WebSphere Application Server Version 6.1 deployment manager, 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 deployment manager using the startManager script if it is not already started.
      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
    3. Start the Version 6.1 node agent using the startNode script if it is not already started.
      Use the following parameters:
      app_server_root/Base/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 your Version 6.1 federated node
    4. 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 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tmig_is_to61mn
File name: tmig_is_to61mn.html