Setting the log level

The log level determines the amount of detail that the Web GUI writes to the log files. As supplied, the product logs all events of the Information severity and above. Use these procedures to change the level if required.

About this task

You can change the log in either of the following ways:
  • Setting the log level in the server initialization file
  • Using the WebSphere administration console

Editing the server initialization file

Procedure

To change the logging level in the server initialization file:

  1. Log in to the machine running the Web GUI using a command line interface.
  2. Open WEBGUI_HOME/etc/server.init in a text editor.
  3. Locate the trace.level property.
  4. Change its value to the required minimum severity level to write to the log files

    The available log levels, in ascending order of ascending severity, are:

    • FINEST
    • FINER
    • PROFILE
    • FINE
    • CONFIG
    • INFO
    • WARNING
    • SEVERE
  5. Save the file.
  6. Restart the Dashboard Application Services Hub server.

Using the WebSphere administration console

Procedure

You can also use the WebSphere administration console. Use this method when diagnosing an issue with the help of IBM Technical Support. To set the logging level using the WebSphere administration console:

  1. Log in to the Web GUI as an administrative user.
  2. Click Console Settings > WebSphere Admin Console.
  3. On the Web Sphere Admin Console page, click Launch WebSphere Admin Console.

    The console opens in a new browser window.

  4. Click Troubleshooting > Logs and Trace.
  5. In the Logging and Tracing page, click the name of the Dashboard Application Services Hub (for example, server1).
  6. Click Change Log Detail Levels.
    Click the Runtime tab to enable tracing for the Dashboard Application Services Hub process that is currently running. Enabling tracing from the Runtime tab will keep tracing active until the next time the Dashboard Application Services Hub server process is stopped. To make tracing persistent even after stopping and restarting the server process, click the Configuration tab instead.
  7. Clear the trace string in the Groups box and replace it with the following string: 
    *=info: com.ibm.tivoli.ncw.*=finest: com.micromuse.dash.*=finest: com.micromuse.ncw.*=finest: com.micromuse.wave.*=finest
  8. Click Apply and close the WebSphere administration console window.