Bookshelf v7.5: Configuring the Assignment Manager Component

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 27 shows the parameters you can change.

To configure the Assignment Manager component

From the application-level menu, choose View > Site Map > Server Administration > Components.

In the Name field in the Components list, select the Assignment Manager component, and make sure it is running on the correct server.

Click the Component Parameters view tab.

In the Component 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 Server Administration Guide.

Table 27 shows the parameters used by Assignment Manager that you can change. For a list of predefined server components and generic parameters, see Siebel Server Administration Guide.

Table 27. Assignment Manager Component Parameters
Parameter Name	Parameter Alias	Data Type	Description	DefaultValue
Check version iterations	CheckVerIter	Integer	The lag time before the component checks if there is a change to the rules version, that is, when the Release button was pressed. 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 multi-threaded service.	1
Maximum Tasks	MaxTasks	Integer	Maximum number of running tasks for a service.	2
Minimum MT Servers	MinMTServers1	Integer	Minimum number of active servers for a multi-threaded service.	1

1Applies only to the assignment server and other multi-threaded request-based servers.

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.

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.