Siebel Server Sync Guide > Configuring Siebel Server Sync >

Tuning SSSE Siebel Profile Parameters


SSSE contains various parameters that you can adjust to optimize performance. The following procedure describes how to change Siebel profile parameters. The profile applies to all PIMSI Engines in your Siebel Enterprise.

This task is a step in Process of Configuring SSSE.

To tune SSSE parameters in the Siebel profile

  1. Log in to your Siebel application as an administrator and navigate to Administration - PIM Server Integration, Configuration, and then PIM Server Integration Configuration.
  2. In the PIM Server Integration Configuration list, select the record in which the value of Profile Name is Siebel.
  3. In the Configuration Parameters list, modify the fields or add records as needed to tune the performance of your Siebel implementation, using the information in Table 17.

Table 17. Siebel Profile Configuration Parameters
Section
Parameter
Default
Comment

Siebel

AddAttendee

 

Y

The AddAttendee parameter allows you to specify that when SSSE synchronizes data relating to appointment attendees, the most current data in Microsoft Outlook takes precedence over related data in the Siebel application.

If this parameter is set to Y, when SSSE first synchronizes an appointment created in Microsoft Exchange with the Siebel application, all the attendees included in the invitation who do not have synchronization enabled are added to the employee list for the Siebel calendar item, as is the meeting organizer, and the user whose records are currently being synchronized. Attendees who have synchronization enabled are added to the employee list when they accept or tentatively accept the meeting invite.

If this parameter is set to N, all attendees are added to the employee list for the Siebel calendar item whether or not they have synchronization enabled and whether or not they have accepted the meeting invite. During the next synchronization cycle, SSSE creates Microsoft Exchange records for all the appointment attendees included in the Siebel calendar item. This can lead to a situation where a Microsoft Exchange record is created for an attendee who declines or deletes the invitation between the first and second synchronization cycles.

Siebel

AttendeeQueryForce
EmailLower

FALSE

When synchronizing an appointment created in Microsoft Exchange with the Siebel application, force the email addresses of attendees to lower case when querying for the contact in the Siebel application. Because Microsoft Exchange and Siebel email addresses use mixed case or upper case letters, set this parameter to TRUE.

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. For example, if you run the Dispatcher every five minutes, unneeded data is removed once an hour.

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

MaxUserExtractReq
BatchSize

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

OnlySyncCategorized
Contacts

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.

Siebel Server Sync Guide