Formulas for Calculating Siebel Application Object Manager Parameter Values

Use the following formulas for calculating parameter values for your Siebel Application Object Manager components:

• MaxTasks = target_number_of_users plus anon_users

• MaxMTServers = (target_number_of_users plus anon_users) divided by 100

• MinMTServers = MaxMTServers

As necessary, after making your initial calculations, round up MaxMTServers to the nearest integer, calculate the remainder (X) of MaxTasks divided by MaxMTServers, then increment MaxTasks by adding (MaxMTServers minus X). You do this to make sure that the ratio of MaxTasks divided by MaxMTServers is an integer.

The following descriptions apply to the variables and figures used in the formulas:

• target_number_of_users is the maximum number of concurrent user sessions that your Siebel Application Object Manager will support (for users who are logged in to the application).

  The maximum number of concurrent users is limited by the value of the MaxTasks parameter for the Siebel Application Object Manager, by the number of multithreaded processes you are running (determined by MaxMTServers and MinMTServers), and, effectively, by your hardware resources.

• anon_users is the number of sessions on the Siebel Application Object Manager that are dedicated to anonymous users (threads that support users who do not log in).

  • For employee applications like Siebel Call Center, anonymous users are not supported, so this is not a factor.

  • For customer applications like Siebel eService, anonymous users might be approximately 25% of the target number of users. However, the actual figure depends on the business requirements for a specific deployment, and could be much higher, for example.

• In the MaxMTServers formula, the figure of 100 is the approximate maximum number of concurrent threads that each multithreaded process on the Siebel Application Object Manager can support. The number 100 is a rule of thumb. Use the number that is appropriate for your deployment.

Note: A ratio of 100 for threads per multithreaded process works for most Siebel Application Object Manager usage scenarios. However, if your deployment involves a shorter think time than 30 seconds, or a heavier than average load per thread, then each multithreaded process will support fewer concurrent threads. Conversely, a longer think time or a lighter average load will support more concurrent threads. For more information about how the ratio of threads per multithreaded process relates to think time, see Performance Factors for Siebel Application Object Manager Deployments.