Siebel Performance Tuning Guide > Tuning Siebel Communications Server > Guidelines for Session Communications Tuning >

Conserving Siebel Application Object Manager Server Resources Through Caching

This topic is part of Guidelines for Session Communications Tuning.

You can use two caching mechanisms to make communications configuration data load faster for each agent session and to reduce demand on server resources on the Siebel Application Object Manager.

These caching mechanisms can be used together or separately. For more information, see Siebel CTI Administration Guide.

• CommConfigCache parameter. Setting the CommConfigCache parameter on the Siebel Application Object Manager to TRUE caches communications configuration data when the first agent logs in. Configuration data is cached until the Siebel Application Object Manager is restarted. For agents associated with the same communications configuration, each agent session uses the same cached data. See also Tuning the Siebel Application Object Manager Component.
  • Performance is improved for subsequent agent logins, because the configuration data is loaded from the cache rather than from the database.
  • Siebel Application Object Manager scalability is also improved because configuration data is shared in Siebel Application Object Manager memory across agent sessions, therefore conserving server resources even as the number of agent sessions increases.
• CommConfigMgr server component and CommConfigManager parameter. The CommConfigMgr server component caches communications configuration data when the first agent logs in. Setting the CommConfigManager parameter on the Siebel Application Object Manager to TRUE enables this server component.
  • Performance is improved for subsequent agent logins, because the configuration data is loaded from the cache rather than from the database.
  • Using the CommConfigMgr component to cache data speeds up the login process and reduces memory usage per agent session because the component uses configuration data that was already cached on the Siebel Application Object Manager component.
  • Although it is not required to use the CommConfigMgr component in conjunction with the CommConfigCache parameter for Siebel Application Object Manager, if you use them together, communications configuration data gets cached at the enterprise level rather than only for the Siebel Application Object Manager. Overall performance can be enhanced compared to using each of these mechanisms separately.