HCL Notes and Domino wiki: Lotus Notes Traveler administration: Lotus Traveler

Lotus Traveler - Forcing Data Limits for End Users

Added by ~Xagra Loprechekoden | Edited by ~Xagra Loprechekoden on June 10, 2011 | Version 14

Actions ▼

Abstract

Abstract

Forcing Data Limits for End Users

Tags: Lotus Notes Traveler

Overview

Lotus Traveler support has seen some PMRs related to poor server performance or even server crashes when one or more end users have selected "No Limit" for mail and calendar on the device. In general selecting "No Limit" is not an issue, but it can be a problem when a Lotus Traveler server is running at or near capacity or the particular end user has a large amount of calendar data or a large Inbox. Once the particular user completes the initial sync, performance should return to normal, however in some cases it can take hours to complete a full calendar and Inbox sync. If the server is crashing as a result of insufficient memory, the sync will resume once restarted and the server may see a temporary repeated crash scenario.

In Lotus Notes Traveler 8.5.2.3 and later releases, an administrative setting has been added that will enforce a maximum filter window for all users. Once set, if a user selects "No Limit", instead of receiving all data for a particular application type, they will only receive data that passes the Administrator defined filter limit. This should prevent unexpected heavy load on the server. The settings will apply to all users on the system.

Settings

These settings are not present and not enabled by default. To set a maximum filter size, add these parameters to the TrueSyncServer section of data\traveler\cfg\NTSConfig.xml.

Setting	Description
<PROPERTY NAME="USER_EMAIL_LIMIT" VALUE="14"/>	Sets maximum mail filter window.
<PROPERTY NAME="USER_EVENTS_LIMIT" VALUE="30"/>	Sets maximum calendar filter window.
<PROPERTY NAME="USER_NOTES_LIMIT" VALUE="30"/>	Sets maximum journal filter window.

All values are specified in days. Mobile device users can always set their filter limit to be lower than this defined maximum, but anything higher will not be honored by the server. A restart of the server will be needed for the settings to take effect.