Migrating deployment managers for z/OS

Use the available planning information, information on how to generate the migration jobs and instructions, high-level migration checklist, and detailed migration explanation when you migrate deployment managers to WebSphere® Application Server Version 7.0.

Before you begin

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

About this task

Complete this task to migrate a WebSphere Application Server for z/OS® Version 5.1.x or Version 6.x deployment manager to a Version 7.0 deployment manager.

Tip: For help, read Troubleshooting migration.

Procedure

  1. Print the Migrating a z/OS deployment manager: Checklist, and use it as you conduct your migration.
  2. Inventory your applications, and capture key information as described in Preparing to migrate a WebSphere Application Server, Network Deployment cell for z/OS.
  3. Generate a set of migration jobs and instructions.

    Read Preparing to migrate a deployment manager using the z/OS Migration Management Tool and Processing a migration definition using the z/OS Migration Management Tool for information on generating and uploading your migration definition using the z/OS Migration Management Tool.

    Read Using the zmmt command to create migration definitions on z/OS for information on generating migration definitions using the zmmt command.

  4. Follow the customized instructions in the BBOMDINS member of the CNTL dataset that you generated and refer to the information in Migrating a z/OS deployment manager.

Results

After you migrate the deployment manager, use the WebSphere Application Server Version 7.0 administrative console or scripting to administer the migrated deployment manager.

What to do next

If security is enabled in your Version 6.0.2 environment before migration, the LocalOSUserRegistry element in the security.xml file contains the realm="customRealm" value. This realm setting causes the following exception to occur in the controller region log for the previously migrated V6.0.2 deployment manager:

ExtendedMessage: BBOO0220E: HMGR0149E: An attempt to open a connection to
coregroup DefaultCoreGroup has been rejected
Complete the following steps to remove the customRealm value for the realm:
  1. Access the install_root/deployment_manager_profile/bin directory.
  2. Issue the following commands to remove the customRealm value for the realm.
    1. wsadmin.sh -conntype SOAP -port port_name -user user_name -password password
    2. set cell [$AdminConfig list Cell]
    3. set security [$AdminConfig list Security $cell]
    4. set localos [$AdminConfig list LocalOSUserRegistry $security]
    5. $AdminConfig modify $localos [list {"realm" ""}]
    6. $AdminConfig save

After you complete these steps, realm value is removed. The error no longer occurs.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 2:48:53 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tmig_z_dm
File name: tmig_z_dm.html