WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate WAS ND configurations


Migrate a large WAS ND configuration with a large number of applications

If we have an existing WAS v6.x WAS ND configuration with a significant number of large applications and meet a specific maintenance window for migration, you might have some difficulty if you use the standard migration scenario. In this case, you might want to copy the resources in the configuration tree from a Version 6.x dmgr configuration to a v8.0 deployment-manager management profile but defer adding applications to the v8.0 profile so that you can continue managing the environment using the v6.x dmgr.

Supported configurations:

This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

Tip: To avoid possible connection-timeout problems, modify the connection-timeout value before running the WASPostUpgrade command to migrate the federated nodes in a cell containing many small applications, a few large applications, or one very large application. If you use a SOAP connector, for example, perform the following actions:

  1. Go to the following location in the v8.0 directory for the profile to which you are migrating your federated node: 
    PROFILE_ROOT/properties

  2. Open the soap.client.props file in that directory and find the value for the com.ibm.SOAP.requestTimeout property. This is the timeout value in seconds. The default value is 180 seconds.
  3. Change the value of com.ibm.SOAP.requestTimeout to make it large enough to migrate the configuration. For example, the following entry would give you a timeout value of a half of an hour: 
    com.ibm.SOAP.requestTimeout=1800

    Select the smallest timeout value that will meet your needs. Be prepared to wait for at least three times the timeout that you select—once to download files to the backup directory, once to upload the migrated files to the dmgr, and once to synchronize the dmgr with the migrated node agent.

  4. Go to the following location in the backup directory that was created by the WASPreUpgrade command: 
    backupDirectory/profiles/profile_name/properties

  5. Open the soap.client.props file in that directory and find the value for the com.ibm.SOAP.requestTimeout property:
  6. Change the value of com.ibm.SOAP.requestTimeout to the same value that you used in the v8.0 file.

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 WAS.

We can use this strategy to satisfy your specific maintenance-window requirement by building the full WAS v8.0 WAS ND configuration in the background while the existing topology is still running and being managed.

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


Procedure

  1. Make sure that the WAS v6.x dmgr is running and managing the existing environment, and make sure that no v8.0 dmgr is running.

    This is important in order to prevent two different dmgrs from trying to manage the same environment.

  2. Run the WASPreUpgrade command.

    • Run the WASPreUpgrade command from the v8.0 WAS_HOME/bin directory.

    • Specify the name of the v6.x migration backup directory.

    • Specify the name of the v6.x WAS ND installation.
    • Optional: Specify the name of a specific instance or profile to be migrated from a previous version of WAS.
    • Optional: Specify the location of user preferences for the administrative console for one or more profiles.

    For example: 

    WASPreUpgrade /WAS6.1_backup_directory /WAS6.1_install_directory

    For a full explanation of the WASPreUpgrade command and its parameters, read WASPreUpgrade command.

  3. Run the WASPostUpgrade command.

    • Run the WASPostUpgrade command from the v8.0 WAS_HOME/bin directory.

    • Specify the name of the v6.x migration backup directory.

    • Specify -includeApps script.

      This will not migrate the applications, but it will create some scripts that you can run later to install the applications

    • Specify -keepDmgrEnabled true.

    • Specify any other options that you want.

    For example: 

    WASPostUpgrade /WAS6.1_backup_directory -profileName dmgr_profile_name
  -includeApps script -keepDmgrEnabled true

    For a full explanation of the WASPostUpgrade command and its parameters, read WASPostUpgrade command.

    At this point, you can exit the maintenance window and still manage the environment using the WAS Version 6.x dmgr.

  4. Customize the administration files.

    1. Go to the migration backup directory location that contains the generated administration files.
    2. Combine and tailor the administration files as needed.

      This might include grouping applications together in some administration files or specifying the installedApplications directory using the installed.ear.destination parameter .

  5. Run the wsadmin command to install the applications.

    • Install the applications in the v8.0 configuration during either normal operations or in applicable maintenance windows.

    • Specify -conntype NONE. For example: 
      wsadmin -f application_script -conntype NONE

    After all applications have been installed, you are ready to start using the WAS v8.0 dmgr.

  6. Stop the WAS Version 6.x dmgr.

    This is important in order to prevent two different dmgrs from trying to manage the same environment.

    We can do this in a number of ways. One easy way is to rename the serverindex.xml file in the node directory of the v6.x dmgr to something else.

  7. Start the WAS v8.0 dmgr.

    Start the dmgr from its PROFILE_ROOT/bin directory. For example: 

    startManager


Results

At this point, the WAS v8.0 dmgr should be running and the normal application synchronization should occur.

We can follow either of the following procedures:

+

Search Tips   |   Advanced Search