|
Problem(Abstract) |
Sometimes it is necessary to enable additional debugging
or tracing during the installation process for WebSphere® Application
Server V5.0 and V5.1 products. |
|
|
|
Cause |
Some install problems do not generate enough tracing to
help you figure out what is going on. Using the following methods, it
might be possible to get more trace data from the installer software. |
|
|
Resolving the
problem |
The following are some tips for debugging installations.
Base install
- For V5.0 only (not V5.1):
install -W
SetDebugInstall.active="true" >> log.txt |
|
The preceding command will run the install in debug mode.
This is the preferred method of generating traces. |
|
- The following command will generate a install log file that logs all
events.
install -log #
!<log_filename> @ALL |
|
- The following command will create a log file for the native launcher
JVM searches. This is helpful if you are seeing JVM not found errors.
install -is:log
<log_filename> |
|
- Bypass the native launcher
This method bypasses the native launcher. Instead, it invokes java
directly to run the installer. Using this method can help the support team
determine whether the native launcher is contributing to the problem.
However, it is a last effort and is not recommended as a workaround. The
installer will hang once it has finished installing the process, requiring
the operator to manually terminate the java process once the wizard states
that the installation is complete.
For Windows® systems: |
|
jdk\java\bin\java -Dis.debug=1 -cp
setup.jar run >logfilename |
|
For UNIX-based systems: |
|
./jdk/java/bin/java -Xmx512m
-Dis.debug=1 -cp setup.jar run >logfilename |
|
Special note for UNIX®: The -Xmx512m parameter
will increase the heap size to avoid core dumps. This can sometimes help
avoid problems with the Enterprise Edition product. |
|
Maintenance fix install
You need to add shell script (for example: updateWizard.sh) above the
-cp flag, settings for debugging the fix.
- In the updateWizard.bat|sh or silentWizard.bat|sh, add the following
before the -cp entry and to redirect the information to a log
file, add >> mylog.log to the end of the line. This will
set debugging on.
|
-Dcom.ibm.websphere.update.ptf.log.level=9 |
|
OR |
|
-Dis.debug=1 |
|
- For AIX®, to increase the debugging even further, set the following
variables on the system.
ISJELOG=255
JNILOG=1 |
|
Note: Set these variables before running the
install. |
|
- For WebSphere Application Server V5.0.2 Update Installer silent
install only, you can run run the following to get more debug
information:
./updateSilent.sh -verbose=5 |
|
Note: To change the temporary directory of the fix
install, view technote 1116718. |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|