IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Runtime migration procedures > Migrating a z/OS ND environment
Migrating a managed node
When you migrate a managed node, the migration process does not automatically back up the files on the source server, so it is good practice to back up the files on the source server before running the migration.
Before migrating any managed nodes in the cell, first migrate the dmgr.
Procedure
- Generate the WebSphere Application Server migration
jobs and variables from the z/OS Migration
Management Tool component of the WebSphere Customization
Toolbox application.
Only the variables created by the WebSphere Customization Toolbox are used; the jobs are generated but not run.
- In the IBM BPM product file system, go to the DATASET directory; for example, /was/V8IMbpm3/DATASET. Locate the sample IBM BPM migration
jobs BPZWMG1F, BPZWMG2F, and BPZWMG3F, and take a copy.
The BPZWMG1F and BPZWMG2F jobs must be run only if you had XA Connectors installed in the V7.5, 7.0, or 6.2.0 server. The BPZWMG3F job runs the wbimgrt2.sh script, which starts the BPMSnapshotSourceProfile.sh and BPMMigrateProfile.sh migration utilities. As part of wbimgrt2.sh processing, the WebSphere Application Server profile is also migrated.
- Edit your copy of the sample jobs to make use of the parameters generated in step 1 by the WebSphere Customization Toolbox panels.
- Stop the V7.5, 7.0, or 6.2.0 managed node server, but ensure that the dmgr is running.
- Submit the sample jobs that you edited in step 3. Use the administrator user name and password when submitting the jobs.
- Examine the output in /tmp/migrate/xxxxx/BPZWMGxF.out and /tmp/migrate/xxxxx/fed_backup/logs to verify that the migration completed successfully.
- If you have used the same procnames for your source and target servers, update the started task JCL members in USER.PROCLIB by running the BBOMCPY1 job from the jcl library that was generated during the installation process of your WebSphere Application Server target server. This job replaces the V7.5, 7.0, or 6.2.0 started task members with the new V8.0.1 members.
- Start the V8.0.1 managed node from the MVS console.
- Repeat these steps for each managed node in the cluster.
Results
The managed nodes are migrated to the target version.
What to do next
Verify that the migration was successful.
After you have migrated all of your managed nodes, you must then migrate the cluster.
: Migrating a z/OS ND environment
Previous topic: Migrating a dmgr
Next topic: Migrating a cluster
Related tasks:
Migrating a dmgr Starting a server from the MVS console Verifying migration
Related information: