Migrate a large ND configuration with a large number of applications

 

+

Search Tips   |   Advanced Search

If you have an existing WAS V5.x or 6.0.x 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 V5.x or 6.0.x deployment manager configuration to a Version 6.1 profile but defer adding applications to the V6.1 profile so that you can continue managing the environment using the V5.x or 6.0.x deployment manager.

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 V6.1 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 deployment manager, and once to synchronize the deployment manager 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 V6.1 file.

See Overview of migration, coexistence, and interoperability and Premigration considerations.

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

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

 

Procedure

  1. Verify the WAS V5.x or 6.0.x deployment manager is running and managing the existing environment, and make sure that no V6.1 deployment manager is running.

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

  2. Run the WASPreUpgrade command.

    • Run the WASPreUpgrade command from the Version 6.1 app_server_root/bin directory.

    • Name of the V5.x or 6.0.x migration backup directory.

    • Name of the V5.x or 6.0.x ND installation.

    For example:

    WASPreUpgrade /WAS5.0_backup_directory /WAS5.0_install_directory

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

  3. Run the WASPostUpgrade command.

    • Run the WASPostUpgrade command from the Version 6.1 app_server_root/bin directory.

    • Name of the V5.x or 6.0.x migration backup directory.

    • Specify -includeApps script.

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

    • Specify -keepDmgrEnabled true.

    • Specify any other options that you want.

    For example:

    WASPostUpgrade /WAS5.0_backup_directory -profileName dmgr_profile_name -includeApps script -keepDmgrEnabled true

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

    At this point, you can exit the maintenance window and still manage the environment using the WAS V5.x or 6.0.x deployment manager.

  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 V6.1 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 V6.1 deployment manager.

  6. Stop the WAS V5.x or 6.0.x deployment manager.

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

    You can do this in a number of ways. One easy way is to rename the serverindex.xml file in the node directory of the V5.x or 6.0.x deployment manager to something else.

  7. Start the WAS V6.1 deployment manager. Start the deployment manager from its profile_root/bin directory. For example:

    startManager

 

Results

At this point, the WAS V6.1 deployment manager should be running and the normal application synchronization should occur. You can follow either of the following procedures: