Migrate to a WebSphere Application Server Version 6.0 new profile

Tools for migrating administrative configurations are provided for Versions 4 and later. This support enables either edition of Version 4.0.4 (or later) to be upgraded to Version 6.0.

Before performing the instructions on this page, do the steps in Step 1: Plan your migration.

A summary of the product migration process is as follows:

  1. Analyze the Version 4 configuration.
  2. Create a Version 6.0 profile to receive the Version 4 configuration.
  3. Start the Version 4 instance being migrated.
  4. Save the Version 4 configuration.
  5. Restore the Version 4 configuration into a Version 6.0 profile.
  6. Start the Version 6.0 profile that receives the Version 4 configuration

Analyze the Version 4 configuration

Perform the following steps to analyze the Version 4 configuration:

  1. Open the Version 4 console on the instance you would like to migrate. Analyze the environment, taking note of number of application servers and the names of each application server.

Create a Version 6.0 profile to receive the Version 4 configuration

Perform the following steps to create a Version 6.0 profile to receive the Version 4 configuration:

  1. Enter the following command from an OS/400 command line: 
    STRQSH

    This starts the Qshell environment so that you can run WebSphere Application Server scripts.

  2. Run the wasprofile command with the following parameters: 
    install_root/bin/wasprofile -create -profileName 60ProfileName
-startingPort starting_port_number
-templatePath install_root/profileTemplates/defaultnoexamp -serverName 4xApplicationServerName

    where

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • 60ProfileName is the name of your WebSphere Application Server Version 6.0 profile.
    • starting_port_number is the first of a block of 13 consecutive ports.
    • 4xApplicationServerName is the name of your WebSphere Application Server Version 4.x.

    For details on the syntax and parameters of the wasprofile command, see wasprofile command.

Start the Version 4 instance being migrated

Perform the following steps to start the Version 4 instance being migrated:

  1. Enter the following command from an OS/400 command line: 
    STRQSH

    This starts the Qshell environment so that you can run WebSphere Application Server scripts.

  2. Run the strwasinst script with the following parameters: 
    /QIBM/ProdData/WebASAes4/bin/strwasinst -instance 4xInstanceName

    where 4xInstanceName is the name of the Version 4.x instance that is being migrated.

Save the Version 4 configuration

If you have servlets and/or JSPs in the Version 4.x default_app Web application, the WASPreUpgrade migration tool does not migrate them. If you wish to have these servlets and JSPs migrated, move them into a different Web Application before calling WASPreUpgrade.

Perform the following steps to save the Version 4 configuration:

  1. Enter the following command from an OS/400 command line: 
    STRQSH

    This starts the Qshell environment so that you can run WebSphere Application Server scripts.

  2. Run the WasPreUpgrade script with the following parameters: 
    install_root/bin/WASPreUpgrade    
backupDirectoryName
/QIBM/UserData/WebASAEs4/4.xInstanceName

    where:

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • backupDirectoryName(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 WasPreUpgrade.
    • /QIBM/UserData/WebAsAEs4/4.xInstanceName (required parameter) is the fully qualified path of the Version 4.x administrative instance being migrated.

For a full explanation of the WasPreUpgrade migration tool and parameters, see The WASPreUpgrade script.

Restore the Version 4 configuration into a Version 6.0 profile

  1. Enter the following command from an OS/400 command line: 
    STRQSH

    This starts the Qshell environment so that you can run WebSphere Application Server scripts.

  2. Run the WasPostUpgrade script with the following parameters: 
    install_root/bin/WASPostUpgrade backupDirectoryName
-profileName 60ProfileName
[-portBlock port_starting_number]

    where:

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • backupDirectoryName(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 WasPreUpgrade.
    • 60ProfileName is the name of the Version 6.0 profile to which you are migrating the 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. IBM recommends that you always specify the -portBlock parameter if you do not want your profile's ports to conflict with the default profile's ports.

Start the Version 6.0 profile that receives the Version 4 configuration

Perform the following steps to start the Version 6.0 profile:

  1. Enter this command from an OS/400 command line to start the QWAS6 subsystem if it is not already started: 
    STRSBS QWAS6/QWAS6
  2. Enter the following command from an OS/400 command line: 
    STRQSH

    This starts the Qshell environment so that you can run WebSphere Application Server scripts.

  3. Run the startServer script with the following parameters: 
    install_root/bin/startServer -profileName 60ProfileName 4xApplicationServerName

    where install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND. 60ProfileName is the name of the Version 6.0 profile created in an earlier step. 4xApplicationServerName is the name of the Version 6.0 application server created in an earlier step.