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 later to Version 9.0, you must first migrate the administrative agent.

1. Back up the source administrative agent and node configuration by running the backupConfig command.

   The backupConfig command saves the administrative agent and node configuration to a file that you can use later for recovery purposes.

   1. Change to the administrative_agent_profile_root/bin directory.
   2. Run the backupConfig command with the appropriate parameters on the administrative agent and all managed base application servers.
      For example:

      /opt/WebSphereV70/profiles/v70dmgr01/bin/backupConfig.sh 
      /mybackupdir/v70dmgr01backupBeforeV90migration.zip 
      -username myuser -password mypass -nostop

   3. For each node in the configuration, change to the profile_root/bin directory.
   4. Run the backupConfig command with the appropriate parameters, and save the current profile configuration to a file.
      For example:

      /opt/WebSphereV70/profiles/v70mas01/bin/backupConfig.sh 
      /mybackupdir/v70mas01rbackupBeforeV90migration.zip 
      -username myuser -password mypass -nostop

   Alternately, you can use the PAX command to back up all HFS files. For more information, see Using the z/OS UNIX pax command.

2. Install WebSphere Application Server for z/OS® Version 9.0 onto each target host.

   For more information, see the installation documentation.

3. Specify the new administrative agent migration configuration in the z/OS Migration Management Tool.

   Use the z/OS Migration Management Tool to create a migration definition and upload the jobs for migrating the administrative agent.

   Avoid trouble: The Version 9.0 cell name must match the cell name in the Version 7.0 or later configuration. If you create a profile with a new cell name, then the migration will fail.
   1. Complete the following worksheet:
      Specifying a deployment manager migration configuration in the z/OS Migration Management Tool: Worksheet
   2. On the Migration Node Type Selection panel, select Migrate an administrative agent.
   3. Complete the fields on the subsequent panels using the values from your worksheet.
   4. Review the administrative agent migration definition to make sure that all the values are correct.
      • In the WebSphere Application Server for z/OS migration definition table, select the migration definition that you want to review.
      • Click View.
      • For information about the migration definition, click the Summary, Instructions, or Response file tab.
   5. Upload the migration jobs to the target z/OS system.
4. Ensure that all in-progress jobs are completed on the managed profiles.

   Before you run the WASPreUpgrade command on a managed application server or deployment manager, all in-progress jobs must be complete.

5. If the administrative agent is registered with a job manager, stop polling the job manager.

   For more information about how to stop the job manager, see ManagedNodeAgent command group for the AdminTask object using wsadmin scripting.

6. Run the migration jobs for the administrative agent by following the instructions in the Migration Instructions view of the z/OS Migration Management Tool or in the BBOMAINS member of the CNTL dataset that you uploaded to the target z/OS system.

   The CRPROF (profile create), PREUPGRD (preUpgrade) and UPGRADE steps are all executed during this process.

7. Verify all output created in the working directory of the HFS/ZFS (specified in ZMMT) and all MVS job output created by the batch jobs.

   Verify that you are getting return codes of 0, and review the log files in the migration temp directory on the configuration file system.

   The migration temporary directory is temporary_directory_location/nnnnn, where temporary_directory_location is the directory specified for the temporary directory location and nnnnn is the numeric value generated for the migration identifier when you generated your migration jobs. The default temporary directory location is /tmp/migrate.

8. Specify a managed application migration configuration in the z/OS Migration Management Tool.

   Use the z/OS Migration Management Tool to create a migration definition and upload the jobs for migrating the managed base application servers.

   Avoid trouble: The Version 9.0 cell name must match the cell name in the Version 7.0 or later configuration. If you create a profile with a new cell name, then the migration will fail.
   1. Complete the following worksheet:
      Specifying a federated node migration configuration in the z/OS Migration Management Tool: Worksheet
   2. On the Migration Node Type Selection panel, select Migrate a managed base application server.
   3. Complete the fields on the subsequent panels using the values from your worksheet.
   4. Review the federated node migration definition to make sure that all the values are correct.
      • In the WebSphere Application Server for z/OS migration definition table, select the migration definition that you want to review.
      • Click View.
      • For information about the migration definition, click the Summary, Instructions, or Response file tab.
   5. Upload the migration jobs to the target z/OS system.
9. Run the migration jobs for the managed base application server by following the instructions in the Migration Instructions view of the z/OS Migration Management Tool or in the BBOMDINS member of the CNTL dataset that you uploaded to the target z/OS system.

   The CRPROF (profile create), PREUPGRD (preUpgrade) and UPGRADE steps are all executed during this process.

   Avoid trouble:

   • Ensure that the source administrative agent is running so that application server can be de-registered with the administrative agent.
   • If the managed application server is also registered to a job manager, you must unregister from the job manager before you run a managed application server migration. After the migration is complete, register to the administrative agent and job manager again.
10. Verify all output created in the working directory of the HFS (specified in ZMMT) and all MVS job output created by the batch jobs.

    Verify that you are getting return codes of 0, and review the log files in the migration temp directory on the configuration file system.

    The migration temporary directory is temporary_directory_location/nnnnn, where temporary_directory_location is the directory specified for the temporary directory location and nnnnn is the numeric value generated for the migration identifier when you generated your migration jobs. The default temporary directory location is /tmp/migrate.

11. Change to the new Version 9.0 migrated administrative agent
    Avoid trouble: Be sure all the managed application servers that were registered to the old administrative agent are migrated. These should have all been de-registered during their migration process.
    1. Stop the old Version 7.0 or later administrative agent.
    2. Start the new Version 9.0 administrative agent.
12. Start the managed application server.
    1. Start each managed base application server.
    2. Register each managed application server with the new administrative agent.
    Check the Node Agent logs for errors.
13. Start polling the job manager.

    For more information, see ManagedNodeAgent command group for the AdminTask object using wsadmin scripting.