After you generate JCL jobs for migrating a deployment manager to WebSphere® Application Server for z/OS® Version 8.5, you can perform the actual migration by running those jobs. When you generated your custom migration jobs, you also created customized instructions for preparing and running the migration jobs in the BBOMDINS members of the CNTL dataset that was used to generate your jobs. Follow these customized instructions to complete the process of migrating your deployment manager to Version 8.5.
This article 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.
sptcfgAll other jobs must be submitted by a user ID that has control over the file system.
Migrating a deployment manager from Version 6.1 or later to Version 8.5 redeploys all application binaries when the deployment manager is restarted. This action results in the deployment manager recycling all the applications across the sysplex. This can cause an outage in a sysplex that is set up for high availability if the synchronization settings are not disabled.
For help, read Troubleshooting migration.
Before you perform the migration, Version 8.5 requires a configuration file system to be present for your new configuration. You can run BBOMDHFS or BBOMDZFS to create and mount a new configuration file system, or you can mount one manually. Either way, you must have a configuration file system for your Version 8.5 configuration created and mounted before you proceed. This configuration file system is the target of the migration; your Version 6.1 or later configuration file system is the source.
BBOMDHFS or BBOMDZFS creates a mount point directory, allocates the configuration's file system, and mounts the file system at whatever value you specified for the mount point when you generated you migrations jobs.
Ensure that you have allocated, created, and mounted your configuration file system data sets either manually or using BBOMDHFS or BBOMDZFS before you proceed. The mount point should be owned by the WebSphere Admin ID, and have permissions of at least 755. The new configuration file system structures should be included in BPXPARM so that they will be mounted at the next IPL.
The migration utility BBOMDCP copies the generated JCL procedures to start the servers to the specified procedure library. Your Version 8.5 configuration must use different JCL procedures from those used by your Version 6.1 or later configuration. This utility will update the new Version 8.5 configuration, substituting your new JCL names in place of the names that existed in your original Version 6.1 or later configuration.
Submit BBOMDCP, and verify a return code of 0.
new controller same identity used in JCL name V6.1 or later configuration | | RDEFINE STARTED AZ1DCR.* STDATA(USER(AZDCRU) GROUP(AZCFG) TRACE(YES))
A deployment manager migration does not require bringing the node into and out of Peer Restart and Recovery (PRR) mode as stand-alone application server and federated node migrations do. There are two fewer jobs to submit for a deployment manager migration, therefore, and you are ready to perform the physical migration.
BBOWMG3D is the job that performs the physical migration of the Version 6.1 or later deployment manager to Version 8.5 based on the information that you supplied when you generated your migration jobs. Submit BBOWMG3D. Verify that you are getting return codes of 0, and review the log files in the migration temp 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.
BBOWDPRO creates the WebSphere Application Server home and default profile.
BBOWDPRE runs the migration pre-upgrade process.
BBOWDPOS runs the migration post-upgrade and finish-up (change file permission) processes.
Ensure that all nodes on the deployment manager's LPAR in the same cell are shut down.
WebSphere Application Server for z/OS Version 8.5 requires that the daemon process be at the highest level of code of any of the servers that it manages on the same LPAR. It will be at the Version 8.5 level when the deployment manager is started.
After you migrate all nodes to Version 8.5 and before you remove the previous version's libraries from the system, you must update the daemon JCL procedure. Failure to do so will result in a failure of the daemon to start.
Use the existing commands that you would use to start a Version 6.1 or later application server, but replace the RACF STARTED procedure name with the value that you entered in the deployment manager panel for the controller procedure name when you generated your migration jobs. This command starts the Version 8.5 deployment manager. Wait until the server is finished initializing before proceeding.
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBODMGR