Siebel Communications Server Administration Guide > Configuring Advanced Communications Features >

Using Push Keep Alive Driver for Session Connections


The Push Keep Alive communications driver provides a heartbeat message that can maintain connections for your communications sessions in some environments. You use this driver with Communications Session Manager, such as when you are using Siebel CTI.

The Push Keep Alive driver helps to solve problems that may be experienced in some environments, where push communications sessions between the Application Object Manager and a user's Web browser are sometimes dropped. A connection may be dropped if messages have not been pushed to an agent for a particular length of time.

The Push Keep Alive driver sends a heartbeat message to the Application Object Manager, and each agent user's browser, at a regular interval. This heartbeat message allows the push connection applicable to each agent's communications toolbar not to be dropped in such cases. The heartbeat interval is specified using a driver parameter.

NOTE:  When you use the Push Keep Alive driver, you must also set the ChannelCleanupTimer configuration parameter to make sure that abandoned connections for communications sessions are dropped promptly. For more information about the ChannelCleanupTimer configuration parameter, see Parameters for Communications Configurations. For information about how to set this parameter, see Specifying Parameters for Communications Configurations.

To use the Push Keep Alive driver

  1. Start the Siebel application, such as Siebel Call Center, logging in as the system administrator (for example, as the user SADMIN).
  2. Navigate to Administration - Communications > Communications Drivers and Profiles.
  3. Create a new record in the Communications Drivers list and complete the fields as described in the following table.
    Parameter
    Value

    Name

    Enter Push Keep Alive

    Channel Type

    Select Push Keep Alive from the drop-down list.

    Interactive

    Select this check box.

    Library Name

    Enter sscmimed

  4. Click the Driver Parameters tab and enter the values as described in the following table.
    Parameter
    Value

    LogDebug

    FALSE

    LogFile

    push_{@UserName}.log

    MaxLogKb

    128

    PushKeepAliveTimer

    0

    ReleaseLogHandle

    TRUE

  5. Click the Profiles tab and enter a new record with a name that identifies the Profile with the Push Keep Alive communications driver. For example, enter Push Keep Alive.
  6. In the Profile Parameter Overrides child applet, enter a record with the following values.
    Parameter
    Value

    Name

    Select PushKeepAliveTimer from the drop-down list.

    Value

    Enter the time interval (in seconds) between the Push Keep Alive driver sending messages. For example, enter 180 to have the driver send a heartbeat message every 180 seconds.

  7. Click All Configurations in the application link bar and select your configuration in the displayed list.
  8. Click the Profiles screen tab.

    The list of profiles currently associated with your configuration appears.

  9. Click New.

    The Add Communications Profiles dialog box appears. This dialog box displays the list of currently available profiles.

  10. Select Push Keep Alive, then click OK.

    This associates the Push Keep Alive communications driver with your configuration. It means that a heartbeat message is sent at the interval that you specify (for example, every 180 seconds).

  11. If you use the server component Communications Configuration Manager to cache your configuration, shut down and restart your Siebel Server to apply the changes made in steps Step 1 to Step 10. If you do not use Communications Configuration Manager, log out and log into the application for these changes to take effect. For more information about the Communications Configuration Manager, see Administering Communications Configuration Manager.
Siebel Communications Server Administration Guide Copyright © 2006, Oracle. All rights reserved.