Siebel Server Administration Guide > Application Object Manager Administration > Siebel Application Object Manager Parameters >

Determining Application Object Manager Parameter Values


When setting up the eApplication (such as Siebel eService), you need to consider the application, coding, number of users, and other variables that may impact the performance of the Application Object Manager (AOM). You can enhance performance by adjusting the values of generic and component-specific parameters for the AOM.

You should adjust the values of these parameters as required by your implementation to achieve optimal performance. For example, you should make sure that the Maximum MT Servers and Minimum MT Servers parameters be set correctly to support the anticipated number of Web client users. Because the default number is 1, you should increase the number of MT servers according to your system requirements.

When setting the Maximum Tasks parameter, it is important to know how many concurrent users will be using the system and then allow for some extra tasks. Remember that anonymous tasks may be created to handle login information and will reduce the total number of concurrent tasks that can run. Generally, anonymous tasks represent 10 percent of user tasks. For this reason, you should set the Maximum Tasks parameter to a value greater than 2, because at least one task will be started for the AOM, and at least another task will be started to handle the client connection after the login has been established. After you have determined the optimal setting, restart the Siebel Server to automatically register the AOM services.

Indications that the settings for Maximum Tasks and Maximum MT Servers parameters have reached their maximum values and need reconfiguration include:

NOTE:  These error messages are not exclusive to improperly set parameter values.

If your system will not be used at night, you may also want to use the Siebel Server Manager command-line interface to shut down the AOM for your site on a nightly basis to free resources in your system. For information on using the Siebel Server Manager command-line interface, see Using the Siebel Server Manager Command-Line Interface.

NOTE:  If users do not log out properly by navigating to File >Log Out on the application-level menu, the Object Manager task is left hanging and only terminates when the SessionTimeOut parameter is reached. Therefore, if a user logs out improperly and logs back in, two Object Manager tasks are created for that user.


 Siebel Server Administration Guide 
 Published: 23 June 2003