Runtime components : Runtime Tools : Trace Facility : Tasks : Configuring the trace
  
Configuring the trace
The trace configuration in the btt.xml file defines the trace target by BTTLogFactory Implementation class, and defines the trace level for packages and classes.
The traceTargetFactoryImplClass field defines the trace target.
traceTargetFactoryImplClass
 
Trace Target
value of traceTargetFactoryImplClass
Underlying Technical
WAS
com.ibm.btt.base.BTTLogFactoryToWASImp
Java.util.logging
File
com.ibm.btt.base.BTTLogFactoryToFileOrConsoleImp
Console
Common Logging
com.ibm.btt.base.BTTLogFactoryToCommonLoggingImp
Common Logging
Log4J
Display window
com.ibm.btt.base.BTTLogFactoryToDisplayImp
UDTT implementation
For more information about how to use common logging and Log4J, see:
http://commons.apache.org/logging/guide.html and http://logging.apache.org/log4j/
If you want to trace to file, then you must define the traceFileName_WhenTraceToFile filed, otherwise, the trace output is trace to console.
UDTT trace levels are consistent with industry general trace levels: DEBUG, INFO, WARN, ERROR, FATAL. The higher level contains the lower ones. For example, if current level is WARN, then INFO and DEBUG is enabled, while ERROR and FATAL is disabled.
The following table is the trace level map between UDTT trace and other trace facilities.
Trace level map
 
UDTT trace level
WebSphere Application Server trace level
Common Logging
Log4J
Original trace level
FATAL
Fatal
Fatal
Fatal
Severe
ERROR
Severe
Error
Error
Error
WARN
Warning
Warn
Warn
Warning
INFO
Info
Info
Info
Information Display
DEBUG
Detail*
Debug
Debug
Debug AllTypes
Note If trace to WAS, Console, and File, the entry() and exit() correspond to the FINER level of Java logging.
The trace level configuration for packages or classes is defined in btt.xml) If the trace target is WAS, File or Console, the configuration is registered by Java logging API. UDTT trace level configuration is not registered to common logging, so it doesn't affect the trace output of common logging. You can set the configuration of common logging by the way of common logging itself, such as the common-logging.property file.
When tracing to common logging/Log4J, the trace level configuration does not take affect. The trace level should be set by the Log4J configuration itself.
When tracing to WAS, you can also set the level configuration in WAS admin console at runtime. When the UDTT runtime environment starts, the trace configuration can register to WAS and override the trace level setting in WAS admin console. But if you tune the level in WAS admin console dynamically after the UDTT runtime environment is started, the static UDTT trace configuration will be overridden.
Go up to
Tasks