After the deployment manager is migrated and restarted, you can perform the actual migration of its federated application server nodes by running the Job Control Language (JCL) jobs that you generated. When you generated your custom migration jobs, you also created customized instructions for preparing and running the migration jobs in the BBOMMINS members of the CNTL dataset that was used to generate your jobs. Follow these customized instructions to complete the process of migrating your federated nodes to Version 7.0.
The BBOWMG3F job must be submitted by a user ID that has control over the file system and the user ID must also be a WebSphere Administrator user ID.
All other jobs must be submitted by a user ID that has control over the file system.
Read the "backupConfig command" article in the information center for more information.
Read the "backupConfig command" article in the information center for more information.
If necessary, you can now roll back the federated node that you just migrated. Read Rolling back a federated node for more information.
For help, read Troubleshooting migration.
You must stop the Version 5.1.x or Version 6.x federated node before proceeding.
For the application server node to be properly migrated, the deployment manager must be running. For this migration to work, the deployment manager must be up and listening on its SOAP port.
Check Off | Item |
---|---|
Access the administrative console of the WebSphere Application Server Version 7.0 deployment manager. This validates that the deployment manager is running. |
Check Off | Item |
---|---|
Ensure that the WebSphere Application Server Version 7.0 copy of the code is running. Under "About your WebSphere Application Server," the build number should begin with W70. |
Before you perform the migration, Version 7.0 requires that a configuration file system be present for your new configuration. You can run BBOMMHFS or BBOMMZFS to create and mount a new configuration file system, or you can mount one manually. Either way, you must have a file system for your Version 7.0 configuration created and mounted before you proceed. This configuration file system is the target of the migration; your Version 5.1.x or Version 6.x configuration file system is the source.
BBOMMHFS or BBOMMZFS 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 your migration jobs.
Before you proceed, ensure that you have allocated, created, and mounted your configuration file system datasets either manually or using BBOMMHFS or BBOMMZFS. The mount point should be owned by the WebSphere Administrator user 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.
BBOWMG1F enables all servers on the federated application server node being migrated to start in Peer Restart and Recovery (PRR) mode. PRR processing mode resolves any outstanding transactions, clears the transaction logs, and stops the server. BBOWMG2F disables PRR mode and returns all servers to normal operating state.
BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C218D5
The migration utility BBOMMCP copies the generated JCL procedures to start the servers to the specified procedure library. Your Version 7.0 configuration must use different JCL procedures from those used by your Version 5.1.x or Version 6.x configuration. This utility will update the new Version 7.0 configuration, substituting your new JCL names in place of the names that existed in your original Version 5.1.x or Version 6.x configuration.
Submit BBOMMCP, and verify a return code of 0.
new controller same identity used in JCL name V5.1.x or V6.x configuration | | RDEFINE STARTED AZ1ACR.* STDATA(USER(AZACRU) GROUP(AZCFG) TRACE(YES))
You can use the BBOLOGSD and BBOLOGSA jobs that were created during Version 5.1.x or Version 6.x customization if you configured the server initially to use the log stream.
//RLSP1A JOB 'xxxx,yyy,?','USERID',MSGCLASS=H, // CLASS=J,MSGLEVEL=(1,1),REGION=4M,NOTIFY=&SYSUID //STEP1 EXEC PGM=IXCMIAPU //STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * DATA TYPE(LOGR) REPORT(YES) /* Default to show output of job */ DELETE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D) DEFINE LOGSTREAM NAME(P1ACEL6A.W51ASA2.D) LOWOFFLOAD(20) HIGHOFFLOAD(79) STG_DUPLEX(YES) DUPLEXMODE(UNCOND) STG_DATACLAS(OPERLOG) STG_SIZE(5000) HLQ(Q10RRS) LS_SIZE(5000) LS_DATACLAS(OPERLOG) STRUCTNAME(WAS_LOGRLS) /*
If you are migrating nodes in a sysplex, follow this procedure for each federated node that you migrate.
//*************************************************************** //* //* UPGRADE: Perform the migration to the new Profile //* //*************************************************************** //* //* //UPGRADE EXEC PGM=IKJEFT01,REGION=0M,COND=(4,LE) //SYSTSPRT DD SYSOUT=* //STDENV DD * // _CEE_RUNOPTS=TRAP(ON,NOSPIE) //* //SYSTSIN DD * BPXBATCH SH + export _BPXK_SETIBMOPT_TRANSPORT=TCP; + /tmp/migrate/bbomigrt2.sh WASPostUpgrade + /tmp/migrate/28133744/_ + 1>> /tmp/migrate/28133744/BBOWMG3F.out + 2>> /tmp/migrate/28133744/BBOWMG3F.err; /*
BBOWMG3F is the job that performs the physical migration of the Version 5.1.x or Version 6.x node to Version 7.0 based on the information that you supplied when you generated your migration jobs. Submit BBOWMG3F, verify that you are getting return codes of 0, and review the log files in the temporary migration 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 (/tmp/migrate by default) and nnnnn is the numeric value generated for the migration identifier when you generated your migration jobs.
BBOWMPRO creates the WebSphere Application Server home and default profile.
BBOWMPRE runs the migration pre-upgrade process.
BBOWMPOS runs the migration post-upgrade and finish-up (change file permission) processes.
Ensure that all federated nodes in the same cell on this LPAR are stopped.
WebSphere Application Server Version 7.0 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 7.0 level when this federated node is started.
After you migrate all nodes to Version 7.0 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.
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBON001
Use the existing command that you would use to start a Version 5.1.x or Version 6.x application server, but replace the RACF STARTED procedure name with the value that you entered in the federated node panel for the controller procedure name when you generated your migration jobs. This command starts the Version 7.0 federated application server. Wait until the server is finished initializing before proceeding.
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR z/OS CONTROL PROCESS BBOS001
At this point, your migration to Version 7.0 is complete.
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. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |