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 dmgr
You can migrate a dmgr. 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.
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.
To open this component, click Window > Open Perspective > z/OS Migration Management Tool, and complete the panels as appropriate to your configuration.
- In the IBM BPM product file system, go to the DATASET directory; for example, /was/V8IMbpm3/DATASET. Locate the sample IBM BPM migration
job BPZWMG3D, and take a copy.
The BPZWMG3D 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 also gets migrated.
- Edit your copy of the sample jobs to make use of the parameters generated in step 1 by the WebSphere Customization Toolbox panels.
Add the following parameters to BBOWMDEV in the DATA partitioned data set (PDS):
FROM_ProfileName=default wpsMigEnabledPrivate=true
Also amend the value of the TO_AdminPassword parameter. This value initially shows the encrypted form of the password, and must be amended to show the password in plain text.
- Stop the older version (V7.5, 7.0, or 6.2.0) dmgr.
- Back up the WebSphere Process Server or IBM BPM database. If necessary, you can recover the V7.5, 7.0, or 6.2.0 data later.
- If you have applications that use WebSphere Adapters, extract the application deployment configuration by running the BPMQueryDeploymentConfiguration command from the target_INSTALL_ROOT/bin directory.
For more information about the BPMQueryDeploymentConfiguration command, see BPMQueryDeploymentConfiguration command-line utility.
- Submit the edited sample job BPZWMG3D. Use the administrator user name and password when submitting the job.
- Examine the output in /tmp/migrate/xxxxx/BPZWMG3D.out and /tmp/migrate/xxxxx/dmgr_backup/logs to ensure that the migration completed successfully.
- Manually upgrade the Common, Business Process Choreographer, and Business Space databases. See Manually upgrading the product databases.
- 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 BBODCPY1 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.
Alternatively, run the BBOMDCP job that can be found in the migration CNTL PDS.
- Start the dmgr.
Results
The dmgr is migrated to V8.0.1.
What to do next
Next, migrate each of the managed nodes in the cell.
: Migrating a z/OS ND environment
Next topic: Migrating a managed node
Related tasks:
Manually upgrading the product databases Start and stop dmgrs Starting dmgrs Migrating a managed node