Example Settings for Siebel Application Object Manager Parameters

Along with other factors such as think time, the calculation of MaxTasks, MaxMTServers, and MinMTServers depends on your assumptions for target_number_of_users and anon_users, as previously described. Example settings follow for Siebel Call Center and Siebel eService.

Example Settings for Siebel Call Center

For Siebel Call Center, assume (for example) a think time of 30 seconds, and assume that target_number_of_users = 500. For this application, anon_users is not a factor. Your parameter values would be like the following:

MaxTasks = 500
MaxMTServers = 500 divided by 100 = 5
MinMTServers = MaxMTServers = 5

Example Settings for Siebel eService

For Siebel eService, assume (for example) a think time of 30 seconds, and assume that target_number_of_users = 500. Depending on your implementation, anon_users might be about 25% of target_number_of_users (or 125). Your preliminary parameter values would be like the following:

MaxTasks = (500 plus 125) = 625
MaxMTServers = (500 plus 125) divided by 100 = 6.25 = 7 (round up)
MinMTServers = MaxMTServers = 7

Adjust the value of MaxTasks. The variable X = the remainder of (625 divided by 7) = 2. Increment MaxTasks by (MaxMTServers minus X): 625 plus (7 minus 2) = 625 plus 5 = 630. Therefore, the final calculations for parameter values would be like the following:

MaxTasks = 630
MaxMTServers = MinMTServers =7

Note: The settings of MaxTasks and MaxMTServers also help determine the setting of the parameter SessPerSisnConn, which sets the number of sessions per SISNAPI connections. For more information, see Configuring SISNAPI Connection Pooling for Siebel Application Object Managers.