Bookshelf Home | Contents | Index | Search | PDF

Siebel Communications Server Administration Guide > Using Email, Fax, and Other Systems > Other Communications Drivers >

Push Keep Alive Driver Parameters

---

Table 82 lists the supported parameters for the Push Keep Alive communications driver. The channel type for this driver is Keep-Alive.

Table 82.  Push Keep Alive Driver Parameters

Name	Required	Default Value	Description
LogDebug	No	FALSE	TRUE or FALSE If TRUE, data output to the log file is more detailed.
LogFile	No	push_{@UserName}.log	The name of the file where logging information will be written. If this parameter is empty, no log file is generated. Logging data is always appended to this file. Log files are created in the log subdirectory of the Siebel Server or Siebel Dedicated Web Client installation directory, depending on the client type and on your communications deployment. Optionally, if you want to use a single log file in a multichannel environment, you can specify the same log file name for all interactive drivers you are using.
MaxLogKB	No	128	Specifies the maximum size of the log file, in kilobytes (KB). When the log file is full, it is emptied completely, then logging begins again.
PushKeepAliveTimer	Yes	0	Specifies the interval, in seconds, for the heartbeat message sent by the Keep Push Alive driver to the Application Object Manager. and to each agent's Web browser. For example, if this parameter is set to 180, then the heartbeat message is sent every 180 seconds. The default value, 0, specifies that no heartbeat message is sent. Typically, this parameter would be defined as a parameter override in a driver profile that has been associated with the communications configuration.
ReleaseLogHandle	No	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 LogDebug is also FALSE, because logging is less intensive. When ReleaseLogHandle is FALSE, however, some log files may not be generated if the number of concurrent users exceeds the file-handle capacity provided by the operating system.

Bookshelf Home | Contents | Index | Search | PDF