Migrate to a WebSphere Application Server Version 5 default instance

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 5.

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

A summary of the product migration process is as follows:

  1. Start the Version 4 instance being migrated.

  2. Save the Version 4 configuration.

  3. Restore the Version 4 configuration into a Version 5 instance.

  4. Start the Version 5 default instance.

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 4.xInstanceName

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

Save the Version 4 configuration

If you have servlets 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. See Issues concerning the migration of JSPs and Servlets in the Application Development topic for more information.

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: 
    /QIBM/ProdData/WebAS5/Base/bin/WASPreUpgrade   
/backup/myBackupDirectory  
/QIBM/UserData/WebASAEs4/4xInstanceName

    where:

    • /backup/myBackupDirectory (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 in the Administration topic.

Restore the Version 4 configuration into a Version 5 instance

Perform the following steps to restore the Version 4 configuration into a Version 5 instance:

  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: 
    /QIBM/ProdData/WebAS5/Base/bin/WASPostUpgrade
/backup/myBackupDirectory

    where /backup/myBackupDirectory (required parameter) is the fully qualified path to the integrated file system directory where the the WasPreUpgrade migration tool had previously been used to save the Version 4 instance configuration.

For a full explanation of the WasPostUpgrade migration tool and parameters, see The WASPostUpgrade script in the Administration topic.

Start the Version 5 default instance

Perform the following steps to start the Version 5 default instance:

  1. If the QEJBAS5 subsystem has not been started, start the default instance by entering this command from an OS/400 command line: 
    STRSBS QEJBAS5/QEJBAS5

  2. If the QEJBAS5 subsystem is already started, and the SERVER1 job is present, stop the server and start it again.

  3. If the QEJBAS5 subsystem is already started, but the SERVER1 job is not present, start the server using the startServer script at the Qshell prompt: 
    /QIBM/ProdData/WebAS5/Base/bin/startServer