Options for monitoring installation messages

IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Options for monitoring installation messages

The following two configuration options control the display or logging of installation messages. These options can help you monitor and debug all phases of an installation.

-W LogSetting.consoleOut=true | false specifies whether to display messages issued by installation or upgrade program on the console. If you use this option with a native launcher, it must be used in combination with the -is:javaconsole option.
-W LogSetting.logLevel=value specifies the level of tracing for the installation log files. The amount of tracing for a specific level includes the messages for that level and all messages at a higher severity. For example, if you choose the WARNING trace level, the following messages are logged: WARNING, ERROR, and FATAL. During the installation maximum logging is turned on by default. Access the installation log files in the following path: C:\IBM\tivoli\common\CYN\logs.

Trace level settings for installation log files

Option string Description
-W LogSetting.logLevel=FATAL Log fatal messages. A fatal message reports an error from which the program cannot recover. A fatal message is the most severe message.
-W LogSetting.logLevel=ERROR Log error messages. An error message reports a serious failure. An error message is less severe than a fatal message.
-W LogSetting.logLevel=WARNING Log warning messages. A warning message reports that an abnormal condition has occurred. The condition might or might not require the user to take action.
-W LogSetting.logLevel=INFO Log information messages. An information message indicates a condition that is worth noting but does not require the user to take action.
-W LogSetting.logLevel=DEBUG_MIN Log debug messages that provide minimal detail. DEBUG_MIN is appropriate for a software trace that is always running. It provides some information about the program state with only minimal impact to performance. DEBUG_MIN is the default setting for installation log files.
-W LogSetting.logLevel=DEBUG_MID Log debug messages that provide a medium amount of detail. The DEBUG_MID setting produces a level of detail between DEBUG_MIN and DEBUG_MAX.
-W LogSetting.logLevel=DEBUG_MAX Log debug messages that provide the most detail about program execution. Program performance is usually not an issue when debugging in this mode.
-W LogSetting.logLevel=ALL Enable all message logging.

Parent topic:
Configuration options

+
Search Tips | Advanced Search

Option string	Description
-W LogSetting.logLevel=FATAL	Log fatal messages. A fatal message reports an error from which the program cannot recover. A fatal message is the most severe message.
-W LogSetting.logLevel=ERROR	Log error messages. An error message reports a serious failure. An error message is less severe than a fatal message.
-W LogSetting.logLevel=WARNING	Log warning messages. A warning message reports that an abnormal condition has occurred. The condition might or might not require the user to take action.
-W LogSetting.logLevel=INFO	Log information messages. An information message indicates a condition that is worth noting but does not require the user to take action.
-W LogSetting.logLevel=DEBUG_MIN	Log debug messages that provide minimal detail. DEBUG_MIN is appropriate for a software trace that is always running. It provides some information about the program state with only minimal impact to performance. DEBUG_MIN is the default setting for installation log files.
-W LogSetting.logLevel=DEBUG_MID	Log debug messages that provide a medium amount of detail. The DEBUG_MID setting produces a level of detail between DEBUG_MIN and DEBUG_MAX.
-W LogSetting.logLevel=DEBUG_MAX	Log debug messages that provide the most detail about program execution. Program performance is usually not an issue when debugging in this mode.
-W LogSetting.logLevel=ALL	Enable all message logging.