Enable remote diagnostic logging at debug
level to Rational Test Control Panel
Note: Available
levels are error, warning, info, debug, and trace. The Java.Util.Logging (JUL)
appender defaults to "level:debug" if level is not set, so all events
are passed to Java.Util and filtered there by the
separate configuration.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.net.NET
Value: level:DEBUG
- Click Apply, OK,
and click New again.
- Under General Properties, enter the following:
Name: greenhat.logappender.jul.JUL
Value: level:DEBUG
- Click Apply and OK.
|
Enable remote diagnostic logging at debug
level to Rational Test Control Panel and
specify the URL for the network log appender.
Note: Available
levels are error, warning, info, debug, and trace. Instead of entering
a specific URL, you can enter url:auto.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.net.NET
Value: url:http://<IP
address or host name>,level:DEBUG
- Click Apply, OK,
and click New again.
- Under General Properties, enter the following:
Name: greenhat.logappender.jul.JUL
Value: level:DEBUG
- Click Apply and OK.
|
Enable remote diagnostic logging at debug
level and internal logging to Rational Test Control Panel.
Note: Available
levels are error, warning, info, debug, and trace.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.net.NET
Value: level:DEBUG
- Click Apply, OK,
and click New again.
- Under General Properties, enter the following:
Name: greenhat.logappender.jul.JUL
Value: level:DEBUG
- Click Apply, OK,
and click New again.
- Under General Properties, enter the following:
Name: greenhat.loginternal
Value: appender
- Click Apply and OK.
|
Enable remote diagnostic logging at error
or warning level to Rational Test Control Panel.
Note: Default
remote log level is warning.
Note: The Java.Util.Logging (JUL)
appender is not present, so there will be no local file logging.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.net.NET
Value: level:WARNING
- Click Apply and OK.
|
Enable console logging at debug level and
use detailed layout.
Note: If Java™ logging
is not enabled, you might want to enable console logging. Console
logging layout can be detailed, standard, or compact.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.console.CONSOLE
Value: layout:detailed,level:DEBUG
- Click Apply and OK.
|
Enable console logging at debug level, use
detailed layout, and log internal framework events.
Note: Internal
events will be sent to the console to help diagnose issues within
the logging framework.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.console.CONSOLE
Value: layout:detailed,level:DEBUG
- Click Apply, OK,
and clickNew again.
- Under General Properties, enter the following:
Name: greenhat.loginternal
Value: console
- Click Apply and OK.
|
Disable all logging.
|
- Click New on the Custom properties page.
- Under General Properties, enter the following:
Name: greenhat.logappender.none
Value: NONENote: You
can enter any value in the Value field because
it will be ignored.
- Click Apply and OK.
|