Migrating a job manager profile and its registered set of servers using the z/OS Configuration Migration Management Tool

You can migrate a job manager profile and its registered set of servers from Versão 7.0 ou posterior to Versão 9.0.

Before you begin

Configurações suportadas 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.

About this task

Job manager profiles can have one or more of the following server types registered:
  • Deployment manager servers
  • Managed base application servers (which are also registered to an administrative agent)
Evitar Problemas Evitar Problemas:
  1. Managed base application servers and deployment manager servers cannot accept jobs from a job manager that is of a previous version. To avoid problems, migrate your job manager profiles to Versão 9.0 before you migrate managed base application servers and deployment manager servers to Versão 9.0.
  2. When migrating the managed base application server or managed deployment manager in a flexible management environment, the node names must be the same in Versão 9.0 and the previous releases.
gotcha

Procedure

  1. Back up the current job manager configuration by running the backupConfig command.

    The backupConfig command saves the job manager configuration to a file that you can use later for recovery purposes.

    1. Change to the job_manager_profile_root/bin directory.
    2. Run the backupConfig command with the appropriate parameters on the job manager. For example:
      /opt/WebSphereV70/profiles/jobMgr01/bin/backupConfig.sh /mybackupdir/jobMgrBeforeV90migration.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 para z/OS® Versão 9.0 onto each target host.

    For more information, see the installation documentation.

  3. Specify the new job manager 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 job manager.

    Evitar Problemas 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
    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 a job manager.
    3. Complete the fields on the subsequent panels using the values from your worksheet.
    4. Review the job manager 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. Stop the job manager that you are migrating. Any jobs that exist within the old job manager database will be migrated as part of the migration.
  5. Run the migration jobs for the administrative agent

    Follow 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.

  6. 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 temporary 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.

  7. Start the Versão 9.0 job manager.

    Ensure that both Versão 7.0 ou posterior and Versão 9.0 of the job manager are running.

    1. Change to the new Versão 9.0 job manager profile bin directory.
    2. Run the startServer jobmgr command.
    3. Check the SystemOut.log file for warnings or errors.
  8. Migrate the registered servers.

    The Versão 9.0 job manager can manage Versão 7.0 ou posterior registered servers. For the Versão 7.0 ou posterior topology to function with the Versão 9.0 job manager, you are not required to migrate the registered servers.

    For each registered server that you plan to migrate to Versão 9.0 perform the following steps:

Results

You migrated a job manager 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.


Ícone que indica o tipo de tópico Tópico de Tarefa



Ícone de registro de data e hora Última atualização: June 20, 2016 0:09
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-zos&topic=tmig_migrate_jobmgr_zos
Nome do arquivo: tmig_migrate_jobmgr_zos.html