WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Troubleshooting installation and configuration

You can diagnose problems when the installation and configuration of WebSphere® ESB is unsuccessful.

About this task

The installer program records the following indicators at the end of the primary log file:
  • INSTCONFSUCCESS: installation was successful
  • INSTCONFPARTIALSUCCESS: installation was partly successful. Some installation actions failed but can be retried.
  • INSTCONFFAILED: installation was not successful. Recovery is not possible.
The primary log file, log.txt, is located in install_root/logs/wbi/install/log.txt on i5/OS®, Linux®, and UNIX® platforms or install_root\logs\wbi\install\log.txt on Windows® platforms, where install_root represents the product installation directory.

If the result is INSTCONFPARTIALSUCCESS or INSTCONFFAILED, continue analyzing the problem by following these steps. (For details on uninstalling any installed portions before reinstalling, see Preparing for reinstallation after a failed uninstallation.)

Procedure
  1. Read any error messages from the installation process.

    See the following topic for an explanation: Error messages: installation and profile creation and augmentation. If the message corresponds to any of those described, correct the problem, clean up any installed portions, and try to reinstall.

  2. Determine which product caused the partial success or failure. Review the install_error.log file located in the install_root/logs/wbi/install directory on Linux, UNIX, and i5/OS platforms or the install_root\logs\wbi\install\ directory on Windows platforms. This file logs errors, warnings, and installation results extracted from the log files for installation of WebSphere Application Server Network Deployment, WebSphere Feature Pack for Web Services, and WebSphere ESB. If profile creation failed or was partially successful during an installation, the results are extracted from the profile log files and included in this file as well.
    Tip: If no files exist in the install_root/logs/wbi/install directory, installation failed early in the process. See the log files in user_home/wbilogs instead.
    Perform one of the following tasks depending on which product did not install properly:
    • If WebSphere Application Server Network Deployment did not install properly, go to step 3.
    • If WebSphere Feature Pack for Web Services did not install properly (and WebSphere Application Server Network Deployment did), go to step 4.
    • If WebSphere ESB did not install properly (and WebSphere Application Server Network Deployment and WebSphere Feature Pack for Web Services did), go to step 5.
  3. If the installation of WebSphere Application Server Network Deployment was not successful, review the install_error.log file for errors. If this file does not provide enough information to correct the problem, check Troubleshooting installation in the WebSphere Application Server Network Deployment information center and use the information found there to correct the problem before attempting to reinstall WebSphere ESB.
    Tip: If a problem occurs during an installation of WebSphere Application Server Network Deployment as part of a WebSphere ESB installation, the installation process will not continue and an error message will be displayed.
  4. If the installation of WebSphere Feature Pack for Web Services was not successful (and installation of WebSphere Application Server Network Deployment was), review the install_error.log file for errors. If this file does not provide enough information to correct the problem, check Troubleshooting Web server plug-ins installation and removal in the WebSphere Application Server Network Deployment information center and use the information found there to correct the problem before attempting to reinstall WebSphere ESB.
    Tip: If a problem occurs during an installation of WebSphere Feature Pack for Web Services as part of a WebSphere ESB installation, the installation process will not continue and an error message will be displayed.
  5. If the installation of WebSphere ESB was not successful (and installation of WebSphere Application Server Network Deployment and WebSphere Feature Pack for Web Services were), review the install_error.log file for errors. If this file does not provide enough information to correct the problem, check other WebSphere ESB installation log files. For information about the names, locations, and descriptions of these log files, see Installation and profile creation log files. Check the log files in this sequence:
    For i5/OS operating system On i5/OS platforms:
    1. log files in the install_root/logs/wbi/install directory
    2. log files in the user_home/wbilogs directory if no files are found in install_root/logs/wbi/install
    3. user_data_root/profileRegistry/logs/manageprofiles/profile_name_create_error.log
    4. user_data_root/profileRegistry/logs/manageprofiles/profile_name_create.log and user_data_root/profileRegistry/logs/manageprofiles/pmt.log
    5. install_root/logs/wbi/installconfig.log (indicates configuration problems that can prevent the product from working correctly). For more information about diagnosing failed configuration scripts, see Diagnosing a failing Ant configuration script.
    6. Any additional log or trace files generated by installation actions. Look in install_root/logs/wbi/install for trace files generated during the installation process. Look in user_data_root/profileRegistry/logs/manageprofiles/profile_name for those generated by profile creation or augmentation. (For more information about install_root and user_data_root locations, see Default installation directories for the product, profiles, and tools.) These files are primarily intended for use by IBM® technical support.
    For Linux operating systemFor UNIX operating system On Linux and UNIX platforms:
    1. log files in the install_root/logs/wbi/install directory
    2. log files in the user_home/wbilogs directory if no files are found in install_root/logs/wbi/install
    3. install_root/logs/manageprofiles/profile_name_create_error.log
    4. install_root/logs/manageprofiles/profile_name_create.log and install_root/logs/manageprofiles/pmt.log
    5. install_root/logs/wbi/installconfig.log (indicates configuration problems that can prevent the product from working correctly). For more information about diagnosing failed configuration scripts, see Diagnosing a failing Ant configuration script.
    6. Any additional log or trace files generated by installation actions. Look in install_root/logs/wbi/install for trace files generated during the installation process. Look in install_root/logs/manageprofiles/profile_name for those generated by profile creation or augmentation. (For more information about install_root and profile_root locations, see Default installation directories for the product, profiles, and tools.) These files are primarily intended for use by IBM technical support.
    For Windows operating system On Windows platforms:
    1. log files in the install_root\logs\wbi\install directory
    2. log files in the user_home\wbilogs directory if no files are found in install_root\logs\wbi\install
    3. install_root\logs\manageprofiles\profile_name_create_error.log
    4. install_root\logs\manageprofiles\profile_name_create.log and install_root\logs\manageprofiles\pmt.log
    5. install_root\logs\wbi\installconfig.log (indicates configuration problems that can prevent the product from working correctly). For more information about diagnosing failed configuration scripts, see Diagnosing a failing Ant configuration script.
    6. Any additional log or trace files generated by installation actions. Look in install_root\logs\wbi\install for trace files generated during the installation process. Look in install_root\logs\manageprofiles\profile_name for those generated by profile creation or augmentation. (For more information about install_root and profile_root locations, see Default installation directories for the product, profiles, and tools.) These files are primarily intended for use by IBM technical support.
  6. If the error logs do not contain enough information to determine the cause of the problem, uninstall the product, clean up any log files or other artifacts that are left behind, turn on tracing, and reinstall.
    • Report the stdout and stderr logs to the console window by adding the -is:javaconsole parameter to the install command:
      • For i5/OS operating system On i5/OS platforms:
        install -is:javaconsole
        Capture the stream to a file with the following commands:
        install -is:javaconsole > captureFileName.txt 2>&1
      • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms:
        install -is:javaconsole
        Capture the stream to a file with the following commands:
        install -is:javaconsole > captureFileName.txt 2>&1
      • For Windows operating system On Windows platforms:
        install.exe -is:javaconsole
        Capture the stream to a file with the following commands:
        install.exe -is:javaconsole > drive:\captureFileName.txt
    • Capture additional information to a log of your choice with the -is:log file_name option.
  7. If you have successfully created a server profile, use the First steps console or the command-line method to start the server.
  8. Verify that 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.

    If no Java process exists or if the message is not displayed, examine the same logs for any miscellaneous errors. Correct any errors and try again.

    You can find the SystemOut.log and SystemErr.log files in the following platform-specific directories:
    • For i5/OS operating system On i5/OS platforms: profile_root/logs/servername
    • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: profile_root/logs/servername
    • For Windows operating system On Windows platforms: profile_root\logs\servername
  9. Use the First steps console or the command-line method to stop the server, if it is running.
  10. If you want to use a Snoop Servlet to verify the ability of the Web server to retrieve an application from WebSphere ESB, see the step "Start the Snoop servlet to verify the ability of the Web server to retrieve an application from the Application Server" in Troubleshooting installation in the WebSphere Application Server Network Deployment documentation.
  11. Start the administrative console. For more information, see Starting and stopping the administrative console.
  12. To resolve any IP address caching problems, see the step "Resolve any IP address caching problems" in Troubleshooting installation in the WebSphere Application Server Network Deployment documentation.

What to do next

On the product support Web site, you can review current information about resolutions to known problems, and you can read documents that can save you time gathering the information that you need to resolve a problem. Before opening a PMR, see the IBM WebSphere ESB support page.


task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_trouble.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).