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.
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: - 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.
- 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.
- 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
- 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.
- 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:
/QIBM/ProdData/WebSphere/AppServer/V9/ND/bin/manageprofiles -create -profileName JobMgr01
-profilePath /QIBM/ProdData/WebSphere/AppServer/V9/ND/profiles/JobMgr01 -templatePath /QIBM/ProdData/WebSphere/AppServer/V9/ND/profileTemplates/management
-serverType JOB_MANAGER -nodeName JobMgrNode01 -cellName JobMgr01Cell01 -hostName myhost.company.com
- Stop the old job manager. Any jobs that exist within the old job manager database are migrated as part of the
migration.
- 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.
- Run the WASPreUpgrade command. For
example:
/QIBM/ProdData/WebSphere/AppServer/V9/ND/bin/WASPreUpgrade /mybackup/WAS70JobMgrbackup
/QIBM/UserData/WebSphere/AppServer/V9/ND/profiles/AppServer70
-traceString *=all=enabled -tracefile /mybackup/logs/WASPreMigrationSummary.log
- 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.
- 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: 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
- Run the WASPostUpgrade command to restore the saved
job manager configuration into the new Versão 9.0 administrative agent
profile. For
example:
/QIBM/ProdData/WebSphere/AppServer/V9/ND/bin/WASPostUpgrade /mybackup/WAS70JobMgrbackup
-profileName JobMgr01 -backupConfig TRUE -includeApps TRUE -keepDmgrEnabled FALSE
-username myuser -password mypass
- 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.
- 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.
- Change to the new Versão 9.0 job manager profile
bin directory.
- Run the startServer jobmgr command.
- 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.
- 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.