Migrate to a WebSphere Application Server Version 6.0, Network Deployment 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 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 6.0 profile.
  2. Create a Network Deployment profile.
  3. Add the WebSphere Application Server Version 6.0 profile to the Network Deployment profile.
  4. Add migrated resources to the Network Deployment profile.
  5. Start the Version 6.0 profile that receives the Version 4 configuration.

Migrate Version 4 to a Version 6.0 profile

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

Create a Network Deployment profile

Perform the following steps to create a Network Deployment 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 wasprofile command with the following parameters: 
    install_root/bin/wasprofile -create -profileName 60NDProfileName
-startingPort starting_port_number
-templatePath install_root/profileTemplates/dmgr

    where

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • 60NDProfileName is the name of your WebSphere Application Server Version 6.0, Network Deployment profile.
    • starting_port_number is the first of a block of 10 consecutive ports.

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

Add the WebSphere Application Server Version 6.0 profile to the Network Deployment profile.

Perform the following steps to add the Version 6.0 profile to the Network Deployment 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 startManager script with the following parameters: 
    install_root/bin/startManager -profileName 60NDProfileName

    where:

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/ND
    • 60NDProfileName is the name of your WebSphere Application Server Version 6.0, Network Deployment profile

  3. Run the addNode script with the following parameters: 
    install_root/bin/addNode -profileName 60profile host soapPort -includeapps

    Where:

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • 60profile is the name of the Version 6.0 application server profile that was migrated in an earlier step.
    • host is the host name of the system the Network Deployment profile is running on.
    • soapPort is the SOAP port for the Network Deployment profile.

    If you have already used addNode to add the default profile to a Network Deployment profile, 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 command, see The addNode command.

Add migrated resources to the Network Deployment profile

Perform the following steps to add migrated resources to the Network Deployment 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]

    where

    • /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. It is also the directory where the WasPreUpgrade migration tool writes a log file called WasPreUpgrade.log that chronicles the steps taken by WasPreUpgrade.
    • 60NDProfileName is the name of the Version 6.0 profile to which you are migrating the configuration.

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

Start the Version 6.0 profile that receives the Version 4 configuration

Perform the following steps to start the Version 6.0 profile that receives Version 4 configuration:

  1. Start the Network Deployment profile if it is not already started.
  2. Start the Network Deployment administrative console. For more information, see Start the administrative console for the deployment manager.
  3. Navigate to System Administration --> Node agents.
  4. Verify that the node agent is started. For more information, see Verify that the node agent is running.
  5. If it is not, use the following script to start it: 
    install_root/bin/startNode -profileName 60profile

    where:

    • install_root is /QIBM/ProdData/WebSphere/AppServer/V6/Base or /QIBM/ProdData/WebSphere/AppServer/V6/ND.
    • 60profile is the name of the new Version 6.0 profile.

  6. Once started successfully, start application server from Network Deployment administrative console. Navigate to Server --> Application Servers. Select your server, and then click Start.