Before you migrate a WebSphere Application Server for z/OS Version 5.x or 6.0.x node to Version 6.1.x, you must create JCL jobs (CNTL and DATA data sets) that you will run on z/OS during the actual migration. You must create these jobs before you can begin the actual migration. Walk through using the migration option within the Customization Dialog to generate the JCL jobs (CNTL and DATA data sets) for migrating a standalone application server node.
See Overview of migration, coexistence, and interoperability and Premigration considerations.
For help in troubleshooting problems when migrating, see Troubleshooting migration.
Default values can be accepted for all fields and settings except for those that are explicitly identified in the following steps.
ex 'product_hlq.SBBOCLIB(BBOWSTRT)' 'options'
You are taken back to the Standalone Application Server Migration menu.
In the following panels, the migration data collection process begins.
Correctly specifying STEPLIB is essential to a successful migration. It is likely that your Version 5.x or 6.0.x modules are currently in LPA/LNKLST and that you will begin with your Version 6.1.x libraries being defined in STEPLIB.
System Locations (1 of 2) Specify the following V6.1 information, then press ENTER to continue. For some data sets, specify "Y" if they are in STEPLIB. Full Names of Data Sets PROCLIB.: SYS1.PROCLIB Run WebSphere Application Server from STEPLIB (Y/N)? Y SBBOLPA.: WAS610.WAS.SBBOLPA SBBOLOAD: WAS610.WAS.SBBOLOAD SBBGLOAD: WAS610.WAS.SBBGLOAD SBBOLD2.: WAS610.WAS.SBBOLD2
Press Enter to proceed.
System Locations (2 of 2) Specify the following, then press Enter to continue. V6.1 WebSphere Application Server product directory: /usr/lpp/zWebSphere/V6R1
After specifying your Version 6.1.x home directory, press Enter to proceed.
You are taken back to the Define Variables to Migrate a Standalone Application Server Node menu, where option 1 is marked as completed.
The configuration file system is where the configuration for the node being migrated is physically stored. You can choose to use an existing Version 6.1.x file system if you already have an appropriate file system on the node being migrated. If you choose to use an existing Version 6.1.x file system, you need to ensure that the mount point that you specify here is present before running the migration utilities (BBOWMG1B, BBOWMG2B, and so on) that are created through these dialogs. If you choose to create a new Version 6.1.x file system on the node being migrated, the actual creation of the new file system will not occur until you run the BBOMBHFS or BBOMBZFS job during the migration process after you complete this walk-through. See Migrating a standalone application server for more information.
System Environment Customization Specify the following to customize your system environment, then press Enter to continue. WebSphere Application Server for z/OS configuration file system information Mount point....: /WebSphere/V6R1 Name...........: OMVS.WAS.CONFIG.HFS Volume, or '*' for SMS.: * Primary allocation in cylinders...: 250 Secondary allocation in cylinders.: 100 File system type (HFS or ZFS): HFS
After specifying either an existing mount point or a new mount point and the configuration file system type, press Enter to proceed.
You are taken back to the Define Variables to Migrate a Standalone Application Server Node menu, where options 1 and 2 are marked as completed.
Your Version 6.1.x configuration must use different JCL procedures from those used by your Version 5.x or 6.0.x configuration. The migration process creates new Version 6.1.x JCL procedures using the procedure names specified here.
Server Customization (1 of 2) Specify the following to customize your migration, then press Enter to continue. From WebSphere Application Server home directory: /WebSphere/V5R1M0 / AppServer V6.1 WebSphere Application Server home directory: /WebSphere/V6R1 / AppServer Replace Started Procedure Command Names: Y Daemon Procedure name.........: BBO6DMN Controller Procedure name.....: BBO6ACR Servant Procedure name........: BBO6ASR Adjunct Procedure name........: BBO6CRA
After you have specified or left the defaults for all values, press Enter to proceed to the next panel.
Choose to migrate to support script compatibility if you want to minimize impacts to existing administration scripts. If you have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the Version 5.x or 6.0.x configuration definitions, for example, you might want to choose this option during migration.
If you choose to enable tracing, it will remain enabled throughout the entire migration process.
During migration, a backup copy of the Version 5.x or 6.0.x configuration is required. The default location of this backup is already specified, though you can override if needed. You might need to specify a location other than the default if the /tmp file system does not have adequate space to store the backup configuration. If you choose to override the default location of the backup copy, the best practice is to keep the same naming convention and just replace the /tmp portion with another path, /myTemp/migrate for example.
The five-digit migration identifier (55449 in this example) is generated uniquely each time you create the migration jobs. The migration output messages, which you will need to monitor throughout the migration process, are stored in /tmp/migrate/55449. (After migration, the job output in this directory is NOT automatically deleted.) The migration output messages are also appended to the JCL sysout messages, which can be viewed in SDSF.
Choose one of the following options:
/tmp/migrate/55449/nodetype_backup/where nodetype is dmgr, fed, or base depending on the type of node that you are migrating.
wsadmin -f install_ivtApp.ear.jacl
WebSphere Application Server system applications will migrate regardless of the value set here.
Server Customization (2 of 2) Specify the following to customize your migration, then press Enter to continue. Migration Options Migrate to support script compatibility: Y Enable Tracing: Script: N Profile: N PreUpgrade: N PostUpgrade: N Temporary Directory Location: /tmp/migrate Migration Identifier........: 55449 Application Migration Settings: Application Migration Preference: Y (Y/S/P/N) (Y) Migrate and install applications using the Application Installation Directory. (S) Migrate Applications and generate scripts for later installation. (P) Migrate Applications and keep the same application installation directories as the previous version. (N) Do not migrate applications. Application Installation Directory: ==> /WebSphere/V6R1/AppServer/profiles/default/installedApps
Specify values or accept defaults, and press Enter to proceed.
You are returned to the Define Variables to Migrate a Standalone Application Server Node menu.
On the Generate Customization Jobs panel, you can see the names of the .CNTL and .DATA data sets that have been customized based on your previous input.
Generate Customization Jobs This portion of the Customization Dialog generates the jobs you must run after you complete this dialog process. You must complete the customization process before you generate the jobs with this step. If you have not done this, please return to that step. Jobs and data files will get generated into data sets: 'hlq.CNTL' 'hlq.DATA' If you wish to generate customization jobs using other data sets, then exit from this panel and select the "Allocate target data sets" option. All the jobs that will be tailored for you will need a job card. Please enter a valid job card for your installation below. The file tailoring process will update the job name for you in all the generated jobs, so you need not be concerned with that portion of the job cards below. If continuations are needed, replace the comment cards with continuations. Specify the job cards, then press Enter to continue. //jobname JOB (ACCTNO,ROOM),'IBMUSER',CLASS=A,REGION=0M //* //* //*
After you enter an appropriate job card, press Enter.
The generation process runs and presents you with a list of job streams and files that have been created to perform the migration to Version 6.1.x. These jobs do not require any editing; they are to be submitted "as-is" during the migration process.
Processing for data set 'hlq.CNTL' ... Member BBOWMG1B successfully created. Member BBOWMG2B successfully created. Member BBOWMG3B successfully created. Member BBOMBHFS successfully created. Member BBOMBCR successfully created. Member BBOMBCRZ successfully created. Member BBOMBDN successfully created. Member BBOMBDNZ successfully created. Member BBOMBSR successfully created. Member BBOMBSRZ successfully created. Member BBOMBCP successfully created. Member BBOMBINS successfully created. Processing for data set 'hlq.DATA' ... Member BBOWBMPT successfully created. Member BBOWMBRF successfully created. ***
You have now completed the job generation process and are ready to begin the process of migration.
See Migrating a standalone application server for details.