[V5.1 and later]Migrating and coexisting

This topic describes migrating, which is copying the configuration from a previous release of a WAS product into a new release. This topic also describes coexisting, which is running a new release of a WAS product on the same machine at the same time as you run an earlier release.

 

Overview

IBM Support offers tutorials on various WAS installation topics. See WebSphere education on demand: Installation best practices tutorials for more information. One topic describes migration. Another topic describes installing a coexisting WAS product.

Determine if an existing version of WAS is installed on the machine where you plan to install your Version 5.x product.

 

Overview

If you have a previous version, decide whether to copy the configuration and applications of the previous version to the new version. Migration does not uninstall the previous version. The earlier release is still functional but you cannot run both releases at the same time. To run an earlier release and the new release at the same time is coexistence. You must provide non-default port assignments to support coexistence, by selecting the coexistence option during installation. See Migration and coexistence overview for more information.

Coexistence is described as an optional step in the following procedure. Migration is also optional but the steps are not listed as optional. Use the following procedure to migrate applications and configurations:

 

Steps for this task

  1. Prepare to migrate or update product prerequisites and corequisites to supported versions.

    Refer to the Look it up! (<a href=References and specifications)" src="../../reference.gif">   IBM WAS supported hardware, software, and APIs
    http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html site for current requirements.

    [V5.1 and later]Examples include upgrading to the level of DB2 supported in V5.1 and the embedded messaging feature.

    V5.0.0 and V5.0.1 use a level of embedded messaging that is incompatible with the level supported by V5.0.2. To solve this problem, upgrade V5.0.0 or V5.0.1 to V5.0.2 by applying Fix Pack 2.

  2. Prepare to use the migration function of the Installation wizard, to migrate silently, or to migrate using the migration tools.

    You have the option of letting the Installation wizard issue the commands to use the migration tools or you can issue the commands after installation.

    The Installation wizard detects a previously installed version, and displays a coexistence panel. If you choose not to coexist with the existing product, the Installation wizard displays a migration panel. You can select either option or no option.

    1. Start the administrative server of WAS Standard Edition (V3.5.x) or WAS Advanced Edition (V3.5.x or V4.0.x).

      When you start the administrative server, the migration tools can use the XMLConfig tool to export the configuration data repository. It is not necessary that you start the administrative server for WAS Advanced Single Server Edition, V4. The migration tools use the XML Metadata Interchange (XMI) configuration files directly.

    2. Select the migration option and click Next when using the Installation wizard. When using the silent installation method, select the appropriate option.

      Enter a fully qualified path for the backup directory, where the migration tools store and read the saved configuration and other files. During migration, the wizard backs up the old version of the administrative configuration and the user data files, but does not uninstall the old version. The wizard automatically configures the new installation with the previous configuration data and copies some application data to the newer version.

      The Installation wizard uses the WASPreUpgrade migration tool to export the current administrative configuration. After this phase completes, the wizard runs the second phase, which uses the WASPostUpgrade migration tool to convert the backed-up administrative configuration into the new V5.x configuration. You can stop the administrative server of the earlier version after the migration is complete. You must stop the administrative server of the earlier version before starting the V5.x WAS.

      The installation program prompts you for the following information during migration:

      • Backup directory.

      • Currently installed WAS directory. You must install V5.x in a different directory.

    3. Plan to complete the migration after the installation is complete.

      Here is an overview of the tasks that perform to complete the migration:

      1. Stop all servers from the earlier version.

      2. Load existing applications into your development environment and fix any known problems.

      3. Start the Application Servers in the new installation.

      4. Deploy the changed applications in a test environment.

      5. Test all applications thoroughly.

      6. Follow normal test procedures as you move the test environment into production.

      The Installation wizard backs up the earlier version but does not uninstall it, exports the current configuration, and migrates the configuration to the new installation. If errors result when using the WASPreUpgrade tool, the Installation wizard does not run the WASPostUpgrade tool. The wizard displays the WASPreUpgrade.log and the WASPostUpgrade.log files if errors occur.

    4. Migrate the configuration of a previous version to the Network Deployment product using the Installation wizard or during a silent installation. See Migrating V3.5.x and V.4.0.x to Network Deployment and Installing silently for more information.

    5. [V5.1 and later]Migrate the configuration using the migration tools if you prefer a more incremental approach

      The Migrating topic describes migrating from V4.x (little to consider) or V3.5.x (several things to consider). The topic describes differences between V3.5.x and V5.1 that result from the full compliance of V5.1 with Java 2 Platform, Enterprise Edition (J2EE) specifications.

  3. Set up multiple versions of WAS to coexist.

    No run-time conflicts can exist for multiple instances and versions of WAS to run at the same time on the same machine. Potential conflicts can occur in these areas:

    • Prerequisites and corequisites, including the level of the embedded messaging feature
    • Operating system registration
    • Environmental conflicts
    • File system
    • Port assignments

  4. Here are some configuration options:

    1. [V5.1 and later]Run V3.5.x and V5.1 together
    2. [V5.1 and later]Run V4.0.x and V5.1 together
    3. [V5.1 and later]Install V5.1 more than once on the same machine.

 

Results

[V5.1 and later]The migration function migrates all of your resources and applications, but does not migrate entities in your classes directory. As the Installation wizard for the WAS product migrates applications to Version V5.1, it also migrates any applications that use IBM WebSphere Business Integration Server Foundation Edition, V4.0.x.

The base migration removes (from the server configuration) those parts of your configuration that are dependent upon the Integration Server services.

Migration saves the following files in the backup directory.

For V3.5.x:

  • bin/setupCmdLine.sh (or bin/setupCmdLine.bat for Windows platforms)
  • classes (not saved for iSeries)
  • deployableEJBs (Advanced Edition only)
  • deployedEJBs (Advanced Edition only)
  • hosts
  • properties
  • servlets

For V4.0.x:

  • bin/setupCmdLine.sh (or bin/setupCmdLine.bat for Windows platforms)
  • classes (not saved for iSeries)
  • config
  • installableApps
  • installedApps (by default unless overriden within a specified developer configuration file)
  • installedConnectors (V4.x Advanced Edition only)
  • properties

For V5.0.x:[V5.1 and later]

  • classes (not saved for iSeries)
  • config
  • installableApps
  • installedApps
  • properties

You can coexist with, or migrate the applications and configuration from a previous version of WAS.

 

What to do next

[V5.1 and later]Migration from V5.0.x to V5.1 does not require extensive tuning but does require that you use the new migration tools. Use the tools to migrate an embedded messaging queue manager and a federated node.

[V5.1 and later]Migration from V4.x to V5.1 does not require extensive tuning. Migration from V3.5.x to V5.1 does require that you examine the migrating applications. See Migrating configuration data for a description of fine tuning a migration. Part of the procedure for using the migration tools includes a description of what to tune after using the tools. After migrating, return to Installing the product.

For more information on coexistence among releases, see Migration and coexistence overview.

Related concepts
Migration and coexistence overview
Migrating
Configuration mapping during migration
Related tasks
Installing the product
Creating multiple V5 configuration instances
Related reference
Coexistence support
Port number settings in WAS versions
Default coexistence settings for port numbers
Installation: Resources for learning