Push Keep Alive Driver Parameters

The following table lists the supported parameters for the Push Keep Alive communications driver.

Name	Required	Default Value	Description
LogDebug	No	False	True or False If True, then data output to the log file is more detailed.
LogFile	No	push_{@UserName}.log	The name of the file where logging information is written. If this parameter is empty, then 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 installation directory. Optionally, if you want to use a single log file in a multichannel environment, then you can specify the same log file name for all of the interactive drivers that 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.
PushKeep AliveTimer	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 is 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 is released periodically, after logs have been generated. The default setting of True provides better performance. When ReleaseLogHandle is False, however, some log files might not be generated if the number of concurrent users exceeds the file-handle capacity provided by the operating system.