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 Version 7.0 or later to Version 9.0.

Before you begin

Supported configurations:

This topic is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere® Application Server Migration Toolkit.

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)

Avoid trouble:

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 Version 9.0 before you migrate managed base application servers and deployment manager servers to Version 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 Version 9.0 and the previous releases.

Note: Clone migration is not supported for job manager migrations.

Procedure

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.
Install WebSphere Application Server for z/OS® Version 9.0 onto each target host.

For more information, see the installation documentation.
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.

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 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.
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.
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.
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.
Start the Version 9.0 job manager.

Ensure that both Version 7.0 or later and Version 9.0 of the job manager are running.
1. Change to the new Version 9.0 job manager profile bin directory.
2. Run the startServer jobmgr command.
3. Check the SystemOut.log file for warnings or errors.
Migrate the registered servers.
The Version 9.0 job manager can manage Version 7.0 or later registered servers. For the Version 7.0 or later topology to function with the Version 9.0 job manager, you are not required to migrate the registered servers.
For each registered server that you plan to migrate to Version 9.0 perform the following steps:
- If the registered server you want to migrate is a deployment manager, see Migrating deployment managers for z/OS
- If the registered server you want to migrate is a managed base application server, see Migrating an administrative agent profile and its registered set of managed base application servers on z/OS.

Results

You migrated a job manager profile and its associated managed base application servers from WebSphere Application Server Version 7.0 or later to Version 9.0 using the migration tools.