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 8.0.
Before you begin
Supported configurations: This
topic is about configuration migration, such as migrating deployment
managers and federated nodes in a network deployment environment.
The Application Migration Toolkit for WebSphere Application Server
provides support for migrating applications from previous versions
of WebSphere Application Server to the latest product version. For
information about migrating applications, read more about the Application
Migration Toolkit.
sptcfg
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 6.x or Version 7.x deployment manager
to a Version 8.0 deployment manager.
Procedure
- Print the Migrating a z/OS deployment manager: Checklist, and
use it as you conduct your migration.
- Inventory your applications, and capture key information
as described in Preparing to migrate a WebSphere Application Server, Network Deployment cell for z/OS.
- 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.
- 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 for z/OS Version
8.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:
- Access the install_root/deployment_manager_profile/bin directory.
- Issue the following commands to remove the customRealm value for
the realm.
- wsadmin.sh -conntype SOAP -port port_name -user user_name -password password
- set cell [$AdminConfig list Cell]
- set security [$AdminConfig list Security $cell]
- set localos [$AdminConfig list LocalOSUserRegistry $security]
- $AdminConfig modify $localos [list {"realm" ""}]
- $AdminConfig save
After you complete these steps, realm value is removed.
The error no longer occurs.