If the value is FALSE, logging to the
Windows™ event log is disabled, and the
windowsEventLoggingLevel and
windowsEventLoggingCategory settings are ignored.
Campaign|partitions|partition[n]|server|logging
This property is used when the value of keepFlowchartLogOpen is
TRUE. Specify a value to indicate the number of messages to buffer before writing to the log. If the value is
1, every log message is written immediately to file, effectively disabling buffering but having a negative impact on performance.
Campaign|partitions|partition[n]|server|logging
A value of TRUE can improve performance of real-time interactive flowcharts. When the value is
TRUE,
IBM® Campaign opens the flowchart log file only once, and closes it when the flowchart's server process exits. A side effect of using the
TRUE value is that recently-logged messages may not be immediately visible in the log file, as
IBM® Campaign flushes the log messages to file only when its internal buffer becomes full or when the number of logged messages equals the value of the
logFileBufferSize property.
If the value is FALSE,
IBM® Campaign opens and closes the flowchart log file.
Campaign|partitions|partition[n]|server|logging
The logProcessId property controls whether the process ID (pid) of the
IBM® Campaign Server process is logged in the log file.
Campaign|partitions|partition[n]|server|logging
The logMaxBackupIndex property specifies the number of backup
Campaign server log files that are kept before the oldest is erased.
If the value is 0 (zero), no backup files are created, and the log file is truncated when it reaches the size specified by the
logFileMaxSize property.
For a value of n, where
n is greater than zero, the files {
File.1, ...,
File.n-1} are renamed to {
File.2, ...,
File.n}. Also,
File is renamed
File.1 and closed. A new
File is created to receive further log output.
1 (creates one backup log file)
Campaign|partitions|partition[n]|server|logging
The loggingCategories property specifies the category of messages written to the
IBM® Campaign server log file. This works in conjunction with
loggingLevels, which determines which messages are logged based on severity (for all selected categories). You can specify multiple categories in a comma-separated list. The special category
all provides a shorthand for specifying all logging categories.
Campaign|partitions|partition[n]|server|logging
The loggingLevels property controls the amount of detail written to the
Campaign server log file, based on severity.
LOW: represents the least detail (the most severe errors only)
ALL: includes trace messages and is intended primarily for diagnostic purposes
|
You may want to set loggingLevels to ALL during configuration and testing. This value generates a large amount of data and therefore may not be advisable for production operation. Setting any logging level higher than its default can adversely affect performance.
|
Campaign|partitions|partition[n]|server|logging
Campaign|partitions|partition[n]|server|logging
Campaign|partitions|partition[n]|server|logging
LOW: represents the least detail (the most severe errors only)
ALL: includes trace messages and is intended primarily for diagnostic purposes.
Campaign|partitions|partition[n]|server|logging
Campaign|partitions|partition[n]|server|logging
A setting of True allows users to change the path through the user interface or when using
unica_svradm to run the flowchart.
A setting of False prevents users from changing the path to which the flowchart log file is written.
Copyright IBM Corporation 2015. All Rights Reserved.
|