Migrating to a Version 7.0 deployment manager using the Migration wizard

Use the Migration wizard to migrate from a WebSphere® Application Server Version 5.1.x or Version 6.x deployment manager to Version 7.0.

Before you begin

Read Overview of migration, coexistence, and interoperability and Premigration considerations. For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

Read WASPreUpgrade command and WASPostUpgrade command for descriptions of the parameters related to the information that you need to collect before you begin this procedure. (The Migration wizard prompts you for the information during the migration.)

Before using the Migration wizard, you must have access to the existing WebSphere Application Server Version 5.1.x or Version 6.x deployment manager. You can first use the Profile Management tool or the manageprofiles command to create a valid new target Version 7.0 management profile for a deployment manager if one does not already exist, or you can create a target profile later using the Migration wizard.
Restriction: You cannot use the Profile Management Tool to create profiles for WebSphere Application Server installations on 64-bit architectures except on the Linux for zSeries platform. However, you can use the Profile Management Tool on other 64–bit architectures if you use a WebSphere Application Server 32–bit installation.

During installation, the WebSphere Application Server, Network Deployment product gives you the choice of creating a standalone 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 deployment manager 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 WebSphere Application Server Version 6.0. It is the graphical interface to the primary Version 7.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 WebSphere Application Server Version 5.1.x or Version 6.x deployment manager to the Version 7.0 deployment manager.

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

Tip: Before migrating a WebSphere Application Server Version 5.1.x or Version 6.x deployment manager, use the backupConfig command or your own preferred backup utility to back up your existing configuration if you want 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® WebSphere Application Server Version 7.0 WebSphere Application Server, Network Deployment, and click Migration wizard.
    • Run the following command:
      • [AIX] [HP-UX] [Linux] [Solaris] app_server_root/bin/migration.sh
      • [Windows] app_server_root\bin\migration.bat
  2. Read the Welcome panel to learn about the migration process, and then click Next.
  3. Select or specify a previous version of WebSphere Application Server 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 that you want to migrate, and then click Next.
  5. Select the target profile to which you want 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. You 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 deployment manager migration:
    • The Version 7.0 cell name must match the cell name in the Version 5.1.x or Version 6.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 Version 7.0 deployment manager node name must be the same as the Version 5.1.x or Version 6.x deployment manager node name.
      • The Version 7.0 deployment manager node name must be different from every node name in the Version 5.1.x or Version 6.x configuration.
      Otherwise, the migration fails with the following message:
      MIGR0488E: The deployment manager 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 Version 5.1.x or Version 6.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 WebSphere Application Server Version 7.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. You can then run these files at any point and in any combination after the migration. You 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 your applications, specify where the migrated applications should be located and then click Next.
    You 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 WebSphere Application Server Version 5.1.x or Version 6.x installation and the Version 7.0 installation. If you keep the migrated applications in the same locations as those of the previous version, the following restrictions apply:
      • The WebSphere Application Server 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 Version 5.1.x or Version 6.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 if you want to prevent migration processing from disabling the existing WebSphere Application Server Version 5.1.x or Version 6.x deployment manager, and then click Next.

    If this is selected, you can use the existing Version 5.1.x or Version 6.x deployment manager while the migration is being completed.

    Caution: Select this option with care.
    • The reason that WebSphere Application Server Version 5.1.x or Version 6.x deployment manager configurations normally are stopped and disabled is to prevent multiple deployment managers from managing the same nodes. You must stop the Version 5.1.x or Version 6.x deployment manager before you start using the Version 7.0 deployment manager. The most likely error conditions that will occur if this is not done are port conflicts when the second instance of the deployment manager is started.
    • Selecting 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.
    You 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 if you want to migrate to support script compatibility, and then click Next.
    If you select this option, migration creates the following Version 5.1.x or Version 6.x configuration definitions:
    • Transports
    • ProcessDef
    • Version 5.1.x or Version 6.x SSL
    • Version 5.1.x or Version 6.x ORB service threadpool
    instead of the following Version 7.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 you have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the Version 5.1.x or Version 6.x configuration definitions, for example, you might want to select this option during migration.

    Note: This is meant to provide a temporary transition until all of the nodes in the environment are at the Version 7.0 level. When they are all at the Version 7.0 level, you should perform the following actions:
    1. Modify your administration scripts to use all of the Version 7.0 settings.
    2. Use the convertScriptCompatability command to convert your configurations to match all of the Version 7.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 Version 6.1.x.

  14. Enter the administrative security credentials for the source WebSphere Application Server 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

You can now start the migrated servers in the WebSphere Application Server Version 7.0 environment.

What to do next

You might need to do some things that are not done automatically by the migration tools.
  • Examine any Lightweight Third Party Authentication (LTPA) security settings that you might have used in WebSphere Application Server Version 5.1.x or Version 6.x, and make sure that Version 7.0 security is set appropriately.

    Read the "Lightweight Third Party Authentication" article in the information center for more information.

  • Check the WASPostUpgrade.log file in the logs directory for details about any JSP objects that the migration tools did not migrate.

    If Version 7.0 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.

  • Review your Java™ Virtual Machine (JVM) settings to verify that you are using a heap size of at least 50 for improved startup performance.

    Read the "Java virtual machine settings" article in the information center for more information.

    If you have used a smaller heap size in the past, you can use the default heap size of 50.

  • Configure WebSphere Application Server to use a database.

    For example, you can configure WebSphere Application Server to use DB2®.

  • Verify the results of the automatic Apache Derby database migration, and manually migrate any Apache Derby databases that are not automatically migrated by the tools.

    Read Migrating IBM Cloudscape or Apache Derby databases for more information.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 2:38:49 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=tmig_wizto70dm
File name: tmig_wizto70dm.html