14Windows Registry Parameters You Can Use With Oracle CRM On Demand Desktop
Windows Registry Parameters You Can Use With Oracle CRM On Demand Desktop
This chapter describes Windows registry parameters that you can use with Oracle CRM On Demand Desktop. It includes the following topics:
Windows Registry Parameters That Affect Oracle CRM On Demand Desktop Behavior
The following table describes the Windows Registry parameters that you can modify to change Oracle CRM On Demand Desktop behavior. In the Registry Editor (regedit), you can modify these parameters in the following path:
HKEY_CURRENT_USER\Software\Oracle\CRM Desktop
Table Windows Registry Parameters That Affect Behavior of the Oracle CRM On Demand Desktop Add-In
Windows Registry Parameter | Description |
---|---|
AppLanguageID |
The ID of the current installation package of Microsoft Outlook. |
ConnectorCfgPath |
The path to the connector_configuration.xml file in the customization package. |
DestinationProfile |
The name of the Microsoft Outlook profile where Oracle CRM On Demand Desktop is installed. |
DestinationStore |
The location of the profile identified in the DestinationProfile. |
DisableSyncConfirmation |
Suppresses the confirmation for deleting an object. The following values are valid:
The corresponding attribute in the connector_configuration.xml file of the customization package automatically overwrites the DisableSyncConfirmation key. |
FiltersEstimateOnTimer |
Sets the interval in milliseconds for an automatic estimate of the records after the filters are changed in the control panel. The following values are valid:
This entry is not accessible through the administrative interface. |
HTTPClient:AcceptCompression |
A flag that instructs the Web service connector to accept compressed HTTP content. This parameter is not accessible through the administrative interface. |
HTTPClient:CompressOutgoing |
A flag that instructs the Web service connector to send zipped HTTP content. This parameter is not accessible through the administrative interface. |
HTTPClient:ConnectTimeout |
The timeout period in milliseconds for the connection. |
HTTPClient:ReceiveTimeout |
The timeout period in milliseconds for receiving requests. |
HTTPClient:SendRetryCount |
The number of connection retries for a period of time in milliseconds. |
HTTPClient:SendTimeout |
The timeout period in milliseconds for sending requests. |
Page:Feedback:AttachLog |
Specifies the log file for the feedback form. The following values are valid:
|
ProxyLogin |
The login name for the proxy server. |
ProxyPassword |
The password for the proxy server. |
ProxyServer |
The host name for the proxy server. |
ProxyServerPort |
The port number for the proxy server. |
ProxyUsage |
The flag that specifies a proxy server. The following values are valid:
|
RunPeriodicalSyncAlways |
Determines if Oracle CRM On Demand Desktop starts a scheduled synchronization at the scheduled time or waits until Microsoft Outlook is idle. The following values are available:
|
SessionsKeepAliveAmount |
Defines the number of synchronization sessions to store in the internal database as history. Oracle CRM On Demand Desktop stores statistical information for each synchronization session. The user can use the list control in the Sync Issues tab of the Synchronization Control Panel to view information about synchronization issues. |
SharedByDefault:NewItems |
The SharedByDefault:NewItems registry key determines how Oracle CRM On Demand Desktop shares newly created Microsoft Outlook items. For more information, see Overview of How Oracle CRM On Demand Desktop Handles an Activity. |
Connector:HideSavePasswordOption |
Determines how Oracle CRM On Demand Desktop displays the Save Password check box on the login screen. The following values are valid:
|
Connector:MetaInfoFilePath |
Describes the path to the od_meta_info.xml file in the customization package. |
Connector:Protocol |
Defines the URL protocol. The default is http. The following values are valid:
Note: Only https protocol is allowed in production environments.
|
Connector:RequestSuffix |
Defines the suffix of the URL that points to the Oracle CRM On Demand server. The following is the default value: Services/Integration |
Connector:Server |
Defines the host name of the URL. The default is empty. |
Connector:ServerPort |
Defines the port of the URL. The default is 80 for http protocol and 443 for https protocol. Only https protocol is allowed in production environments. |
SuppressSyncEstimating |
At the beginning of the synchronization, this parameter determines how Oracle CRM On Demand Desktop gets an estimate of the number of all the object types that are visible to the current user. The following values are valid:
|
SwitchToAutoCompleteChoiceLimit |
Limits the number of items that Oracle CRM On Demand Desktop displays in the box in the Filters tab when the user creates rules. |
SyncDumpBaseFname |
Defines the full path and file name for the synchronization dump file that Oracle CRM On Demand Desktop creates separately for each synchronization. Oracle CRM On Demand Desktop stores synchronization history information in this file. Oracle CRM On Demand Desktop uses it for investigation purposes. |
Connector:SOAPDumpBaseFname |
Describes the path to where Oracle CRM On Demand Desktop stores information about SOAP activity. This information describes the requests and replies of the Web Service Connector. |
Windows Registry Parameters That Affect Local Synchronization
The following table describes the options in the Windows Registry that control local synchronization behavior. For more information, see Modifying the Windows Registry Parameters That Affect Local Synchronization.
Table Windows Registry Parameters That Affect Local Synchronization
Windows Registry Parameter | Description |
---|---|
EnablePeriodicUpstreamSync |
Enables or disables local synchronization. The following values are valid:
|
UpstreamSyncIsDefault |
Sets the default synchronization type. The following values are valid:
|
CustomSyncPeriodsUpstream |
Specifies the intervals for local synchronization. The default values are:
You must describe these values in the package_res.xml file as resource strings:
|
SyncPeriodUpstream |
Specifies the default value for the local synchronization interval in milliseconds. The default value is 00dbba00 (4 hours). |
UpstreamSyncMinThreshold |
Disables local synchronization if the general synchronization occurs more frequently than the specified value. The default value is 60000 milliseconds (6 hours). |
Windows Registry Parameters That You Can Use with Log Files and Dump Files
This topic describes parameters that you can use with log files and dump files. It includes the following information:
Windows Registry Parameters That You Can Use with the General Log File
Windows Registry Parameters That You Can Use with the Exception Log File
Windows Registry Parameters That You Can Use with the Crash Dump File
Windows Registry Parameters That You Can Use with the SOAP Dump File
Windows Registry Parameters That You Can Use with the Synchronization Dump File
An integer that you can use with a parameter represents a DWORD value in the registry in Windows 7 or a 32-bit DWORD value in the registry in Windows Vista.
Windows Registry Parameters That You Can Use with the General Log File
The following table describes the parameters that you can use with the general log.
Table Parameters That You Can Use with the General Log File
Parameter | Description |
---|---|
enable |
You can use one of the following values:
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:
|
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:
|
enable_cout |
You can use one of the following values:
|
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:
|
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:
|
file_count |
An integer that specifies the maximum number of rotated log files. |
initial_erase |
You can use one of the following values:
|
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:
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:
|
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. |
Windows Registry Parameters That You Can Use with the Exception Log File
The following table describes the Windows parameters that you can use with the exception log file.
Table Parameters That You Can Use With the Exception Log File
Parameter | Description |
---|---|
enable |
You can use one of the following values:
|
file_count |
An integer that specifies the maximum number of rotated log files. |
initial_erase |
You can use one of the following values:
|
max_size_bytes |
An integer that sets the maximum number of bytes that a single log file can contain. |
out_file |
A string that specifies the base file name that Oracle CRM On Demand Desktop uses for logging. |
Windows Registry Parameters That You Can Use with the Crash Dump File
The following table describes the Windows parameters that you can use with the crash dump file. You can use the following parameters:
any_in_trace
all_in_trace
ex_white_list
ex_black_list
To separate the values in these parameters, you can use the following symbols:
, (comma)
; (semicolon)
| (vertical bar)
/ (slash)
\t (backslash with a t)
(single space)
Table Parameters That You Can Use with the Crash Dump File
Parameter | Description |
---|---|
enable |
You can use one of the following values:
|
Count |
An integer that specifies the maximum number of old dump files that Oracle CRM On Demand Desktop preserves in the output logging directory. |
on_top |
A string that specifies the filtering condition for the crash dump file. Oracle CRM On Demand Desktop applies this filtering only if the item you specify resides on top of the stack trace when the failure occurs. For example, you can use the following value: CRMDesktop3D.dll If you do not specify a value, then Oracle CRM On Demand Desktop ignores this parameter. |
on_top_op |
You can use one of the following values:
|
any_in_trace |
A string that specifies a list of items. If the stack trace includes an item that you specify, then Oracle CRM On Demand Desktop saves a crash dump file for this item. For example, you can use the following value: Ntdll.dll,Kernel32.dll In this example, if the stack trace includes an entry for Ntdll.dll or Kernel32.dll, then Oracle CRM On Demand Desktop saves a crash dump file for this item. |
all_in_trace |
A string that specifies a list of items. If the stack trace includes all the items you specify, then Oracle CRM On Demand Desktop saves a crash dump file for these items. For example, you can use the following value: Ntdll.dll,Kernel32.dll In this example, if the stack trace includes an entry for Ntdll.dll and an entry for Kernel32.dll, then Oracle CRM On Demand Desktop saves a crash dump file for these items. |
delay_ms |
An integer that specifies a delay in milliseconds. If the time that elapses after a previous exception exceeds the value you specify, then Oracle CRM On Demand Desktop saves a crash dump file. The default value is 0. This default makes sure that Oracle CRM On Demand Desktop always saves a crash dump file. |
ex_white_list |
A string that specifies a list of C++ exception names. If an exception occurs for an exception name that you specify, then Oracle CRM On Demand Desktop creates a minidump for this exception. |
ex_black_list |
A string that specifies a list of C++ exception names that Oracle CRM On Demand Desktop uses but does not create a minidump file. If the white_list parameter is empty, then Oracle CRM On Demand Desktop creates a dump file for all exceptions except the exceptions that the black_list parameter lists. |
sigabrt |
SIGABRT is a signal that Oracle CRM On Demand Desktop sends to a process to tell it to end. You can use one of the following values:
|
minidump_type |
An integer that specifies the mindump type. The default value is 1 (MiniDumpNormal|MiniDumpWithDataSegs). Use this parameter with caution because other values might increase the size of the crash dump file significantly. For more information, see the documentation about the DumpType parameter of the MiniDumpWriteDump function at the Microsoft MSDN Web site. |
Windows Registry Parameters That You Can Use with the SOAP Dump File
The following table describes the Windows parameters that you can use with the SOAP dump file.
Table Parameters That You Can Use with the SOAP Dump File
Parameter | Description |
---|---|
enable |
You can use one of the following values:
|
enable_dbg_window |
You can use one of the following values:
|
enable_cout |
You can use one of the following values:
|
file_count |
An integer that specifies the maximum number of rotated log files. |
root_tag_name |
A string that specifies the root XML tags that Oracle CRM On Demand Desktop uses in generated XML files. The default value is soap_comm_log. If you use the following value, then it does not write the opening or closing root tags: "" |
file_extension |
A string that specifies the file extension that Oracle CRM On Demand Desktop uses for generated log files. The default value is xml. |
bin_mode |
You can use one of the following values:
|
Windows Registry Parameters That You Can Use with the Synchronization Dump File
The following table describes the Windows parameters that you can use with the synchronization dump file.
Table Parameters That You Can Use with the Synchronization Dump File
Parameter | Description |
---|---|
enable |
You can use one of the following values:
|
file_count |
An integer that specifies the maximum number of rotated log files. |
out_file |
A string that specifies the base file name that Oracle CRM On Demand Desktop uses for logging. |