User's Guide

Troubleshooting the Installation

The Web Health Console installation installs three software components:

• WebSphere Application Server, Advanced Edition, Single Server, 4.0.2
• IBM HTTP Server
• Web Health Console

In order to install WebSphere Application Server, the Web Health Console installation invokes the WebSphere Application Server silent install. This means that, to debug the install, you may need to review several log files.

The primary log for the install is AMW_WAS_Install.log, which is stored in the temporary directory used by InstallShield. In addition, several other logs have useful information. The WebSphere Application Server install, which is executed by the Web Health Console, creates log files at the following location:

• on UNIX: /tmp/install.log
• on Windows:
  • during the install:
    • install_dir/setup.log: this is the IBM HTTP Server install log
    • install_dir/StagingDir/setup.log: this is the WebSphere Application Server install log
  • after the WebSphere Application Server completes:
    • install_dir/logs/wssetup.log

If the installation is not successful, see the following troubleshooting information:

• Make sure that WebSphere Application Server is running:
  • Access http://hostname:9090/admin
  • If this loads the WebSphere Application Server Admin console, then WebSphere Application Server is running correctly
  • If this does not load the WebSphere Application Server Admin console:
    • Check the WebSphere Application Server install log previously indicated
    • Make sure that the WebSphere Application Server application is running:
      • on Windows: check the Services Panel. Make sure that the service "WebSphere Application Server V4 - WebSphere for ITM" is running. If not, attempt to start it using the controls in the Services Panel.
      • on UNIX: check for the WebSphere Application Server process using the ps command on the java process under the WebSphere Application Server install directory. If WebSphere Application Server is not running, try to start it using install_dir/bin/startServer.sh
    • Check the WebSphere Application Server run time logs at: install_dir/logs
• Make sure that the IBM HTTP Server is running:
  • Check the installation logs:
    • on Windows: look in install_dir/setup.log and in install_dir/StagingDir/setup.log
    • on UNIX: look in /tmp/install.log. The IBM HTTP Server install occurs approximately half way through the install.log. The command line used to install IBM HTTP Server is in this log. To find it, look for "IHS install command". Copy that command and attempt to run it manually on the command line.
  • Check if the process is running:
    • on Windows: check the Services Panel. Make sure that the service "IBM HTTP Server" is running. If not, attempt to start it using the controls in the Services Panel. If the service does not start, try to start the Server from the command line by running: install_dir/HTTP_Server/Apache.
      • If the Server runs on the command line but not in a service, check the parameters of the service:
        • Ensure the Login and Password are correct.
        • Ensure the path is correct.
        • If you are using Windows NT 4.0, attempt the following:
          1. Run regedit.
          2. Go to:

             HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/
             IBMHTTPService/Parameters
             

          3. Set the value of ConfigArgs to be blank.

             Note:

             Editing the Windows registry can corrupt the Windows operating system. Attempt the above instructions only if you are knowledgeable about the Windows Registry.

      • If you see errors referring to the Security Library, check the following:
        • Ensure that the IBM Key Management Utility is installed. If it is installed, it shows in Program Files/ibm/gsk5 on the drive where you installed the Web Health Console.
        • Make sure that the environment variable PATH contains the path to the IBM Key Management Utility. For example: PATH=c:\Program Files\ibm\gsk5\lib.
    • on UNIX: Check for the IBM HTTP Server process using the ps command on the http process. If IBM HTTP Server is not running, try to start it using IBM HTTP Server install_dir/bin/apachectl start. If the IBM HTTP Server does not start, look at the log files in IBM HTTP Server install_dir/logs.
• Check that the Web Health Console application is installed correctly:
  • If both WebSphere Application Server and IBM HTTP Server are running correctly but the Web Health Console is still not available, then the Web Health Console is not functioning. At this point do the following:
    1. Launch the WebSphere Application Server Admin Console: http://hostname:9090/ADMIN
    2. Go to Nodes -> yourNodeName -> Enterprise Applications.

       The application "DM Web Health Console" should be present and it should be running.

       • If the application is present but it is not running, try to start it. If it does not start, check the following:
         • Look in the WebSphere logs at install_dir/logs.
         • Look in the Web Health Console logs at:

           c:\Tivoli\AMW\logs\traceDMWebConsole.log or /opt/Tivoli/AMW/logs/traceDMWebConsole.log

       • If the application is not present, check the following:
         • Check (for WebSphere Application Server) install_dir/healthConsole. It should contain the file dm.ear. If the file is not there, then the installation has failed completely. Check the AMW_WAS_Install.log indicated before.
         • Check install_dir/installedApps. It should contain a directory named dm.ear. If it does not contain that directory, then the configuration command failed to run:
           • Check the AMW_WAS_Install.log and install_dir/appInstall.out or install_dir/appInstall.err for details.
           • Attempt to run the following command manually:

             install_dir/bin/SEAppInstall -install install_dir/healthConsole/dm.ear -interactive false

         • Check install_dir/config/server-cfg.xml. It should contain a reference to the Web Health Console. If it does not contain a reference, but the previous step worked, you probably overwrote the file when you logged into the Admin Console. To correct this, stop the WebSphere Application Server by running: install_dir/bin/stopServer[.sh] and execute again the second step in this list.
         • Check the install_dir/config/plugin-cfg.xml. It should contain a reference to the string "dmwhc". If it does not contain a reference, then GenPluginCfg command failed. Look in install_dir/appInstall2.out or install_dir/appInstall2.err for details. Run the following command manually:

           install_dir/bin/GenPlugIn -configFile install_dir/config/server-cfg.xml

         • Restart the server, if you stopped it, by running: install_dir/bin/startServer[.sh]