Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Enabling Session Communications and Simulation >
Parameters for Application Object Manager and Dedicated Web Client
This section describes parameters for the Application Object Manager (for Siebel Web Client) and Siebel Dedicated Web Client. These parameters are described in Table 61.
- For deployments of the Siebel Web Client ("zero footprint"), parameters are specified as server component parameters for the Application Object Manager that is to support communications users.
- For deployments of the Siebel Dedicated Web Client (where applicable), parameters are specified in the [Communication] section of the configuration file, such as uagent.cfg for Siebel Call Center, for each communications user's Siebel client.
Table 61. Object Manager and Dedicated Client Parameters for Communications Sessions Parameter Name Display Name (for Component Parameter) Default Value Description CommConfigCache Communication Configuration Cache FALSE Enables or disables the caching of communications configuration data on the Application Object Manager.Note: This parameter applies to the Siebel Web Client only, not to the Siebel Dedicated Web Client.
- When this parameter is FALSE, communications configuration data is loaded separately for each agent session, with no caching on the Object Manager.
- When this parameter is TRUE, the Application Object Manager loads and caches communications configuration data.
When CommConfigCache is TRUE, after the first agent logs in, subsequent agent logins for the same configuration will download the configuration data from the cache. This speeds up the login process and reduces memory usage per agent session.This parameter may be used with or without the Communications Configuration Manager component and the CommConfigManager parameter.See also the description of the CommConfigManager parameter. CommConfigManager Communication Configuration Manager FALSE Enables or disables use of the Communications Configuration Manager (CommConfigMgr) for loading and caching communications configuration data to reduce configuration downloads.
- When this parameter is FALSE, communications configuration data is loaded separately for each agent session, with no caching.
- When this parameter is TRUE, Communications Configuration Manager is employed to load and cache communications configuration data. After the first agent logs in, subsequent agents using the same configuration will download the configuration data from the cache, thereby speeding up the login process.
For more information, see Administering Communications Configuration Manager. CommConfigManagerName Communication Configuration Manager Name CommConfigMgr Specifies the name of the Communications Configuration Manager server component to use when the parameter CommConfigManager is TRUE.A global deployment may, for example, use different components for different languages within the same enterprise. CommEnable Enable Communication FALSE Enables or disables session-based communications for agents.
- When this parameter is TRUE, the communications toolbar and menu elements are displayed and activated for agents who are associated with a configuration.
- When this parameter is FALSE, the communications toolbar and menu elements are not displayed.
If an agent is not associated with a configuration, the communications toolbar is not displayed, even if CommEnable is TRUE.Enabling communications has many additional requirements, which are described in Configuring Session Communications. CommLocalDriver Local Communication Driver FALSE (as component parameter)TRUE (as configuration file parameter for Dedicated Web Client) Specifies on which machine interactive communications drivers should be loaded by the channel manager for each agent communications session.
- For either the Siebel Web Client or the Siebel Dedicated Web Client: when this parameter is FALSE, interactive drivers are loaded on the Siebel Server machine where Communications Session Manager is running.
- For the Siebel Dedicated Web Client: if this parameter is TRUE in the configuration file, interactive drivers are loaded on each agent's Siebel client.
- For the Siebel Web Client: if this parameter is TRUE on the Application Object Manager, interactive drivers are loaded on the Application Object Manager.
For more information, see Administering Communications Session Manager. CommLogDebug Log Debug Message FALSE Specifies whether the log file specified with the CommLogFile parameter should contain extra detail. CommLogFile Log File SComm_user.log Specifies the name of the log file to create for the agent's communications session, where user is the agent's Siebel login name.The file is written in the log subdirectory of the Siebel Server or Siebel Dedicated Web Client installation directory. CommMaxLogKB Maximum Log Size (KB) 1024 Specifies the maximum size, in Kilobytes, of log files specified using CommLogFile. CommMaxMsgQ Maximum Message Queue 64 The maximum number of messages to be queued for the agent's communications toolbar.If the number of messages exceeds the maximum, the oldest message is discarded. For example, with the default value of 64, the most recent 64 messages are queued. If a 65th message arrives, the oldest message in the queue is discarded in order for the new message to be received.It is recommended that you use the default setting unless you require changing it.If you set this value too low, older messages might be deleted in some cases, such as in a slow network environment.If you set this value too high, server resources may be overused, by storing many messages for agents who experience browser problems that interrupt the session.The behavior is also subject to the general session timeout defined for Siebel Web Client deployments. If an agent's session times out, all toolbar messages for the session are cleared. CommReleaseLogHandle Release Log Handle TRUE Indicates that the log file handle for each agent should be released periodically, after logs have been generated.Performance for agent sessions can be improved by setting this parameter to FALSE. This may be most effective if CommLogDebug is also FALSE, because logging is less intensive.When CommReleaseLogHandle is FALSE, some log files may not be generated if the number of concurrent users exceeds the file-handle capacity provided by the operating system. CommReqTimeout Request Timeout 600 Specifies the number of seconds to wait for a response from the Communications Session Manager for a particular communications interaction. CommSimulate Simulate Communication FALSE Enables or disables the Communications Simulator.
- When this parameter is TRUE, communications simulation is enabled for agents.
- When this parameter is FALSE, communications simulation is disabled for agents.
The Communications Simulator can be enabled in other ways as well. Additional requirements are described in Enabling Communications Simulation.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Communications Server Administration Guide Published: 23 June 2003 |