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 Versão 7.0 ou posterior
to Versão 9.0, you must
first migrate the administrative agent.
Before you begin
Configurações suportadas: Este
artigo trata da migração da configuração de perfil. Para migrar seus aplicativos para a versão mais recente, use o Kit
de Ferramentas de Migração do WebSphere® Application Server. Para obter
mais informações, consulte o Kit
de ferramentas de migração no WASdev.
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 Versão 7.0 ou posterior
to Versão 9.0.
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 Versão 7.0 ou posterior to Versão 9.0. 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 Versão 7.0 ou posterior, or Versão 9.0 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.
Evitar Problemas: When migrating
the managed base application server in a flexible management environment,
ensure that the node names are the same on
Versão 9.0 and previous releases.
gotcha
Procedure
- 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.
- Change to the administrative_agent_profile_root/bin
directory.
- 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
- For each node in the configuration, change to the
profile_root/bin directory.
- 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.
- Install WebSphere Application Server para z/OS®
Versão 9.0 onto each target host.
For more information, see the installation documentation.
- 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.
Evitar Problemas: The
Versão 9.0 cell name must match
the cell name in the
Versão 7.0 ou posterior configuration. If you create a
profile with a new cell name, then the migration will fail.
gotcha
- Complete the following worksheet: Specifying a deployment manager migration configuration in the z/OS Migration Management Tool: Worksheet
- On the Migration Node Type Selection panel, select Migrate an administrative
agent.
- Complete the fields on the subsequent panels using the values from your worksheet.
- Review the administrative agent migration definition to make sure that all the values are
correct.
- In the WebSphere Application Server para 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.
- Upload the migration jobs to the target z/OS system.
- 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.
- 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.
- 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.
- 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.
- 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.
Evitar Problemas: The
Versão 9.0 cell name must match
the cell name in the
Versão 7.0 ou posterior configuration. If you create a
profile with a new cell name, then the migration will fail.
gotcha
- Complete the following worksheet: Specifying a federated node migration configuration in the z/OS Migration Management Tool: Worksheet
- On the Migration Node Type Selection panel, select Migrate a managed base
application server.
- Complete the fields on the subsequent panels using the values from your worksheet.
- Review the federated node migration definition to make sure that all the values are correct.
- In the WebSphere Application Server para 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.
- Upload the migration jobs to the target z/OS system.
- 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.
Evitar Problemas: - 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.
gotcha
- 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.
- Change to the new Versão 9.0 migrated administrative
agent
Evitar Problemas: 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.
gotcha
- Stop the old Versão 7.0 ou posterior administrative agent.
- Start the new Versão 9.0 administrative agent.
- Start the managed application server.
- Start each managed base application server.
- Register each managed application server with the new administrative agent.
Check the Node Agent logs for errors.
- Start polling the job manager.
For more information, see ManagedNodeAgent command group for the AdminTask object using
wsadmin scripting.
Results
You migrated an administrative agent profile
and its associated managed base application servers from WebSphere
Application Server Versão 7.0 ou posterior to Versão 9.0 using the migration
tools.