$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Troubleshooting > Agent Builder Trace logging IBM Tivoli Monitoring, Version 6.3

Logging configuration

You can configure logging on components of the Tivoli Monitoring Agent Builder.


Tivoli Monitoring Agent Builder logging options can be configured after installation. If you are experiencing problems, IBM Software Support might request that you configure logging and tracing information. The following steps explain how to configure the product to provide logging data.


Parent topic:

Agent Builder Trace logging


Configuration using the IBM Java Logging Toolkit

You can configure trace logs using the IBM Java Logging Toolkit to set the trace level for the appropriate component of the Tivoli Monitoring Agent Builder.


You can do all logging configuration in the IBM Java Logging Toolkit. Access the Eclipse preference window using the following steps:


Procedure

  1. Select Window > Preferences to display the Window toolbar menu.

  2. Click IBM Java Logging Toolkit to display the IBM Java Logging Toolkit window.

    The Logger Configuration table displays the trace configuration for the following components:

    JLog

    IBM Tivoli Monitoring Logger Trace Logger

    KQZGeneratorTrace

    IBM Tivoli Monitoring Generator Trace Logger

    KQZTrace

    IBM Tivoli Monitoring Agent Builder Trace Logger
    The trace level for each component can be set independently to one of the following values. Selecting a trace level causes trace entries of that level and all higher levels to be included in the log file.

    • Error - error messages.

    • Warning - Warnings.

    • Information - Informational messages.

    • Minimum - The Minimum level of tracing provides some information about the program state with only a minimal affect on the performance of the program.

    • Medium - The Medium level of tracing follows the paths of some high-level APIs and their parameters.

    • Maximum - The Maximum level of tracing follows the paths of most of the code and provide a detailed program flow.

    Logging for each component can also be enabled or disabled by selecting On or Off for Logging.

    Figure 1. IBM Java Logging Toolkit

  3. By expanding the IBM Java Logging Toolkit, you can set the following Trace Attributes for each component:

    • Log file Directory

    • Maximum number of revolving trace files

    • Maximum size of each trace file (in KB)

    • Enable trace logging to files

    • Enable trace logging to console

    • Restore Defaults


Customize trace file settings

Use the appropriate output windows to customize the trace file settings.


Access the Eclipse output page by doing the following steps:


Procedure

  1. Click Window to display the Window toolbar menu.

  2. Click Preferences to display the Preferences window.

  3. Click the plus sign next to the IBM Java Logging Toolkit to display the output windows.

  4. Click the appropriate output window to display the output settings for that component.

    The window displays the following information:

    Log file directory

    Specifies the location of the log file directory.

    Maximum number of revolving trace files

    Specifies the number of trace files that are used and reused to store the trace data.

    Maximum size of each trace file (in Kilobytes)

    Specifies the maximum size in KB for each of the revolving trace files.

    Enable trace logging to files

    Check this box to store the trace log data.

    Enable logging to console

    Check this box to send logging information to a development console.

    If you enable this option, you must restart the Tivoli Monitoring Agent Builder as described in the following procedure:

    1. Close the Tivoli Monitoring Agent Builder.

    2. Modify the install_dir/agentbuilder.ini file.

      • On Windows systems, change install_dir/_jre/jre/bin/javaw.exe to install_dir/_jre/jre/bin/java.exe.

      • On Linux or AIX systems, change install_dir/_jre/jre/bin/javaw to install_dir/_jre/jre/bin/java.

    3. Relaunch the Tivoli Monitoring Agent Builder.


+

Search Tips   |   Advanced Search