Migrate V5.x Express to a stand-alone V6 Application Server

You can migrate the configuration from V5.x WebSphere Application Server - Express to WAS Network Deployment, V6.

 

Before you begin

This topic describes how to use the V6 migration tools to migrate your applications and configuration from V5 WAS - Express to a stand-alone Application Server in the V6 Network Deployment product.

 

Procedure

  1. Use the V6 Migration wizard to transfer configuration settings from V5 Express to the V6 stand-alone Application Server.

    1. Start the First steps console at the end of installation, or by issuing the following command from the firststeps directory:

      • ./install_root/firststeps/firststeps.sh

      • install_root\firststeps\firststeps.bat

    2. Start the Migration wizard from the First steps console.

    The Migration wizard uses the WASPreUpgrade command line tool and the WASPostUpgrade command line tool to migrate the data and applications from V5 to V6.

    This step transfers applications and configuration information for the V5 Express server resources, security, variables, and virtual hosts to the V6 stand-alone Application Server. All stored information is in XML files in the install_root/config/cells directory of each product. For a full description of each XML file, see the Configuration documents and Configuration document descriptions topics in the information center.

    The WASPreUpgrade command line tool saves selected files from the /bin directory to a backup directory you specify on a wizard panel. Migration saves files from the following directories to the backup directory:

    • classes (This directory is not saved for iSeries platforms.)

    • config

    • installableApps

    • installedApps (or an alternate directory specified by the user)

    • properties (A subset of files in this directory is saved for iSeries platforms.)

    Later, the Migration wizard uses the WASPostUpgrade migration tool to restore the environment in the backup directory into the V6 stand-alone Application Server installation.

  2. Resolve port differences.

    The Migration wizard displays a list of ports for Express. If the same port is used for more than one purpose, the Migration wizard will print a warning message (with a prefix ending in "W:"). This message signifies that a custom port from the V5 Express configuration is part of the default V6 destination profile. The Migration wizard does not resolve these port conflicts automatically; it gives a warning that the server may not function properly until the port conflicts are resolved.

    Two groups of port differences can remain within port assignments in the virtual hosts file, at the cell level:

    • HTTP transport chains

      WebSphere Application Server and Express use different HTTP transport ports by default. To maintain port assignments used by Express when migrating to the base WAS product, add the Express port values at the server level:

      1. In the WAS administrative console, click the plus sign ("+") next to Servers

      2. Click Application Servers.

      3. Click the server on which you plan to install your applications.

      4. Click Web Container settings.

      5. Click Web container transport chains.

      6. Use Studio Site Developer to find the original V5 Express remote server HTTP transport ports:

        1. Display the Server Configuration view.

        2. Double-click the Express remote server that you are migrating.

        3. Click Ports.

        4. View ports defined under Server Settings.

      7. Click New in the V6 WAS administrative console to create additional entries needed to define a port.

    • Advanced ports

      There are a number of special purpose ports defined for Express. These ports are described in the Migrating and coexisting topic. Use non-conflicting values to continue to run both V5 Express and V6 Express on the same system (coexistence), or if WAS applications are dependent on the port values.

      V6 Express port values might require you to change applications. Change any references to port values that are changing. To identify Express applications that require port changes, modify the port configuration on the V5 Express installation to use V6 port values. Test the applications that you intend to migrate to identify port references that are in error.

      1. In the WAS administrative console, click the plus sign ("+") next to Servers.

      2. Click Application Servers to get a list of servers.

      3. Click the server on which you intend to install the applications.

      4. Click Ports.

      5. Use Studio Site Developer to find the original V5 Express remote server port assignments:

        1. Display the Server Configuration view.

        2. Double click the Express remote server that you are migrating.

        3. Click Ports.

        4. View Advanced Ports defined under Server Settings.

  3. Verify migrated applications.

    To verify that applications are installed successfully:

    1. Click Enterprise Applications in the administrative console.

    2. Check your migrated applications.

    3. Click Start.

    Verify that your applications start successfully.

 

Result

You can successfully migrate applications to the the V6 stand-alone Application Server profile in the Network Deployment product.

 

What to do next

Return to Migrating product configurations to continue.


 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.