Migrating a job manager profile and its registered set of servers

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 at Knowledge Collection: Migration planning for WebSphere Application Server.

Tip: Rather than specifying individual parameters on migration commands, you can specify the -properties file_name.properties parameter to input a properties file. For more information, see Defining your migration through properties.

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 previous releases.
  3. 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.
gotcha

Procedure

  1. Install WebSphere Application Server, Network Deployment Versão 9.0 onto the target host in a new directory.

    For more information, see the installation documentation.

  2. Create a Versão 9.0 job manager profile that will be the target of the job manager migration.

    Run the manageprofiles command with the appropriate parameters to create a new job manager profile.

    For example:
    C:\WebSphere\AppServer90\bin>manageprofiles.bat -create -profileName JobMgr01 
    -profilePath C:\WebSphere\AppServer90\profiles\JobMgr01 -templatePath C:\WebSphere\AppServer90\profileTemplates\management 
    -serverType JOB_MANAGER -nodeName JobMgr01Node01 -cellName JobMgr01Cell01 -hostName localhost
  3. Stop the old job manager. Any jobs that exist within the old job manager database are migrated as part of the migration.
  4. Save the current job manager configuration to the migration backup directory by running the WASPreUpgrade command from the new WebSphere Application Server install root bin directory.

    The WASPreUpgrade command does not make any changes to the old configuration.

    1. Run the WASPreUpgrade command. For example:
      C:\WebSphere\AppServer90\bin>WASPreUpgrade.bat C:\WAS70JobMgrbackup C:\WebSphere\AppServer70 -oldProfile JobMgr01 
      -traceString *=all=enabled -tracefile C:\WAS70JobMgrbackup\logs\WASPreMigrationSummary.log
    2. Review warnings or errors in the console output and WASPreUpgrade logs. After the WASPreUpgrade command is complete, check the console output for Failed with errors or Completed with warnings messages. Then, check the following log files for any warnings or errors:
      • migration_backup_dir/logs/WASPreMigrationSummary.log
      • WASPreUpgrade.timestamp.log
      • WASPreUpgrade.trace

      If there are errors, fix the errors and run the WASPreUpgrade command again. Check whether the warnings affect any other migration or runtime activities on Versão 9.0.

      If the command completed successfully, it is not necessary to check the logs for errors or warnings.

  5. Restore the previous job manager configuration Run the WASPostUpgrade command from the new WebSphere Application Server install root bin directory to restore the previous job manager configuration that you saved in the migration backup directory.
    Evitar Problemas Evitar Problemas: To avoid database inconsistencies, run WASPostUpgrade immediately after WASPreUpgrade completes. As part of WASPreUpgrade, a backup of the database is created. If you restart the old job manager before running WASPostUpgrade, the database in the backup and the database in the old job manager will be out of sync.gotcha
    1. Run the WASPostUpgrade command to restore the saved job manager configuration into the new Versão 9.0 administrative agent profile. For example:
      C:\IBM\WebSphere\AppServer90\bin>WASPostUpgrade.bat C:\WAS70JobMgrbackup -oldProfile JobMgr01 -profileName JobMgr01 
      -traceString *=all=enabled -tracefile C:\WAS70JobMgrbackup\logs\WASPostMigrationSummary.log -username myuser -password mypass
    2. Review warnings or errors in the console output and WASPostUpgrade logs. After the WASPostUpgrade command is complete, check the console output for Failed with errors or Completed with warnings messages. Then, check the following log files for any warnings or errors:
      • migration_backup_dir/logs/WASPostMigrationSummary.log
      • WASPostUpgrade.target_profile_name.timestamp.log
      • WASPostUpgrade.target_profile_name.trace

      If there are errors, fix the errors and run the WASPostUpgrade command again. Check whether the warnings affect any other migration or runtime activities on Versão 9.0.

      If the command completed successfully, it is not necessary to check the logs for errors or warnings.

  6. Start the Versão 9.0 job manager and 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.
      Note: Esse tópico faz referência a um ou mais arquivos de log do servidor de aplicativos. Como uma recomendação alternativa, é possível configurar o servidor para usar a infraestrutura de log e rastreio do High Performance Extensible Logging (HPEL) em vez de usar os arquivos SystemOut.log , SystemErr.log, trace.log e activity.log em sistemas distribuídos e IBM® i. Também é possível usar HPEL em conjunção com os recursos de criação de log z/OS® nativos. Se você estiver usando HPEL, será possível acessar todas as informações de log e rastreio usando a ferramenta de linha de comandos LogViewer a partir do diretório bin do perfil do servidor. Consulte as informações sobre a utilização do HPEL para resolução de problemas dos aplicativos para obter mais informações sobre o uso do HPEL.
  7. 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:07
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-dist&topic=tmig_migrate_job_mgr
Nome do arquivo: tmig_migrate_job_mgr.html