Setting the heartbeat algorithm maximum interval

Normally, it is not necessary to modify the maximum interval. However, if you know the network timeout values specific to your environment, then some efficiency may be gained by customizing it.

It is possible for the connection between a device and server to time out without the device being notified of the outage. In this case, changes on the server that need to be pushed to the client are not pushed until a later time. The heartbeat interval prevents the time out and maintains the connection, but it can also decrease battery life.

By automatically adjusting the heartbeat interval to slightly less than the smallest timeout, IBM Traveler can automatically maintain the connection.

Although the heartbeat interval for each connected client is automatically adjusted by IBM Traveler to be optimal, the configuration parameters can be tweaked to slightly improve operation. By default, the Heartbeat Algorithm Maximum Interval is set to 15 minutes in the IBM Traveler server configuration document. If you have devices earlier than Lotus Notes® Traveler 8.5.2 that use TCP push, leave the max at 15 minutes. But, if you are running all devices on IBM Traveler 8.5.2 or later using HTTP push, there are advantages to increasing the maximum setting to 30, 45, or 60 minutes.

If you do modify the heartbeat algorithm maximum interval, set it to a number slightly less than the timeout of the underlying network connection for all users, if known. For example, if all IBM Traveler clients are connecting over a VPN that has an idle timeout of 30 minutes, then set the maximum heartbeat interval to 28 or 29 minutes.

Apple devices use a different heartbeat algorithm (the Exchange ActiveSync algorithm). The Exchange ActiveSync algorithm uses the IBM Traveler minimum and maximum intervals, so these apply to all devices. The other IBM Traveler heartbeat algorithm settings apply only to other devices.