|
Siebel Assignment Manager Administration Guide > Running Assignment Manager > Preparing to Run Assignment Manager >
Configuring the Assignment Manager Component
Before running Assignment Manager, you should configure the Assignment Manager component to enhance its performance for your implementation by adjusting the appropriate parameters. Table 31 shows the parameters you can change. To configure the Assignment Manager component
- From the application-level menu, choose Navigate > Site Map > Administration - Server Configuration > Servers.
- In the Siebel Servers list, select your server (if more than one server appears) and make sure the Assignment Manager component is enabled on that server (the Enable State field in the Components list should have a check mark for the Assignment Manager component).
- Click the Parameters subview (if not already active).
- In the Parameters list, select the component parameters of interest, and adjust the values as required by your implementation to achieve optimal performance.
- After you have determined the optimal settings, make sure that the MinMTServers parameter is set to a current value greater than 0, and then restart the Siebel Server.
This starts the specified number of Assignment Manager components. For more information about starting and restarting the Siebel Server, see Siebel System Administration Guide.
Table 31 shows the parameters used by Assignment Manager that you can change.
Table 31. Assignment Manager Component Parameters
|
|
|
|
|
Check version iterations |
CheckVerIter |
Integer |
Defines the frequency of time Assignment Manager checks whether rule version has changed. This also represents the time lag the new rules take effect after clicking the Release button. One integer value equals ten seconds (minimum value is 1). |
6 |
Default Tasks |
DfltTasks |
Integer |
Default number of service tasks to start (server mode only). |
0 |
Log txn only on change |
LogTxnChgOnly |
Boolean |
Log transaction only when there is a net change in assignment (for example, sales team updated). |
TRUE |
Maximum MT Servers |
MaxMTServers |
Integer |
Maximum number of active servers for a multithreaded service. |
1 |
Maximum Tasks |
MaxTasks |
Integer |
Maximum number of running tasks for a service. |
2 |
Minimum MT Servers |
MinMTServers |
Integer |
Minimum number of active servers for a multithreaded service. |
1 |
The following bulleted points explain why you might want to configure some of the various Assignment Manager component parameters:
- Check version iterations. Changing this parameter to a small value, such as 1, reduces the potential for invalid assignment. For example, running interactive assignment before Assignment Manager detects that the Release button was recently pressed causes assignment based on the previous version of assignment rules. By having a small iteration value, Assignment Manager checks for a newer version of assignment rules more frequently. Test your deployment with this lower parameter value to make sure it does not interfere with any other database activity.
- Log txn only on change. Setting this parameter to FALSE causes Assignment Manager to log a transaction in the S_DOCK_TXN_TABLE on reassignment even when there is no change in rules or assignees. By detault, this parameter is set to TRUE. For information about how this parameter works with regard to merge conflicts, see Siebel Remote and Replication Manager Administration Guide.
- Maximum MT Servers. This parameter controls the maximum number of Assignment Manager server processes that are running at any time (when MaxMTServers > MinMTServers). Generally, the default value is sufficient for most deployments as server processes and Assignment Manager have large resource requirements.
- Maximum Tasks. This parameter controls the maximum number of server threads that can run at any time. For Assignment Manager, this controls the maximum number of assignments that can be processed concurrently. The value of this parameter should be set to the maximum anticipated concurrent requests (dependent on your server's capabilities).
- Minimum MT Servers. This parameter controls the number of Assignment Manager server processes that are started when the Siebel servers starts up. If this value is set to zero, Assignment Manager is disabled. It is recommend to use the default value of one, as server processes and Assignment Manager have large resource requirements.
|
