enable

You can use one of the following values:

• 1. The general log is enabled.
• 0. The general log is disabled.

To disable the general log file, you must use the registry. You cannot use the Logging Configuration dialog box. For more information, see Assigning a Logging Profile to Oracle CRM On Demand Desktop.

log_level

Defines the level of detail in the log files. You can use one of the following integers:

• 4294967295 — Disables all.
• 0 — Enables all.
• 1000 — Shows debug information.
• 2000 — Shows information messages.
• 3000 — Shows warnings.
• 4000 — Shows errors.
• 5000 — Shows fatal errors.

out_file

You can include a string that identifies the file name of the general log file. For example, assume you use the following value:

log.txt

In this example, the first file name is log.0000.txt, the second file name is log.0001.txt, and so forth. If you do not include the out_file parameter, then Oracle CRM On Demand Desktop uses log.txt as the default value.

enable_dbg_window

You can use one of the following values:

• 1. Enables output through the OutputDebugString that Oracle CRM On Demand Desktop displays in the VS Debug Output window during a debugging session.

  The OutputDebugString is a string that Oracle CRM On Demand Desktop sends to the debugger for display. The VS Debug Output window is a window in Microsoft Visual Studio that displays debugging results. For more information about Visual Studio, see the documentation at the Microsoft TechNet Web site.

• 0. Disables the general log file.

enable_cout

You can use one of the following values:

• 1. Enables logging in the console.
• 0. Disables logging in the console.

max_size_bytes

You can use an integer that sets the maximum number of bytes that a single log file can contain. For example, if you set max_size_bytes to 10485760 bytes, and if the current log reaches 10485760 bytes, then Oracle CRM On Demand Desktop creates a new log file. This behavior is similar to setting the rotate_on_start_only parameter to zero (0).

NOTE:  Log rotation does not occur until Microsoft Outlook is restarted.

reuse_not_exceeded

Determines the file that Oracle CRM On Demand Desktop uses when a new logging session starts. You can use one of the following values:

• 1. If the size of the most current log file is less than the value that the max_size_bytes parameter sets, then Oracle CRM On Demand Desktop reuses this file. The default value is one.
• 0. Oracle CRM On Demand Desktop does not reuse the most current log file.

rotate_on_start_only

Log file rotation is a configuration that Oracle CRM On Demand Desktop uses to limit the size of log files. You can use one of the following values:

• 1. Examines the size of the log file size when Outlook starts. If this log file is larger than the value that the max_size_bytes parameter specifies, then Oracle CRM On Demand Desktop creates a new log file, and then it logs all subsequent entries to this new file. The log file size can exceed the value that the max_size_bytes parameter specifies. Oracle CRM On Demand Desktop stores all log entries for one Outlook session in one file. The default value is 1.
• 0. Examines the size of the log file every time Oracle CRM On Demand Desktop writes to the log file. If this log file size is larger than the value that the max_size_bytes parameter specifies, then Oracle CRM On Demand Desktop creates a new log file. Multiple log files can exist for a single Outlook session.

file_count

An integer that specifies the maximum number of rotated log files.

initial_erase

You can use one of the following values:

• 1. Deletes the contents of all general log files when Oracle CRM On Demand Desktop starts.
• 0. Does not delete the contents of any general log file when Oracle CRM On Demand Desktop starts.

time_format

A string that specifies the date-and-time format in the log files. You can use one of the following values to specify the date-and-time format:

• $nano. Nanoseconds.
• $micro. Microseconds.
• $mili. Milliseconds.
• $ss. The seconds expressed as two digits.
• $mm. The minutes expressed as two digits.
• $hh. The hour expressed as two digits.
• $dd. The day expressed as two digits.
• $MM. The month expressed as two digits.
• $yy. The year expressed as two digits.
• $yyyy. he year expressed as four digits.

Nanoseconds or microseconds are available only if the system clock allows nanoseconds or microseconds. If the system clock does not allow nanoseconds or microseconds, and if you specify nanoseconds or microseconds, then Oracle CRM On Demand Desktop adds zeros to the value that it creates for the log entry.

log_format

A string that specifies the logging message format. You can use one of the following values:

• %index%. Sequential message index.
• %time%. The time in the format that the time_format parameter sets.
• %thread%. The thread ID that Oracle CRM On Demand Desktop uses to log the message.
• %level%. The logging level for messages in human-readable format.
• %level_num%. The logging level for messages in numeric format.
• %log_src%. The source of the logging message. This source can be an internal component of Oracle CRM On Demand Desktop, for example, a connector or application manager.

starter

A string that specifies the first message that Oracle CRM On Demand Desktop adds to the log file when it starts logging, for example:

--- logging is initialized ---

finisher

A string that specifies the last message that Oracle CRM On Demand Desktop adds to the log file when it stops logging, for example:

--- logging is finished ---

If a log file does not include the last message, then the log file indicates that Oracle CRM On Demand Desktop stopped logging abnormally.