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

Troubleshooting for BBOWMG3x
Because a migration is complex, errors may occur. The main source for errors is
the BBOWMG3x job, described in the previous section. Here are some
troubleshooting tips.
► If the BBOWMG3x job fails, check the output for errors.
– /tmp/migrate/nnnnn/BBOWMG3x.out
– /tmp/migrate/nnnnn/BBOWMG3x.err written to JOBLOG
– /tmp/migrate/nnnnn/logs directory can contain logs named
WAS*Upgrade*.log
► If you need more information, turn traces on. The trace states are disabled by
default. ‘xxxx.DATA(BBOWMxEV)’ has to be updated to enable tracing:
– TraceState=enabled
– profileTrace=enabled
– preUpGradeTrace=enabled
– postUpGradeTrace=enabled
► If the job fails in the VERIFY step, it is most likely that you made an error
when specifying information used to create the jobs. Correct the information
and rerun the job.
► If the job fails after the VERIFY step, you need to delete the WAS_HOME
directory that was created during the failed run, before re-running the job.
Check the original configuration for the serverindex.xml file being renamed to
serverindex.xml_disabled also. This is done to signal that the configuration
has already been migrated, to stop you from inadvertently migrating the node
again. This is done by default but it is possible to change this behavior during
the configuration phase. It is a check box in the z/OS migration management
tool or you can set the keepDMGREnabled parameter to true in the response
file.
15.7.7 Migration considerations for 64-bit mode
WebSphere Application Server V7.0 runs in 64-bit mode. Consider the following.
Application considerations
For code written in pure Java, the general experience is that there are no
changes necessary to the code to run it in a 64-bit application server.
If the application uses the Java Native Interface (JNI) to call a native program,
that native program must be a 64-bit program. Typically, these native programs
will be code written in C or C++, or perhaps LE compliant assembler. This point is
especially important to check for when using in-house applications that use older
native programs.
Chapter 15. Migration 499