Siebel

AttendeeQueryForceEmailLower

FALSE

When synchronizing an appointment from Exchange to Siebel, force the email addresses of attendees to lower case when querying for the contact in Siebel. Set this parameter to TRUE if your Siebel email addresses use mixed case or upper case letters.

Siebel

DispCycleCount for GC

12

Determines how many times the Dispatcher runs before unneeded information is removed from the S_SD_SYNC_INFO table, where information is stored about data to synchronize. Using default values, this removal of unneeded information occurs once an hour, because the Dispatcher job is normally run every five minutes.

Siebel

ExtractStartDate

01/01/1980

Determines which Calendar and To Do records will be excluded from synchronization because of their date settings. For more information, see Factors That Determine Calendar Synchronization or Factors That Determine To Do Record Synchronization.

Siebel

ExtractStartDateFormat

MM/DD/YYYY

Date format for the ExtractStartDate parameter. SSSE uses the format that you specify in this setting to interpret the value of your ExtractStartDate setting correctly. It is not necessary for this format to match the date format that your Siebel application generally uses.

Siebel

ForceTranscode

FALSE

Forces text conversion to use transcode. Set this parameter to TRUE if your Siebel implementation uses a transcode database type.

Siebel

MaxAlarmLeadMinutes

Not applicable

Maximum number of minutes for an appointment alarm lead time.

Siebel

MaxUserExtractReqBatchSize

20

Maximum number of user extractions that can be requested in one synchronization request.

Siebel

NotificationFrequency

2

If the PIMSI Dispatcher detects that a PIMSI Engine component is not responding correctly, the Dispatcher signals the Engine to discover whether it can respond. This parameter specifies how many times the Dispatcher should request a response from an unresponsive PIMSI Engine before attempting to recover it.

NOTE:  The PIMSI Dispatcher automatically attempts to recover any PIMSI Engine that has failed to respond to the set number of requests. See the Dispatcher log for records of any unresponsive Engines. See the individual Engine log for information that may help you diagnose why the Engine stopped responding.

Siebel

OnlySyncCategorizedContacts

FALSE

Determines whether or not Initial Extract operations synchronize Exchange Contact records that have the Category field set to a specified value. Case-insensitive. For more information about this parameter, see Initial Extract and Ongoing Extract.

Siebel

ReconciliationDuration

60

Specifies how many seconds the PIMSI Dispatcher waits after signaling a PIMSI Engine. If the Dispatcher does not receive a response within this time period, the Dispatcher either attempts to recover the Engine or signals it again, depending on whether or not the number of unsuccessful signals has reached the value of the Notification Frequency setting.

Siebel

ResolveContactbyEmailAddress

FALSE

If set to TRUE, use email addresses, as well as first and last names, when trying to resolve contacts.