WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Tip: The BBOWMG3x job is long running and can cause certain error
conditions (such as an ABEND 522). TIME=NOLIMIT on the JCL job card
should avoid the problem. Also note that the BBOWMG1x and BBOWMG2x
jobs are only needed if you have any XA connectors defined in your
configuration. They do not apply to the deployment manager node migration.
Note: This table is intended to give you an overview on the tasks of each job,
not as a manual. For a detailed step-by-step migration guide, we suggest
printing the Migration Instruction created by the MMT. (See Figure 15-3 on
page 494 for the information how to access the Migration Instruction)
Job BBOWMG3x
The BBOWMG3x job is the job that actually performs the migration. It is the job
that will take the longest time to be processed. Listed below are the steps
included in the job:
1. Create working directory (/tmp/migrate/nnnnn)
2. WRCONFIG: Copy dialog generated variables to the HFS.
3. WRRESP: Create a profile creation response file from dialog generated
variables.
4. MKCONFIG: Gather information from existing configuration (for instance, cell
name, server name).
5. VERIFY: Verify the variables generated from dialog.
6. CRHOME: Create a V7 WAS_HOME structure.
7. CRPROF: Create V7 default profile.
8. PREUPGRD: Backup some files in the HFS to be used by WASPostUpgrade.
9. UPGRADE: Run WASPostUpgrade to perform the migration (serverindex.xml
renamed to serverindex.xml__disabled).
10.FINISHUP: Run Config2Native, update file permissions and attributes.
A working directory in /tmp is used to do much of the processing. The nnnnn is a
unique number that was generated during the creation of your migration jobs. For
normal migration, the space used in /tmp is small, but if you turn on tracing, the
space used can be quite large. Make sure you have enough free space on /tmp.
The UPGRADE step is where the actual migration occurs and will take the
longest to complete. The VERIFY step attempts to check the information
provided so that the migration does not fail because of bad input parameters.
498 WebSphere Application Server V7.0: Concepts, Planning, and Design