5Configuring Siebel Server Sync for Microsoft Exchange Server
Configuring Siebel Server Sync for Microsoft Exchange Server
This chapter provides instructions for configuring SSSE after installation. It includes the following topics:
About Configuring SSSE
Most of the tasks described in this chapter are required for configuring SSSE. For information about the correct order for performing these required configuration tasks, see Roadmap for Configuring SSSE.
Some configuration and administration steps are required only if you want all of yourSSSE users to be able to select which calendar and task records to synchronize from Microsoft Exchange to Siebel Business Applications. For information about providing users with this capability, see About Setting Calendar and Task Record Synchronization Options.
Roadmap for Configuring SSSE
To configure SSSE, perform the following tasks:
Configuring User Mailbox Access for the Exchange Service Account
Configuring and Starting PIMSI Dispatcher
The following configuration tasks are optional:
About the Default Account Setting
This topic describes how the Default Account setting affects synchronization.
Every business contact record that is stored in the Siebel database must be associated with an account. This association provides the account’s Primary Address for the business contact. When a Siebel business contact is synchronized using SSSE, the Account and Account Location fields for the contact and the Account’s Primary Address are synchronized with the Company Name field, the Office field, and the Address field in Microsoft Exchange, respectively.
If a user enters a value for the Address field for a contact record in Microsoft Outlook, but does not enter a value for the Company field and the Office field, then a problem occurs whenSSSE attempts to synchronize the record, because the Siebel data model cannot associate the address with the contact if there are no values for Account Name and Location. For this reason, it is recommended that users always include a Company name and Office value when entering a contact address in Microsoft Outlook.
To work around this problem, you can specify Account name and Account Location values that already exist in the Siebel database as the default values for the Account Name and Account Location fields. This allows the contact address from Microsoft Outlook to be synchronized with the Siebel database. However, that address is associated with the default account, since no account was supplied in Microsoft Outlook.
About Tuning SSSE for Optimal Performance
In general,SSSE works well when you configure your Siebel implementation using the scalability and sizing recommendations that are discussed in Siebel Performance Tuning Guide. For example, you can set parameters such as MaxMTServers and MinMTServers for the PIMSI Engine component to the values that suit your implementation as a whole, without especially consideringSSSE performance issues. However, this topic discusses some configuration recommendations that are particularly important for ensuring optimum performance for SSSE.
MaxTasks
The MaxTasks setting controls the total number of PIMSI Engine jobs that can run simultaneously on a single Siebel Server computer. The value you choose for the MaxTasks parameter can limit the total number of connector instances that run at any one time, preventing the connector computers from becoming overloaded.
Choosing an Appropriate Dispatcher Repeat Interval
When you are satisfied with your MaxTasks setting values, you might want to measure how quickly SSSE can process your entire population of ongoing SSSE users. You can use the information to adjust the values of the Repeating job settings for the PIMSI Dispatcher job, so that the Dispatcher runs at an interval of your choosing. Dispatcher jobs must not overlap. To ensure that this does not occur, set the Repeat From field of the repeating job to End. This ensures that each PIMSI Dispatcher cycle does not start until a specified interval after the previous PIMSI Dispatcher cycle has completed. For more information about setting up PIMSI Dispatcher jobs, see Configuring and Starting PIMSI Dispatcher.
Modifying Enterprise and Server Component Parameters
Many Siebel Enterprise Server parameters and PIMSI server component parameters that affect the operation of SSSE are set automatically during the Siebel installation and configuration process. You can choose different values for these parameters if the default values do not suit your Siebel implementation. It is recommended that you set SSSE-related parameters at the Enterprise level rather than at the server component level; this ensures that SSSE settings are consistent on all the Siebel Servers in your Enterprise. However, a number of parameters must be set for the PIMSI Engine or PIMSI Dispatcher at the server component level.
The following procedures describe how to view and modify Siebel Enterprise Server and PIMSI server component parameters that affect the operation of SSSE using the Server Administration views in the Siebel application and using the srvrmgr command-line interface. For information about additional parameters that affect SSSE performance, see About Tuning SSSE for Optimal Performance.
This task is a step in Roadmap for Configuring SSSE.
For a list of the PIMSI server component parameters and the SSSE-related Siebel Enterprise Server parameters, see the following topics:
Modifying Enterprise and Server Component Parameters Using Server Administration Views
The following procedure describes how to change the value of Siebel Enterprise Server or server component parameters using the Siebel Server Administration views.
To modify Enterprise and server component parameters using Server Administration views
Perform one of the following:
To view or change SSSE-related Siebel Enterprise Server parameters, navigate to the Administration - Server Configuration screen, Enterprises, and then the Parameters view.
To view or change PIMSI Engine or PIMSI Dispatcher component parameters, navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Definitions view.
In the Component Definitions list, select either PIMSI Dispatcher or PIMSI Engine.
In the Component Parameters or Enterprise Parameters list, locate the parameter you want to view or change.
See the tables in topics SSSE-Related Siebel Enterprise Server Parameters and Configuring the Database for SSSE for a description of some of the SSSE-related server component parameters and Siebel Enterprise Server parameters.
Change the value of the relevant parameter.
To make the change effective, restart the Siebel Server.
Modifying Enterprise and Server Component Parameters Using srvrmgr
You can change the value of Siebel Enterprise Server or server component parameters using the Siebel Server Manager command-line interface (srvrmgr program) as described in the following procedure.
To modify Enterprise and server component parameters using srvrmgr
Start the Server Manager command-line interface.
For information on how to start and use the srvrmgr program, see Siebel System Administration Guide.
At the srvrmgr> prompt, enter an appropriate command to change the parameter. For example, the following command sets the Enable Inbound Activity Filter parameter to a value of TRUE:
change ent param EnableInboundActivityFilter="TRUE"
Take any required action to make the change effective, such as restarting the Siebel Server.
PIMSI Engine Server Component Parameters
The information in the table in SSSE-Related Siebel Enterprise Server Parameters lists PIMSI Engine server component parameters.
Related Topic
SSSE-Related Siebel Enterprise Server Parameters
The following information lists SSSE-related Siebel Enterprise Server parameters. Most of these parameters relate to the PIMSI Engine. If a parameter relates to the PIMSI Dispatcher, then this is indicated.
| Parameter Name | Parameter Alias | Comments |
|---|---|---|
Business Service Query Access |
BusinessServiceQueryAccessList |
The Siebel database and Microsoft Exchange differ in how they store addresses. This parameter specifies the name of the script that is used to combine two Siebel address field values when transmitting address data to Microsoft Exchange, and split one Microsoft Exchange address field value into two values when transmitting address data to the Siebel database. The value for this parameter, SSSE Address Parser (eScript), is set automatically during installation. |
Calendar Lock Expire After |
CalendarLockExpireAfter |
The lock on a calendar record expires after the specified number of seconds. A calendar record is locked whenever it is being updated. |
Calendar Lock Sleep Time |
CalendarLockSleepTime |
Time interval thatSSSE waits before checking the calendar lock again. |
Dispatcher Abort Limit Low B Applies to the PIMSI Dispatcher component only. |
DispAbortLowBound |
When the PIMSI Dispatcher inspects changed records to determine which users the PIMSI Engine must synchronize, if the total number of changed records to inspect is larger than DispAbortLowBound, then the Dispatcher stops inspecting records individually and sets a flag that notifies the PIMSI Engine to search for changed records for all SSSE users. This improves SSSE performance in situations where large numbers of records are changed frequently. |
Dispatcher Abort Limit Per Use Applies to the PIMSI Dispatcher component only. |
DispAbortLimit |
The maximum number of updates that the Dispatcher processes for each dispatch cycle. If there are more changes in the Siebel database than this number, then the Dispatcher stops searching for changes and sends dispatch messages for the users determined so far. |
Dispatcher Garbage Collection Applies to the PIMSI Dispatcher component only. |
DispGCCycleCount |
Determines how many times the Dispatcher runs before information that is no longer required is removed from the S_SD_SYNC_INFO table. The S_SD_SYNC_INFO table stores information about data to synchronize. Using default values, this removal of unnecessary information occurs once an hour, because the Dispatcher job is normally run every five minutes. |
Dispatcher Notification Frequency Applies to the PIMSI Dispatcher component only. |
DispNotificationFreq |
If the PIMSI Dispatcher detects that a PIMSI Engine component is not responding correctly, then the Dispatcher signals the Engine to discover whether it can respond. This parameter specifies how many times the Dispatcher requests a response from an unresponsive PIMSI Engine before attempting to recover it.
Note: The PIMSI Dispatcher automatically attempts to recover users’ data changes that are being processed on 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 logs for information that might help you diagnose why the Engine stopped responding.
|
Dispatcher Reconciliation Dura Applies to the PIMSI Dispatcher component only. |
DispReconciliationDuration |
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, then 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. |
Distribution List Query Size |
DistributionListQuerySize |
When the Siebel Exchange Connector determines the members of a Distribution List, it requests information about one or more batches of members. This setting specifies the maximum number of members in each batch. Maximum valid value is 1500 for Windows 2003. Minimum value is 1. |
Enable Inbound Activity Filter |
EnableInboundActivityFilter |
When set to TRUE for the PIMSI Engine server component, synchronizes calendar and task items that originate in Microsoft Exchange only if the value of the Category field matches a valid Siebel Value for an LOV that has Siebel LIC Type set to TODO_Type. When this parameter is set to FALSE,SSSE attempts to synchronize all calendar and task items that originate in Microsoft Exchange for each user who has synchronization enabled. For more information on using this parameter, see: |
Extract Start Date Format |
ExtractStartDateFormat |
Format of the Extract Start Date parameter. Default value is MM/DD/YYYY. 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. For information on the Extract Start Date parameter, see PIMSI Engine Server Component Parameters. |
Force Transcode |
ForceTranscode |
Forces text conversion to use transcode. Set this parameter to TRUE if your Siebel implementation uses a transcode database type. |
Max Alarm Lead Minutes |
MaxAlarmLead |
This parameter is now obsolete. |
Max Extract Request Batch Size Applies to the PIMSI Dispatcher component only. |
MaxExtReqBatchSize |
Maximum number of user extractions that can be requested in one synchronization request. The default value is 10. For example, if the Max Extract Request Batch Size parameter is set to 10, and if 1000 users have synchronization enabled, then the PIMSI Dispatcher creates 100 PIMSI Engine jobs, each containing 10 user extractions. The data for 100 users is synchronized at one time, because each PIMSI Engine processes each user in a job sequentially. When specifying a value for this parameter, consider the number of users who have synchronization enabled, and the number of jobs that your server can process in parallel without affecting performance. If there are multiple users in a single PIMSI Engine job, then data, such as LOVs and system parameters, is queried only once and is shared by the jobs for each user. |
Maximum Tasks |
MaxTasks |
The maximum number of PIMSI Engine jobs that can run simultaneously on a single Siebel Server computer. For more information about this setting, see About Tuning SSSE for Optimal Performance. The value of the Maximum Tasks parameter determines the total number of users who can be synchronized in parallel. For example, if the Maximum Tasks parameter is set to a value of 50, and the PIMSI engine is installed on three Siebel Server computers in your SSSE environment, then 150 users can be synchronized simultaneously. |
Only Sync Categorized Contacts |
OnlySyncCategorized Contacts |
Determines whether or not initial extract operations synchronize only Microsoft Exchange contact records that have the Category field set to a specified value—the value that matches the Siebel domain’s PIM Category Value setting—or all contact records. Valid values are TRUE and FALSE, case-insensitive. For more information about this parameter, see Initial Extract and Ongoing Extract and Setting PIM Category Values for Siebel Domains. |
Preserve Attachments |
PreserveAttachments |
Indicates whether or not the Exchange Connector preserves PIM attachments for non Calendar domains. (Calendar attachments are automatically preserved.) If this parameter is set to FALSE, then attachments are removed when the Exchange Connector updates the record in Microsoft Exchange. This setting does not affect Siebel attachments. |
Preserve Unmapped Fields |
PreserveFields |
Indicates whether or not the Exchange Connector preserves the data for PIM fields which are not mapped for synchronization for non Calendar domains. If this parameter is FALSE, then any data in an unmapped field is removed from the record in Microsoft Exchange. |
Remove Attendees With No Email |
RemoveOutAttendees WithoutEmail |
If set to TRUE, then do not synchronize attendees who do not have email addresses when synchronizing from Siebel Business Applications to Microsoft Exchange. |
Resolve Contact by Email |
ResolveContactbyEmail |
When synchronizing Microsoft Exchange calendar records with Siebel Business Applications, SSSE categorizes calendar record attendees as contacts or unresolved attendees. When matching attendees to Siebel contact records, the value of the Resolve Contact by Email parameter determines whether or not the attendee and the contact record must have identical email addresses to be considered as matching records. If the Resolve Contact by Email parameter is TRUE, then an attendee’s email address must be identical to the email address of a single Siebel contact record for the records to be considered a match. SSSE does not match records on the basis of matching names if the email address differs (or does not exist). If the Resolve Contact by Email parameter is FALSE, if an attendee’s email address is not identical to the email address of a single contact record, then SSSE searches for a contact record with the same first and last names as the attendee. If a record is found with matching first and last names, then provided that the records do not contain different email addresses, SSSE treats the two records as a match. |
Related Topic
About the Exchange Service Account
The user account under which the Exchange Connector runs is known as the Exchange service account. The Exchange service account must have read-write privileges to the Microsoft Exchange mailboxes of all synchronization-enabled users. Therefore, the Exchange service account must be a domain account, not a local account.
Provided there are trust relationships between all the Active Directory domains in which your Exchange Servers are deployed, you require only one Exchange service account for your whole Microsoft Exchange infrastructure, regardless of how many Exchange Servers you have. Exchange Servers are not listed in the Siebel database. Instead, the Exchange Connector queries the Active Directory Global Catalog at runtime to determine which Exchange Server handles the mailbox for a given user (SMTP email address).
To manage the process of giving the Exchange service account read and write access toSSSE user mailboxes, you can use a script that gathers information about the applicable users from the Siebel User Map view. For more information about the script, see Configuring User Mailbox Access for the Exchange Service Account.
Configuring User Mailbox Access for the Exchange Service Account
The Exchange Connector uses the credentials of the user account under which it runs to interact with all of the Microsoft Exchange mailboxes in the Active Directory forest (one or more Active Directory domains that share certain characteristics and information). The Exchange Connector user account must have an active Microsoft Exchange mailbox account, and must have special mailbox access privileges to access other users’ active Microsoft Exchange mailboxes. This topic describes how to configure access privileges to users’ mailboxes for the Exchange Connector user account. For more information about these privileges, see About the Exchange Service Account.
This task is a step in Process of Configuring the Web Service Exchange Connector and Modifying SSSE Log File Settings.
The following procedures describe two ways of configuring the necessary credentials to access user mailboxes: a method that uses a script, and a manual method.
Script Method. The method that uses a script is recommended if the Exchange Connector requires access to many users’ mailboxes, as would be typical during deployment of SSSE. For more information on using the script method, see Configuring Exchange Service Account Access Permissions Using a Script.
Manual Method. The manual method is recommended if you only have to grant access to a few users’ mailboxes, such as when you want to enable synchronization for a few new employees. For more information on using the manual method, see Configuring Exchange Service Account Access Permissions Manually.
Configuring Exchange Service Account Access Permissions Using a Script
The procedure in this topic describes how to use a script in a Microsoft Exchange environment to configure the security settings that grant access to other users’ mailboxes for the user account under which the Exchange Connector application runs.
To configure access to user mailboxes for the Microsoft Exchange service account using a script
Verify that the user account under which the Exchange Connector runs has an active mailbox on the Exchange Server, or create and activate one if necessary.
Log in to your Siebel application as an administrator and navigate to the Administration - PIM Server Integration screen, Sync Access Control, and then the User Map view.
In the User Map list, query for the set of users who will use SSSE.
From the applet menu, select Columns Displayed, and then hide all columns except PIM User Identifier.
Click Menu, then select Export, and then click Next (accepting the defaults)
In the Export dialog box, choose settings as described in the following table, and then click Next.
Setting Value Rows to Export
All Rows in Current Query
Columns to Export
Visible Columns
Output Format
Comma Separated Text File
In the File Download dialog box, click Save, then select an output file name and location.
In the Export dialog box, click Close.
Navigate to install_directory\siebsrvr\bin where install_directory is the installation directory for your Siebel implementation.
Extract the ssse_exchange2k10_permissions.zip file.
Use a text editor to edit ssse_exchange2k10_permissions.ps1 in accordance with the instructions included in the file, then save the file.
Run the script according to the instructions provided in the ssse_exchange2k10_permissions.ps1 file.
Configuring Exchange Service Account Access Permissions Manually
The following procedure describe how to manually configure the security settings that grant access to other users’ mailboxes for the user account under which the Exchange Connector application runs.
To configure access to user mailboxes for the Microsoft Exchange service account manually
Verify that the user account under which the Exchange Connector application runs has a mailbox on the Microsoft Exchange Server, or create one if necessary.
On any computer that has the Exchange System Management Tools installed (for example, the Exchange Server), start the Exchange Management Console.
In the console tree, expand Recipient Configuration, then select Mailbox.
In the result pane, select the user mailbox to which you want to grant access, then select Manage Full Access Permission from the action pane.
On the Manage Full Access Permission page, select Add.
Select the user to whom you are granting full access permission (the user account under which the Exchange Connector application runs), then click OK.
Click Manage, then click Finish.
In the action pane, select Manage Send As Permission.
On the Manage Send As Permission page, select Add.
Select the Exchange Connector user account, then click OK.
Click Manage, then click Finish.
Repeat Step 4 to Step 11 for each user who will use SSSE.
Process of Configuring the Web Service Exchange Connector
This topic describes the tasks involved in configuring the Web service Exchange Connector.
This process is a step in Roadmap for Configuring SSSE.
To configure the Web Service Exchange Connector, perform the following tasks:
Ensure that you run the Siebel Server system service with the credentials of the Microsoft Exchange service account user, and that the Exchange service account user has access to user mailboxes as described in Configuring User Mailbox Access for the Exchange Service Account.
Configuring SSSE for Multiple AD Forest Environments (Web Connector).
Configuring the IIS Web Server for Microsoft Exchange (Web Connector).
Configuring the Autodiscover Service URL
This topic describes how to configure the Microsoft Exchange Autodiscover service for each domain in your corporate network. The Autodiscover service provides a variety of functions, such as automatic configuration and updating of Microsoft Outlook user profile settings; it also provides Outlook clients with the URLs required to access Microsoft Exchange Web services.
This task is a step in Process of Configuring the Web Service Exchange Connector.
In order that the Autodiscover service can locate the Exchange Servers of synchronization-enabled users, you must configure an Autodiscover URL for each domain containing Microsoft Exchange Server hosts. It is necessary to define only one Autodiscover URL for each domain in your environment, even if a domain includes multiple Microsoft Exchange Server hosts.
To configure the Autodiscover service URL
Navigate to the Administration - PIM Server Integration screen, then the Configuration view.
In the PIM Server Integration Configuration list, select the Exchange Web Service profile.
In the Configuration Parameters list, click New to add a new section and complete the fields as shown in the following table:
Field Value Section
AutoDiscover URL
Parameter
Value
Value
https://HOSTNAME/Autodiscover/autodiscover.svcwhere HOSTNAME is the name of a Microsoft Exchange Server host computer
Repeat Step 3 for each domain containing Microsoft Exchange Server 2010 hosts in your SSSE environment.
Configuring SSSE for Multiple AD Forest Environments (Web Connector)
SSSE provides support for Microsoft Exchange environments that include more than one Active Directory forest. This topic describes how to configure SSSE to run in an environment in which a Web service Exchange Connector is implemented, and the Siebel Server computer running the Web service Exchange Connector is in a different AD forest to the host computer(s) running the Microsoft Exchange Server(s).
This task is a step in Process of Configuring the Web Service Exchange Connector.
To run SSSE in a multiple AD forest Microsoft Exchange environment with the Web service Exchange Connector, perform the following procedure.
To configure SSSE for multiple AD forest environments (Web Service Exchange Connector)
Ensure that the Web service Exchange Connector runs using the credentials of a specific user account that has access to the mailboxes of Active Directory (AD) users who have been enabled for synchronization.
If the Web service Exchange Connector user account is not in the same domain as the Microsoft Exchange Server, then there must be a trust relationship between the two domains. There does not necessarily have to be a trust relationship between Microsoft Exchange Servers in different domains.
For each domain containing Microsoft Exchange Server hosts that is in a different AD forest to the Exchange Connector host computer, configure an Autodiscover URL as described in Configuring the Autodiscover Service URL.
Configuring the IIS Web Server for Microsoft Exchange (Web Connector)
This topic describes the Internet Information Server (IIS) configuration tasks you must perform on the Microsoft Exchange Server host to enable Web service Exchange Connector communications with the host.
This task is a step in Process of Configuring the Web Service Exchange Connector.
Microsoft Exchange uses Internet Information Services (IIS) 7, which supports anonymous and Integrated Windows authentication by default. On the Microsoft Exchange Server host, ensure that the IIS authentication settings for the Autodiscover and Exchange Web Services (EWS) virtual directories are set to these default values. For information on setting authentication properties for IIS virtual directories, see the Microsoft documentation.
Configuring Outbound Web Services for Microsoft Exchange
You must configure outbound Web services.
This task is a step in Process of Configuring the Web Service Exchange Connector.
To configure outbound Web services
Navigate to the Administration - Outbound Web Services view.
Enter values for the following Web services:
EWSAutoDiscover = https://server/Autodiscover/autodiscover.svc
ExchangeWebService = https://server/EWS/Exchange.asmx
Modifying SSSE Log File Settings
SSSE log files contain information about SSSE operations. Each log file contains information for the operations that are carried out by an individual Siebel Server, and the amount of information that is logged depends on the log level that has been set. For each event listed in the log files, SSSE provides the name of the user who caused the event to be generated. The following procedures describe how to change log levels for SSSE log files, and how to consolidate SSSE log files.
This task is a step in Roadmap for Configuring SSSE.
To change log levels for SSSE
On each Siebel Server that runs an SSSE component, open a Command Prompt window, then navigate to install_directory
\siebsrvr\bin, where install_directory is the installation directory for your Siebel implementation.Log in to Server Manager at the server level for this computer, using a command such as the following:
srvrmgr /u db_user_name /p db_password /e enterprise_server /g gateway_host /s server_name
Use the name of the Siebel Server you are configuring for the value server_name.
At the srvrmgr prompt, enter an appropriate command for the SSSEcomponent log file you are configuring, such as one of the following commands:
Change evtloglvl PIMSIEngSvc=n for comp PIMSIEng Change evtloglvl PIMSIEngSvc=n for comp PIMSIDispatcher
Substitute an integer from 1 to 5 for n, where 1 logs the least information and 5 logs the most information.
By default, many SSSE log files are created. If you want, you can use the following procedure to consolidate these files into one log file for each SSSE component instance on a given Siebel Server. This means that if you consolidate all your SSSE log files, you get one log file for the PIMSI Dispatcher, on the computer where the Dispatcher runs, and you get one log file for each instance of the PIMSI Engine, on the computer where that instance runs.
To consolidate SSSE log files
On a Siebel Server that runs an SSSEcomponent, open a Command Prompt window and navigate to install_directory
\siebsrvr\bin, where install_directory is the installation directory for your Siebel implementation.Enter the following command to log in to Server Manager at the server level for this computer:
srvrmgr /u db_user_name /p db_password /e enterprise_server /g gateway_host /s server_name
Use the name of the Siebel Server you are configuring for the value server_name.
At the srvrmgr prompt, enter one the following commands:
To consolidate PIMSI Engine component log files, enter the following command:
Change param LogUseSharedFile=true for comp PIMSIEng
To consolidate PIMSI Dispatcher component log files, enter the following command:
Change param LogUseSharedFile=true for comp PIMSIDispatcher
The resulting consolidated log file is located in the standard log directory. The format of the file name is component_name_taskId.log, where component_name is either PIMSI engine or PIMSI Dispatcher and taskId is the task that was logged.
Configuring the Database for SSSE
SSSE relies on the presence of certain database triggers in your Enterprise database. You can use an Oracle-provided script to create these triggers. A script is also included for removing database triggers. The following information lists the script names for various database environments. These scripts are located in the siebsrvr/BIN directory on your Siebel Server.
This task is an optional step in Roadmap for Configuring SSSE.
| Database Type | Script to Add Database Triggers | Script to Remove Database Triggers |
|---|---|---|
DB2 |
ssse_triggers_db2.sql |
ssse_drop_triggers_db2.sql |
DB2 390 |
ssse_triggers_db2_390.sql |
ssse_drop_triggers_db2_390.sql |
MS SQL Server |
ssse_triggers_mssql.sql |
ssse_drop_triggers_mssql.sql |
Oracle |
ssse_triggers_ora9.sql |
ssse_drop_triggers_ora9.sql |
If your SSSE implementation includes a significant number of customizations, then you might have to add custom database triggers. For more information about custom triggers, see Process of Customizing SSSE.
The following procedure briefly describes how to use the scripts that create standard database triggers for SSSE.
To create standard database triggers for SSSE
Determine the names of the following items:
The Table Owner for tables in your Siebel database
The script to remove SSSE database triggers from your Siebel database
The script to add SSSE database triggers to your Siebel database
In case old triggers are present, run the script to remove SSSE database triggers from your Siebel database.
Run the script to add SSSE database triggers to your Siebel database.
Provide the Table Owner name when you are prompted to do so.
About Enabling and Disabling Components on SSSE Servers
As with all Siebel Servers, you can selectively enable and disable server components and component groups on the PIMSI Engine and PIMSI Dispatcher computers. For proper operation of SSSE, follow the guidelines in this topic when enabling and disabling server components and component groups. For detailed procedural information on enabling and disabling server components and component groups, see Siebel System Administration Guide.
This task is a step in Roadmap for Configuring SSSE.
It is recommended that you enable the following:
Enable the PIMSI component group on the Enterprise.
Enable the PIMSI Dispatcher (pimsidispatcher) component on the Enterprise and on just one Siebel Server computer.
Enable the PIMSI Engine (pimsieng) component on the Enterprise and on one or more individual Siebel Server computers.
Restarting Siebel Services
You must restart the Siebel Servers and the Siebel Gateway for configuration changes to take effect. For information about restarting Siebel Servers, see Siebel System Administration Guide.
This task is a step in Roadmap for Configuring SSSE.
Configuring and Starting PIMSI Dispatcher
PIMSI Dispatcher runs as a job on a Siebel Server computer. This topic describes how to create and run the PIMSI Dispatcher job and how to configure PIMSI Dispatcher by creating PIMSI Dispatcher user groups. This topic also describes the parameters that affect PIMSI Dispatcher behavior when the PIMSI Engine components stop working and the PIMSI Dispatcher enters recovery mode.
This task is a step in Roadmap for Configuring SSSE.
About PIMSI Dispatcher Recovery Mode Parameters
PIMSI Dispatcher runs for a certain amount of time for each dispatching cycle. The amount of execution time is dependent upon your current configuration, for example, the number of active users and the computer configuration.
If PIMSI Engine components stop working, the PIMSI Dispatcher enters recovery mode. In recovery mode, then the PIMSI Dispatcher sends a number of requests to the PIMSI Engines to respond. The number of requests that are made is determined by the value of the DispNotificationFreq parameter. If the Engines fail to reply after the specified number of response requests are issued, then the PIMSI Dispatcher attempts to remove old PIMSI Engine job requests from the server request queue so that synchronization can resume.
When PIMSI Dispatcher enters recovery mode, you can determine how much additional time the PIMSI Dispatcher requires to complete its run by multiplying the value specified for the DispNotificationFreq parameter by the value specified for the DispReconciliationDuration parameter. The DispReconciliationDuration parameter determines how many seconds the PIMSI Dispatcher waits after signalling a PIMSI Engine.
Creating the PIMSI Dispatcher Job
The following procedure describes how to create the PIMSI Dispatcher job, tune the job’s parameters, and start the job. For information on creating the PIMSI Dispatcher job if you implement PIMSI Dispatcher user groups, see Creating PIMSI Dispatcher User Groups.
To create the PIMSI Dispatcher job and tune its parameters
Log in to your Siebel application as an administrator.
Navigate to the Administration - Server Management screen, then the Jobs view.
In the Jobs List or the Jobs Detail form, click New.
Complete the fields as described in the following table.
For more information about starting jobs, see Siebel System Administration Guide.
Field Comment Component/Job
Specify PIMSI Dispatcher.
Mode
Specify Asynchronous.
Requested Server
Specify the computer where you installed the Siebel Server software for PIMSI Dispatcher.
Repeating?
Select the check box.
Repeat Unit
The suggested value is Minutes.
Repeat Interval
The value you set for this field varies according to your business requirements. It is recommended that you set the Repeat Interval value as high as possible to minimize the performance impact of running the PIMSI Dispatcher job.
Caution: Setting a Repeat Interval less than five minutes can cause SSSE to miss some Siebel updates, causing incomplete synchronization and possibly decreasing performance throughout the Enterprise.Repeat From
Set the value of this field to End.
Repetitions
Accept the default value for this field (0).
Save the record and click Submit Job to begin the initial extract.
Ongoing extracts follow automatically, separated by the repetition interval.
Creating PIMSI Dispatcher User Groups
During each synchronization cycle, the PIMSI Dispatcher by default sends synchronization task requests to the PIMSI engine for all users who have synchronization enabled. However, you can optionally filter the users for whom synchronization task requests are issued during each cycle by defining PIMSI Dispatcher user groups, and specifying different synchronization schedules for each group.
For example, if you create PIMSI Dispatcher user groups for different geographic regions, such as EMEA and the United States, then you can specify different synchronization schedules for each group; instead of all users being synchronized during each cycle, each user group can be configured to synchronize more frequently during their hours of business than during the evenings.
The procedure in this topic describes how to:
Define a PIMSI Dispatcher user group.
Assign users to the new PIMSI Dispatcher user group.
Create a job template for the PIMSI Dispatcher user group.
Create a PIMSI Dispatcher job based on the job template you have created.
To configure PIMSI Dispatcher user groups
Define a new PIMSI Dispatcher user group as follows:
Navigate to the Administration – Data screen, then the List of Values view.
Create a new record, specifying values similar to the following:
Type Display Value Language Independent Code Language Name PIMSI_DISPATCHER_GROUP
The display name of the PIMSI Dispatcher user group, for example, Sync Group EMEA
The name of the PIMSI Dispatcher user group, for example, Sync Group EMEA
Specify the language, for example, English-American
Assign users to the PIMSI Dispatcher group you defined in Step 1 as follows:
Navigate to the Administration – PIM Server Integration screen, Sync Access Control, and then the User Map view.
Select the user you want to associate with a PIMSI Dispatcher group.
In the Dispatcher Group field, select the PIMSI Dispatcher user group to associate with the user.
Save the User Map record.
Create a job template for the new PIMSI Dispatcher user group as follows:
Navigate to the Administration - Server Configuration screen, then the Job Templates view.
Create a new job template, specifying values similar to the following:
Name Component Component Type The name of the job template, for example, Sync Group EMEA
PIMSI Dispatcher
BusSvcMgr
In the Job Parameters list, add a job parameter to the job template, specifying values similar to the following:
Name Value Encoded Input Arguments
DispatcherGroup:value
where value is the name of the PIMSI Dispatcher user group you are defining.
For example, for the Sync Group EMEA user group, specify the following for the Value field:
DispatcherGroup:Sync Group EMEA
Create a new PIMSI job using the job template you created in Step 3 as follows:
Navigate to the Administration - Server Management screen, then the Jobs view.
In the Jobs list, click New.
In the Component/Job field, select the name of the job template you created in Step 3, for example, Sync Group EMEA.
In the Jobs list or Job Detail view, complete other fields as appropriate.
For information on these fields, see Creating the PIMSI Dispatcher Job.
Save the record and click Submit Job to start the initial extract.
Configuring Support for Items Archived in Microsoft Outlook
SSSE cannot distinguish between task and calendar items that have been archived and those that have been deleted from the message store. If an item is archived from Microsoft Outlook, then SSSE interprets this as a deletion of the item and deletes the corresponding record in Siebel Business Applications. However, you can choose to maintain Siebel records for calendar or task records that have been removed from the user's Microsoft Exchange message store due to archiving by specifying a value, in days, for the ArchiveGracePeriod parameter.
This task is an optional step in Roadmap for Configuring SSSE.
When you specify a value for the ArchiveGracePeriod parameter, SSSE determines whether an activity or appointment that no longer exists in Microsoft Outlook has been deleted or archived as follows:
If a deleted Microsoft Outlook event has an end date further in the past than the number of days specified by the ArchiveGracePeriod parameter, then the item is assumed to be archived and the corresponding record is not deleted from the Siebel database.
If a deleted Microsoft Outlook event has an end date more recent than the number of days specified by the ArchiveGracePeriod parameter, then the item is assumed to be deleted and the corresponding record is deleted from the Siebel database.
For example, if you specify a value of 7 for the ArchiveGracePeriod parameter, then SSSE treats a meeting that is older than 7 days, and that no longer exists in Microsoft Outlook, as an archived item. If the meeting was scheduled to occur less than 7 days ago, then it is treated as an item that was intentionally deleted (for example, because the meeting was cancelled) and is removed from Siebel Business Applications.
If you do not specify a value for the ArchiveGracePeriod parameter, then all items archived from a user’s Microsoft Exchange message store are treated as deleted items.
The following procedure describes how to specify a value for the ArchiveGracePeriod parameter.
To enable support for archived items
Log in to your Siebel application as an administrator.
Navigate to the Administration - PIM Server Integration screen, then the Configuration view.
Select the Exchange Calendar profile.
In the Configuration Parameters list, create a record with the following values:
Section Parameter Value Archive
ArchiveGracePeriod
n
where n is the number of days you want to specify for the archive grace period. The default value is 0.
Suppressing Email Invitations
Supressing Email Invitations feature prevents outbound calendar sync from pushing employees and / or contacts on a Siebel Calendar entry to the user's Exchange Calendar, thereby preventing the employees or contacts from receiving an invitation to a meeting.
The feature is useful in situations where a Siebel user wants to create a meeting in Siebel that is associated to a Contact, but they don't actually want to invite that contact to the meeting. Meeting descriptions/bodies may contain sensitive information not intended for contacts associated with a Siebel calendar item.
To suppress the outbound sync of Calendar Contacts
Navigate to Administration – Server Management, and then Jobs.
On the first applet, create New record and set Component = PIMSI Dispatcher. Accept the default values for other fields.
On the last applet, create a new record and set the following:
Name = Encoded Input Arguments
Value = SuppressOutboundContactAttendees:TRUE
To suppress the outbound sync of Calendar Employees
Navigate to Administration – Server Management, and then Jobs.
On the first applet, create a new record and set Component = PIMSI Dispatcher. Accept the default values for other fields.
On the last applet, create a new record and set the following:
Name = Encoded Input Arguments
Value = SuppressOutboundEmployeeAttendees:TRUE
You can combine multiple arguments in Encoded Input Arguments using a semi-colon as a delimiter.
For example, if you use Dispatcher Groups, you can:
Navigate to Administration – Server Management, and then Jobs.
On the first applet, create a new record and set Component = PIMSI Dispatcher. Accept the default values for other fields.
On the last applet, create a new record and set the following:
Name = Encoded Input Arguments
Value = DispatcherGroup:MyGroup;SuppressOutboundEmployeeAttendees:TRUE;SuppressOutboundContactAttendees:TRUE
Any parameter that is missing will use the default (which is FALSE for both "Suppress" parameters).
About Configuring Recurring Appointments
You can control the behavior of non-supported recurring meetings with no end date by using the parameter FanLimit, which is a number representing an absolute number of days in the future. The following sections summarize how the Siebel application handles recurring meetings.
Supported Meetings
Daily, Weekly, Monthly, and Yearly meetings are supported. Any recurring meetings with no end date are created in the Siebel application exactly as in Exchange. For example, if there is a recurring weekly meeting with no end date in Exchange, then there will be a recurring weekly meeting with no end date in the Siebel application.
All other recurrence patterns are not directly supported by the Siebel Calendar itself. For example, meetings scheduled for every other week cannot be directly entered into the Siebel Calendar. To address this inconsistency, SSSE performs special processing to ensure that the Exchange and Siebel calendars contain the same appointments.
Unsupported Meetings with an End Date
For unsupported recurring meetings with an end date, the meeting is fanned, which means that individual meetings are created to replicate the recurring meeting in Exchange.
For example, if a meeting in Exchange goes from April 1 to June 24 every other week, then the Siebel application creates seven individual meetings: April 1, April 15, April 29, and so on through June 27.
The Siebel application creates as many individual appointments as are needed to replicate the meetings in Exchange. The FanLimit parameter does not affect these meetings.
Unsupported Meetings without an End Date
For unsupported recurring meetings without an end date, it is impossible to create an infinite number of individual meetings to replicate the meetings in Exchange. Therefore, the meeting is initially fanned based on based on the value of the FanLimit parameter. However, added occurrences of the meeting are created as time passes, to replicate the recurring meeting without an end date.
For example, assume that FanLimit has the value 60. There is a meeting in Exchange that starts April 1, continues every other week, and lasts forever. Also, assume the first sync is on April 1.
Initially, the Siebel application creates five instances of this meeting with five instances. The reason is that May 31 is 60 days after April 1; between April 1 and May 31, a meeting that occurs every other week will take place on April 1, April 15, April 29, May 13, and May 27.
The next instance would take place on June 10, but the Siebel application has not yet created that meeting, because it is outside the FanLimit.
As time passes, the FanLimit window moves forward. On April 2, the FanLimit is June 1, on April 3, the FanLimit is June 2, and so on, until on April 11, the FanLimit is June 10.
If the PIMSI dispatcher’s FanLimit job is running daily, then the June 10 occurrence of the meeting will be created on April 11, as this occurrence is now within the FanLimit.
As time passes, new occurrences will continue to be created, replicating a recurring meeting with no end date.