WAS v8.0 > Migration and coexistence > Distributed operating systems


 Scenario 3: Flexible Management: Migrating an admin agent profile and its registered set of managed base application servers

Administrative agent profiles manage multiple base application servers in environments such as development, unit test or that portion of a server farm that resides on a single machine. Before you can migrate managed base application servers from version 7.0 to version 8.0, first migrate the admin agent.

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.

Review the migration planning information. See Knowledge Collection: Migration planning for WAS.

New feature: We can migrate admin agent profiles and the registered set of managed base application servers from v7.0 to v8.0.newfeat

This task describes how to use the command line tools to migrate an admin agent and its associated set of managed base application servers from WAS v7.0 to v8.0. A base application server becomes managed when it is registered with a single admin agent. An admin agent may manage one or more base application servers and must be at the same release level and on the same machine as the base application servers it is managing. Because of this restriction, the admin agents on both the old and new release run simultaneously until all managed base application servers are migrated. The migration of an admin agent does not bring forward its old port values, however, all other configuration data is migrated. Access the v8.0 admin agent console using the WC_ adminhost or WC_ adminhost_ secure ports as defined in the new v8.0 admin agent's serverindex.xml file. Additionally, the v7.0 admin agent must not be shut down or disabled during this procedure. For migrating the managed base application server in a flexible management environment, ensure that the node names are the same on v8.0 and previous releases.

For migrating the managed base application server in a flexible management environment, ensure that the node names are the same on v8.0 and previous releases.

Ensure that your setting for the maximum number of open files is 10000 or greater. If the number of open files is too low, this can cause a variety of migration failures.


Procedure

  1. Install WAS v8.0

  2. Create the target admin agent profile

  3. Ensure that all the "In Progress" jobs are completed on the managed profiles

  4. Stop polling the job manager

  5. Run the WASPreUpgrade command from the new WAS install root bin directory

  6. Verify the console output and the WASPreUpgrade logs for success, warnings, or failure

  7. Run the WASPostUpgrade command from the new WAS install root bin directory

  8. Verify the logs for success

  9. Start the v8.0 admin agent

  10. Migrate managed base application servers

  11. Troubleshooting


Results

You have migrated an admin agent profile and its associated managed base application servers from WAS Version 7.0 to v8.0 using the migration tools. We can stop the v7.0 admin agent and you can assign the Version 7.0 ports to the v8.0 admin agent.











+

Search Tips   |   Advanced Search