WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate product configurations with migration tools > Migrate product configurations with the migration wizard


Migrate to a v7.0 dmgr using the Migration wizard


Use the Migration wizard to migrate from a WAS v5.1.x or v6.x dmgr to v7.0.

Before using the Migration wizard, have access to the existing WAS v5.1.x or v6.x dmgr. We can first use the Profile Management tool or the manageprofiles command to create a valid new target v7.0 management profile for a dmgr if one does not already exist, or you can create a target profile later using the Migration wizard.

You should have installed v7.0 already.

During installation, the WAS ND gives you the choice of creating a stand-alone application server, a management profile, a cell, a custom profile, or no profile. The Installation wizard also prompts you to use the Profile Management tool at the end of installing the core product files; however, using the Profile Management tool at that time is optional. If the management profile for a dmgr was not created during the installation, you can create one using the Profile Management tool or the manageprofiles command.

The Migration wizard was introduced in WAS v6.0. It is the graphical interface to the primary v7.0 command-line migration tools, which are the WASPreUpgrade command and the WASPostUpgrade command.

After gathering all of the information that is required during the migration, use the wizard to migrate a WAS v5.1.x or v6.x dmgr to the v7.0 dmgr.

For help in troubleshooting problems when migrating, read Troubleshoot migration.

Tip: Before migrating a WAS Version 5.1.x or v6.x dmgr, use the backupConfig command or your own preferred backup utility to back up your existing configuration if to be able to restore it to its previous state after migration. Read the "backupConfig command" article in the information center for more information. Make sure that you note the exact name and location of this backed-up configuration.


Procedure

  1. Start the Migration wizard.

    Perform one of the following actions to access the Migration wizard:

    • Go to Start > Programs > IBM WAS V7.0 WAS ND, and click Migration wizard.
    • Run the following command:

        WAS_HOME/bin/migration.sh

  2. Read the Welcome panel to learn about the migration process, and then click Next.

  3. Select or specify a previous version of WAS from which to migrate, and then click Next.

    Select the check box and enter the location of the previous installation if it does not display in the selection list.

  4. Select the source profile or instance to migrate, and then click Next.

  5. Select the target profile to which to migrate from the list of valid profiles for the installation or select Create new profile, and then click Next.

    Select the check box to create a backup copy of the target profile's configuration before migrating the source profile. If you select the check box, the backup copy of the target profile will be written to PROFILE_ROOT/temp/MigrationBackup.time_stamp.zip. We can use the restoreConfig command to restore the configuration after migration if necessary.

  6. If you selected Create new profile on the last panel, enter the parameters for creating the new profile and then click Next.

    Restrictions for a dmgr migration:

    • The v7.0 cell name must match the cell name in the Version 5.1.x or v6.x configuration.

      If you create a profile with a new cell name, the migration will fail.

    • Either one or the other of the following options must be true:

      • The v7.0 dmgr node name must be the same as the v5.1.x or v6.x dmgr node name.
      • The v7.0 dmgr node name must be different from every node name in the v5.1.x or v6.x configuration.

      Otherwise, the migration fails with the following message: 

      MIGR0488E: The dmgr node name in the new configuration ({0}) cannot be the same
as a nodeagent node in the old configuration.

    If you also use the same node name that you used for the v5.1.x or v6.x cell, the node agents will still work after migration without being restarted.

  7. Specify a migration backup directory in which to place a backup copy of the configuration from the previous version, and then click Next.

    The directory is created if it does not already exist. If the directory exists, it should be empty because the backup operation might overwrite existing backup files.

  8. Select one of the options for migrating the applications installed on the source profile, and then click Next.

    You can choose to do any one of the following with the applications:

    • Include your enterprise applications as part of the migration.
    • Prepare your enterprise applications for installation in the WAS v7.0 installableApps directory without actually installing them during migration processing.

      Scripts that can be used to install these applications are generated and saved in the migration backup directory. We can then run these files at any point and in any combination after the migration. We can also reorganize and combine these files for better applications installation efficiency if you want.

    • Do nothing with your enterprise applications during migration processing.

  9. If you selected the option to install the applications, specify where the migrated applications should be located and then click Next.

    We can choose any one of the following options:

    • Keep the applications in the same directories in which they are currently located.

      Restrictions: If you choose this option, the location is shared by the existing WAS v5.1.x or v6.x installation and the v7.0 installation. If you keep the migrated applications in the same locations as those of the previous version, the following restrictions apply:

      • The WAS Version 7.0 mixed-node support limitations must be followed. This means that the following support cannot be used when evoking the wsadmin command:

        • Precompile JSP

        • Use Binary Configuration
        • Deploy EJB

      • You risk losing the migrated applications unintentionally if you later delete applications from these locations when administering (uninstalling for example) your v5.1.x or v6.x installation.

    • Choose to install the applications in the default directory of the target version.

    • Specify the directory in which to install the migrated applications.

  10. Select the check box to prevent migration processing from disabling the existing WAS v5.1.x or v6.x dmgr, and then click Next.

    If this is selected, you can use the existing v5.1.x or v6.x dmgr while the migration is being completed.

    Caution: Select this option with care.

    • The reason that WAS Version 5.1.x or v6.x dmgr configurations normally are stopped and disabled is to prevent multiple dmgrs from managing the same nodes. We must stop the v5.1.x or Version 6.x dmgr before you start using the v7.0 dmgr. The most likely error conditions that will occur if this is not done are port conflicts when the second instance of the dmgr is started.

    • Select this option means that any configuration changes made in the old configuration during migration might not be migrated.

  11. Select one of the options for setting port values, optionally specify a starting port value for resolving port conflicts, and then click Next.

    We can choose to do either one of the following with the port values:

    • Use the port values assigned to the previous (source) installation.

    • Use the port values assigned to the target profile.

    By default, a port conflict is resolved by incrementing the port number by one until an unused port number is found. Instead, you can specify a starting port number to be used when a conflict is detected. If the starting port number is in use, it will be incremented by one until an unused port number is found.

  12. Select the check box to migrate to support script compatibility, and then click Next.

    If you select this option, migration creates the following v5.1.x or v6.x configuration definitions:

    • Transports
    • ProcessDef
    • Version 5.1.x or v6.x SSL
    • Version 5.1.x or v6.x ORB service threadpool

    instead of the following v7.0 configuration definitions:

    • Channels
    • ProcessDefs
    • Version 7.0 SSL
    • Version 7.0 ORB service threadpool

    Select this option in order to minimize impacts to existing administration scripts. If we have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the v5.1.x or v6.x configuration definitions, for example, you might want to select this option during migration.

    This is meant to provide a temporary transition until all of the nodes in the environment are at the v7.0 level. When they are all at the v7.0 level, you should perform the following actions:

    1. Modify your administration scripts to use all of the v7.0 settings.

    2. Use the convertScriptCompatability command to convert the configurations to match all of the v7.0 settings.

      Read convertScriptCompatibility command for more information.

  13. Specify the administrative console workspace user root directory where the "My Tasks" user information is stored in the previous installation, and then click Next.

    This panel displays only if you are migrating from v6.1.x.

  14. Enter the administrative security credentials for the source WAS installation, and then click Next.

    This panel displays only if security is enabled and if the server user identity is not stored in the repository.

  15. Check the information in the summary panel and make sure that it is correct, and then click Next to start the migration.

  16. If the wizard indicates that the profile-creation process was successful, click Next.

    This panel displays only if you selected the option to create a new target profile.

    If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.

  17. If the wizard indicates that the pre-upgrade process was successful, click Next.

    If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.

  18. If the wizard indicates that the post-upgrade process was successful, click Next.

    If the process is not successful, the wizard displays a failure panel. If the process is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.

  19. If the wizard indicates that the migration was successful, click Next.

    If the process is not successful, the wizard displays a failure panel. If the migration is partially successful, the wizard displays a warning panel. Correct any problems and retry the migration.

  20. Click Next to migrate another profile, or click Cancel to exit the Migration wizard.


Results

We can now start the migrated servers in the WAS v7.0 environment.


What to do next

You might need to do some things that are not done automatically by the migration tools.


Migrate product configurations with the migration wizard
Migrate a v6.x or 7.x federated node
Migrate to a v8.0 dmgr


Related


WASPreUpgrade command
WASPostUpgrade command

+

Search Tips   |   Advanced Search