Siebel Incentive Compensation Administration Guide > Optimizing Sales Credit Engine Performance >
Sales Crediting Engine Advanced Setup
Often, an organization wants to use a process for assigning a sales team and credit allocation to an order rather than adding the sales team manually. Siebel Incentive Compensation supports the crediting process using the Sales Crediting Engine.
The following tables describe the server parameters that you can configure to tailor the crediting engine's performance to different business processes and requirements. For example, you can optimize the crediting engine to assign credit to new transactions every 30 minutes.
Table 46 lists the crediting engine server parameters that can be optimized.
Table 46. Crediting Engine Server Parameters
Parameter Name
|
Description
|
Default
|
Comments
|
Max DB Operation Threads
|
Maximum Number of threads executing database operations
|
15
|
Should be between two and three times the total Assignment Manager threads up to a maximum of 40
|
Max Size of One Item Set
|
Maximum Number of items sent to AM in one request
|
100
|
Maximum value is 200 depending on the item id value size. The value should be around 2048/(item ID value size plus 3)
|
Max New Item Num
|
Maximum number of New Items returned during a poll
|
700
|
This value is determined by the time it takes the PollNewItems method to detect items and change their status. The value should be set so that the subsequent poll request does not coincide with the first.
|
Max Requests AM
|
Maximum Number of item sets sent to AM at one time
|
20
|
The number of Assignment Manager threads processing a rule group determines this value.Assignment Manager should be kept busy. Start with a number that is two times the number of threads.
|
Maximum Tasks
|
Maximum number of running tasks for a service
|
20
|
This should equal the sum of Max DB Operation threads and the number of threads that are waiting for new items.
|
Sleep Time between AM Requests
|
Sleep Time in seconds between subsequent sets of AM Requests
|
5
|
This can be set lower if the crediting engine has items waiting in queue to be processed and is not sending them out to the Assignment Manager fast enough.
|
Table 47 lists parameters and optimizing suggestions for the crediting database operations server component.
Table 47. Crediting Database Operations Server Component Parameters
Parameter Name
|
Description
|
Default
|
Comments
|
Maximum Tasks
|
Maximum number of running tasks for a service.
|
20
|
This should be equal to the Max DB Operation Threads parameter in the Crediting Engine server component.
|
OM - Model Cache Maximum
|
Maximum number of objects cached in the model cache.
|
20
|
This should be equal to the Maximum Tasks parameter.
|
Table 48 lists the parameters and performance optimization suggestions for the Assignment Manager server component.
Table 48. Assignment Manager Server Component Parameters
Parameter Name
|
Description
|
Default
|
Comments
|
Maximum Tasks
|
Maximum number of running tasks for a service.
|
10
|
This should be set to about twice the number of processors on the system.
|
Minimum Number of cached thread contexts
|
Minimum Number of cached thread contexts for a multi-threaded server process on startup.
|
2
|
This should be equal to the Maximum Tasks parameter plus 1 so that all of the context cache are loaded at startup itself.
|
Maximum Number of cached thread contexts
|
Maximum Number of cached thread contexts for a multi-threaded server process on startup.
|
10
|
This should be equal to the Maximum Tasks parameter plus 1.
|
