Bookshelf Home | Contents | Index | Search | PDF

Performance Tuning Guide > Tuning Siebel Communications Server for Performance > Best Practices for Session Communications Tuning >

Conserving AOM Server Resources Through Caching

---

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 AOM.

These caching mechanisms may be used together or separately. For more information, refer to Siebel Communications Server Administration Guide.

• CommConfigCache parameter (AOM). Setting the CommConfigCache parameter on the AOM to TRUE caches communications configuration data when the first agent logs in. For agents associated with the same communications configuration, each agent session uses the same cached data. See also Tuning the AOM Component.
  • Performance is improved for subsequent agent logins, because the configuration data is loaded from the cache rather than from the database.
  • AOM scalability is also improved because configuration data is shared in AOM memory across agent sessions, thus conserving server resources even as the number of agent sessions increases.
• CommConfigMgr server component and CommConfigManager parameter (AOM). The CommConfigMgr server component caches communications configuration data when the first agent logs in. Setting the CommConfigManager parameter on the AOM 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 this component to cache configuration data does not, by itself, improve AOM scalability, because configuration data is separately loaded for each agent session rather than shared across agent sessions.
  • If you use both the CommConfigMgr component and the CommConfigCache parameter, then the AOM loads configuration data into its cache from the CommConfigMgr cache.

Bookshelf Home | Contents | Index | Search | PDF