Migrate to WebSphere Application Server Version 5 default instance

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

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:

Start the Version 3.5 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/WebASAdv/bin/strwasinst -instance 3.5.xInstanceName

    where 3.5.xInstanceName is the name of the Version 3.5.x instance that is being migrated. You must wait for the administrative server to start successfully before continuing.

Save the Version 3.5 configuration.

If you have servlets and/or JSPs in the Version 3.5.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.

To save the Version 3.5 configuration, perform the following steps:

  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 Version 5 WasPreUpgrade script as shown below: 
    /QIBM/ProdData/WebAS5/Base/bin/WASPreUpgrade    
/backup/myBackupDirectory  
/QIBM/UserData/WebAsAdv/3.5.xInstanceName   
adminNodeName
-nameServiceHost adminNodeName 
-nameServicePort port_number

    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/WebAsAdv/3.5.xInstanceName (required parameter) is the fully qualified path of the Version 3.5.x administrative instance being migrated.

    • adminNodeName (required parameter) is the name of the administration node for the Version 3.5.x instance. Generally, this is the iSeries host name from CFGTCP option 12. The WASPreupgrade tool invokes the Version 3.5 XMLConfig tool using this parameter.

    • The -nameServiceHost and -nameServicePort parameters are also passed to XMLConfig. They are needed to override the default host name and port number used by XMLConfig and are required parameters when the Version 3.5.x instance being migrated is not the default instance. The value for -nameServiceHost is the TCP/IP host name of the iSeries server. The value for the -nameServicePort is the bootstrap port for the Version 3.5.x administrative server. The default bootstrap port is 900.

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

Restore the Version 3.5 configuration into a Version 5 instance

Perform the following steps to restore the Version 3.5 configuration into the Version 5 default 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
backupDirectoryName
[-instance 5_instance_name]
[-portBlock port_starting_number]

    The first argument is required. Supported arguments include:

    • backupDirectory
      Required name of the directory in which the WASPreUpgrade tool stores the saved configuration and files, and from which the WASPostUpgrade tool reads the configuration and files. The WASPreUpgrade tool creates this directory if it does not already exist. This parameter is equivalent to the -W migrationInformationPanelBean.migrationBackupDir="/tmp/migrationbackup" parameter in the silent installation options response file.

    • -portBlock
      Optional. The value portblock specifies the first number of a block of port numbers that your instance uses. Specify the first port in a group of unused ports on your iSeries server. Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to display a list of port numbers that are currently being used. This parameter is case sensitive.

      Note: Although this is an optional parameter, it is recommended that you always specify the parameter (or the specific port parameters, described below) if you do not want your instance's ports to conflict with the default instance's ports.

    For the -portBlock parameter, the script checks instances of WebSphere Application Server Version 5 and WebSphere Application Server Version 5, Network Deployment. The script is not able to detect port usage by other applications, including previous versions of WebSphere Application Server.

    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 the following command on the 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:

    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. Enter the startServer command at the Qshell command prompt.

      /QIBM/ProdData/WebAS5/Base/bin/startServer