|Bookshelf Home | Contents | Index | PDF|
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 considering SSSE performance issues. However, this topic discusses some configuration recommendations that are particularly important for ensuring optimum performance for SSSE.
The ConnectorMaxUsers parameter is a Siebel Enterprise Server parameter that defines the maximum number of users in the Enterprise who can be assigned to each instance of the DCOM Exchange Connector. In general, if you increase the value of this setting, your DCOM Exchange Connector computers use less memory for connector instances.
In versions of SSSE prior to Siebel CRM version 8.0, it was useful to set ConnectorMaxUsers to a low value when performing many initial extracts. This was because initial extracts could share connector instances with ongoing synchronizations unless ConnectorMaxUsers (which was then called MaxUsers) was set to a value of 1. When an initial extract shared a connector instance with ongoing synchronizations, there was a chance that the ongoing synchronizations might be delayed while the initial extract used the connector instance connection to the Microsoft Exchange Server. However, beginning with Siebel CRM version 8.0, every initial extract is automatically assigned to a dedicated connector instance which terminates when the initial extract operation is complete. The ConnectorMaxUsers parameter now applies only to ongoing synchronizations.
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.
The exact settings to use for your implementation depend on the hardware you use. Each connector instance uses about 25 MB of memory. As an example, if you have between 1 and 2 GB of memory available for connector instances to use, you could set ConnectorMaxUsers to 1 and set MaxTasks to 50.
Perform some initial extract test runs to assess the amount of CPU and memory that are used with your initial parameter settings. Check the connector computers and the Siebel Servers where your PIMSI Engine components are running. If you have ample CPU and memory still available, you can try increasing the value of MaxTasks.
When you are satisfied with your ConnectorMaxUsers and 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.
|Siebel Server Sync Guide||Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.|