Migrating to a Version 6.1 standalone application server profile

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

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, perform the actions in Preparing for product-configuration migration.

Tip: Before migrating a WebSphere Application Server Version 5.x or 6.0.x standalone application server profile, 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. Create a WebSphere Application Server Version 6.1 profile to receive the Version 5.x or 6.0.x 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 dspwasinst script to obtain the node name and server name for the Version 5.x or 6.0.x instance or profile that is to be migrated.
      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 instance or profile to be migrated
      • 5.x_or_6.0.x_profile_name is the name of the Version 5.x or 6.0.x instance or profile that is to be migrated
      The name of the Version 5.x or 6.0.x node is listed in the Node section, and the name of the server is listed in the Information for server section.
    3. Run the manageprofiles script.
      Use the following parameters:
      app_server_root/bin/manageprofiles
       -create 
       -profileName 6.1_profile_name
       -startingPort starting_port_number
       -templatePath app_server_root/profileTemplates/default
       -serverName 5.x_or_6.0.x_application_server_name
       -nodeName 5.x_or_6.0.x_node_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 profile

        This parameter must be identical to the Version 5.x or 6.0.x instance or profile that is to be migrated. The source and target node names must be identical when migrating to Version 6.1.

      • starting_port_number is the first of a block of 13 consecutive ports
      • 5.x_or_6.0.x_application_server_name is the name of the Version 5.x or 6.0.x application server obtained in the previous step
      • 5.x_or_6.0.x_node_name is the Version 5.x or 6.0.x node name obtained in the previous step
  2. Save the WebSphere Application Server Version 5.x or 6.0.x 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
       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. It is also the directory where the WASPreUpgrade migration tool writes a log file called WASPreUpgrade.log that chronicles the steps taken by the WASPreUpgrade command.

      • profile_root (required parameter) is the path to the Version 5.x or 6.0.x instance or profile that is 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 configuration into a Version 6.1 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 6.1_profile_name
       [-portBlock port_starting_number]
      
      where
      • app_server_root is the location where Version 6.1 is installed
      • backup_directory_name is the required name of the directory in which the WASPreUpgrade tool stored the saved configuration and files and from which the WASPostUpgrade tool reads the configuration and files
      • 6.1_profile_name is the name of the Version 6.1 profile to which the script migrates your configuration
      • port_starting_number specifies the first of a block of 10-15 consecutive port numbers that are not in use on the iSeries server where the migration is being performed

        It is recommended that you always specify the -portBlock parameter if you do not want your profile's ports to conflict with the default profile's ports.

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

  4. Start the WebSphere Application Server Version 6.1 profile that receives the Version 5.x or 6.0.x configuration.
    1. Start the QWAS61 subsystem if it is not already started.
      Enter the following command on a command line:
      STRSBS QWAS61/QWAS61
    2. Start the Qshell environment so that you can run WebSphere Application Server scripts.
      Enter the following command on a command line:
      STRQSH
    3. Run the startServer script.
      Use the following parameters:
      app_server_root/bin/startServer
       -profileName 6.1_profile_name
       5.x_or_6.0.x_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 created in an earlier step
      • 5.x_or_6.0.x_server_name is the name of the Version 5.x or 6.0.x application server that was migrated
Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=tmig_is_to61sas
File name: tmig_is_to61sas.html