Migrate to a WebSphere Application Server Version 5, Network Deployment new 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 Network Deployment.

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. Migrate Version 4 to a Version 5 Base instance.

  2. Create a Network Deployment instance.

  3. Add the WebSphere Application Server Version 5 ("Base") instance to the Network Deployment instance.

  4. Add migrated resources to the Network Deployment instance.

  5. Start the Version 5 instance that receives the Version 4 configuration.

Migrate Version 4 to a Version 5 Base instance

Complete the instructions in Migrate to WebSphere Application Server Version 5 new instance. When you have finished, continue with the steps in this topic.

Create a Network Deployment instance

Perform the following steps to create a Network Deployment 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 crtnewinst script with the following parameters: 
    /QIBM/ProdData/WebAS5/ND/bin/crtwasinst
-instance 50NDInstanceName
-portblock starting_port_number

    where 50NDInstanceName is the name of your WebSphere Application Server Version 5, Network Deployment instance, and starting_port_number is the first of a block of 13 consecutive ports.

    For details on the syntax and parameters of the crtwasinst script, see Create a new instance in the Administration topic.

Add the WebSphere Application Server Version 5 ("Base") instance to the Network Deployment instance.

Perform the following steps to add the Base instance to the Network Deployment 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 addNode script with the following parameters: 
    /QIBM/ProdData/WebAS5/Base/bin/addNode
-instance baseInstance host soapPort -includeapps

    where host is the host name of the system the Network Deployment instance is running on, and soapPort is the SOAP port for the Network Deployment instance.

    If you have already used addNode to add the default instance to a Network Deployment instance, specify -startingport portValue where portValue is the first port in a block of 14 unused ports. For details on the syntax and parameters of the addNode script, see The addNode script in the Administration topic.

Add migrated resources to the Network Deployment instance

Perform the following steps to add migrated resources to the Network Deployment 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/ND/bin/WASPostUpgrade
backupDirectoryName
[-instance 5_instance_name]
[-cellName nd_cell_name]
[-nodeName base_node_name]

    The first argument is required. Supported arguments include:

    • backupDirectoryName
      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.

    • -cellName
      Optional parameter to specify the cell name for the program to update. If not specified, the program inspects the configuration for cell names. When one cell name exists, the program uses it. Otherwise, the program returns an error.

    • -nodeName
      Optional parameter to specify the node name for the program to update. If not specified, the program inspects the configuration for node names. When one node name exists, the program uses it. Otherwise, the program returns an error.

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

Start the Version 5 instance that receives the Version 4 configuration

Perform the following steps to start the 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 strwasinst script with the following parameters: 
    /QIBM/ProdData/WebAS5/ND/bin/startServer
-instance 50InstanceName server1

    where 50InstanceName is the name of the Version 5 instance created in an earlier step, and server1 is the name of the Version 5 application server created in an earlier step.