2.4.  Troubleshoot the installation (e.g., identify and analyze log files.)


Troubleshooting installation

The installer program records the following indicators of success in the logs:

Return codes:


  1. Run the installation verification test (IVT).

  2. Run the installver.sh command to calculate and compare checksums for all installed components to the bill of materials list for the product.

    Compare the output from the installver.sh command to the installation log files that are described in the next step.

  3. Check the installation log files for errors after installing:

    The app_server_root/logs/install/log.txt file and the app_server_root/logs/manageprofiles/profile_name_create.log file record installation and profile creation status.

    If the error happens early in the installation, look for the log.txt file in the system temporary area.

    • user_home/waslogs/log_date_stamp.time_stamp.txt if installation finishes but is unsuccessful or for some other reason cannot be copied to app_server_root/logs/install/log.txt

    • user_home/waslogs/log.txt if installation is interrupted

    The installation program copies the log from the temporary area to the logs directory at the end of the installation.

    During installation, a single entry in the app_server_root/logs/install/log.txt file points to the temporary log file, /tmp/log.txt on platforms such as AIX or Linux. The installation program copies the file from the temporary directory to the app_server_root/logs/install/log.txt location at the end of the installation.

    If the installation fails and the app_server_root/logs/install/log.txt file has only this one pointer to the temporary directory, open the log.txt file in the temporary directory. The log might have clues to the installation failure.

    Uninstalling creates the app_server_root/logs/uninstall/log.txt file.

  4. Determine whether the installation problem is caused by a failing ANT script.

    The app_server_root/logs/install/instconfig.log file indicates ANT configuration problems that could prevent the product from working correctly.

  5. Verify that no files exist in the app_server_root/classes directory.

  6. Uninstall the product, if possible, and reinstall after turning on tracing if the error logs do not contain enough information to determine the cause of the problem.

  7. Use the command line method to start the application server.

  8. Verify whether the server starts and loads properly by looking for a running Java process and the "Open for e-business message" in the SystemOut.log and SystemErr.log files.

    You can find the SystemOut.log and SystemErr.log files in the profile_root/logs/server1 (platforms such as AIX or Linux) directory in an Application Server profile.

  9. Start the Snoop servlet to verify the ability of the Web server to retrieve an application from the Application Server.

    Test the internal HTTP transport provided by the Application Server:


    Test the Web server plug-in:


  10. Start the WebSphere Application Server administrative console:


  11. Resolve any IP address caching problems.

Professional hosting         Free 'Oracle Certified Expert Web Services Developer 6' Guide     Free SCDJWS 5.0 Guide