Migrating an administrative agent profile and its registered set of managed base application servers on z/OS

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 or above to Version 8.5, you must first migrate the administrative agent.

Before you begin

Supported configurations Supported configurations:

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

sptcfg

Review the migration planning information. See Knowledge Collection: Migration planning for WebSphere® Application Server.

You can migrate administrative agent profiles and the registered set of managed base application servers from Version 7.0 or above to Version 8.5.

About this task

This task describes how to use the z/OS Configuration Migration Management Tool to migrate an administrative agent and its associated set of managed base application servers from WebSphere Application Server Version 7.0 or above to Version 8.5. A base application server becomes managed when it is registered with a single administrative agent. An administrative 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. z/OS restricts that only the version 7.0 or above, or Version 8.5 administrative agent be running at any one time. The following instructions will tell you when to start and stop the old and new administrative agents. This restriction requires that all managed base application servers be migrated at the same time.

Avoid trouble Avoid trouble: When migrating the managed base application server in a flexible management environment, ensure that the node names are the same on Version 8.5 and previous releases.gotcha

Procedure

  1. Back up the administrative agent and node configuration
  2. Install WebSphere Application Server Version 8.5
  3. Specify an administrative agent migration configuration in the z/OS Migration Management Tool
  4. Ensure that all in-progress jobs are completed on the managed profiles
  5. Stop polling the job manager
  6. Run the migration jobs for the administrative agent
  7. Verify the migration output that is generated
  8. Add STEPLIB statements that include the previous version's load modules to the migrated Daemon's startup proc
  9. Specify a managed application migration configuration in the z/OS Migration Management Tool
  10. Run the migration jobs for the managed base application server
  11. Verify all of the migration output that is generated
  12. Add STEPLIB statements that include the previous version's load modules to the migrated Daemon's startup proc
  13. Change to the new Version 8.5 migrated administrative agent
  14. Start the managed application server

Results

You migrated an administrative agent profile and its associated managed base application servers from WebSphere Application Server Version 7.0 or above to Version 8.5 using the migration tools.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 11:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-zos&topic=tmig_migrate_adminagent_zos
File name: tmig_migrate_adminagent_zos.html