Home
Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
Administering HCL Traveler
The HCL Traveler server component functions as a Domino® server add-in task and responds to Domino server console commands. Topics in this section describe common administrative tasks for administering a HCL Traveler server.
Enforcing data sync limits
Administrators can enforce synchronization data limits for all users using a setting in the Default Settings document.

Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
- Planning for installation and configuration
  There are many installation and configuration considerations you should review before installing the HCL Traveler server.
- Installing the HCL Traveler server
  The following topics describe options for installing and uninstalling the server:
- Configuring HCL Traveler server
  The HCL Traveler configuration settings are part of the Domino® server document. The first time that the HCL Traveler server is started, it performs any necessary configurations. You might want to perform additional configurations beyond the basics. The following topics describe additional configuration options.
- Administering HCL Traveler
  The HCL Traveler server component functions as a Domino® server add-in task and responds to Domino server console commands. Topics in this section describe common administrative tasks for administering a HCL Traveler server.
  - Starting and stopping the server
    The HCL Traveler server and the HTTP server automatically start if you accept the default settings during installation. Use the commands in this topic to manually start or stop the HCL Traveler server.
  - Using the administration application
    The HCL Traveler administration database is contained in the LotusTraveler.nsf. This database contains the user interface that is used to view mobile user and device information, as well as set default device preference and security policies.
  - Assigning preferences and security settings to devices
    There are different ways to assign settings that determine how users work with the HCL Traveler server. You can use the built-in set of default device preferences and security settings that HCL Traveler provides, which is simpler. Or you can create a HCL Traveler policy settings document, which provides greater flexibility and control but is more complex to configure.
  - Device security
    There are a number of considerations to be aware of when securing different device types.
  - Working with attachment security settings
    You can control how HCL Traveler clients manage file attachments and images.
  - Remote wipe
    If a mobile device is lost or stolen, an administrator can issue a remote wipe command to remove all sensitive data from the device. You can remove the HCL Traveler application and data from the device and, depending on the device, restore the device to the factory default settings.
  - Console commands
    This topic provides a detailed description of the HCL Traveler console commands.
  - ***
  - ***
  - Controlling access to HCL Traveler
    When a user leaves the company or a device is lost or stolen, you must remove or restrict access to the HCL Traveler server. This section covers methods for removing and restricting access.
  - Deleting a user from HCL Traveler
    An administrator can remove old or invalid users from the HCL Traveler administrator UI and database. This should only be done for users where access is already restricted using a HCL Traveler or Domino® server access list, or who are no longer listed in the Domino directory.
  - Creating links to start the HCL Verse mobile app
    Create links that a user can click to start the HCL Verse mobile app from a web page or email.
  - Enabling syncing of read or unread changes
    Unread replication is enabled for each user automatically by the HCL Traveler server so that unread marks sync correctly with the device. This section explains how to activate unread replication manually using the Domino® Administrator client.
  - Repeated crash protection
    When certain Notes® documents are corrupted or contain non-standard content, they can cause the HCL Traveler server to repeatedly crash as it tries to process these documents. A repeating crash prevention feature exists to help minimize HCL Traveler server outage in these instances.
  - Maintaining the HCL Traveler database
    Whether running standalone HCL Traveler servers with the internal database or a pool of servers with an enterprise database, the database requires periodic maintenance to maintain optimal performance.
  - ***
  - Enforcing data sync limits
    Administrators can enforce synchronization data limits for all users using a setting in the Default Settings document.
  - Log types
    HCL Traveler has many different logs with a variety of purposes.
  - HTTP request handling and 409 responses
    HCL Traveler handles HTTP requests in specific ways that may result in 409 responses.
  - Confirming external recipients on Android devices
    For HCL Verse for Android clients, you can choose to prompt the user to confirm the sending of mail to external recipients. This provides an extra step to help prevent the unintentional sending of mail outside of your organization.
  - Adaptive Initial Sync
    Adaptive Initial Sync (AIS) helps ensure server availability in certain server bring up or recovery situations.
  - FCM messaging for HCL Verse for Android clients
    HCL Traveler server can use Firebase Cloud Messaging (FCM) for real time push notifications to keep your Mail, Calendar, Contact and To Do data on your HCL Verse for Android clients up to date. Google has deprecated GCM and replaced it with FCM.
  - How synced data moves through the system
    When a device needs to sync data with the user's mail server, the user registers that device with the HCL Traveler server. This involves some initial setup which includes negotiating security settings as well as data options and filters to be used when syncing the data from the user's mail database to the device and vice versa.
  - How HCL Traveler processes attachments
    There are several issues to be aware of in how HCL Traveler processes attachments.
  - ***

Enforcing data sync limits

Administrators can enforce synchronization data limits for all users using a setting in the Default Settings document.

Once these are set, if a user selects Unlimited for Calendar , Journal, and Mail data, instead of receiving all data for a particular application type, they will only receive data that passes the Administrator defined filter limit.

This helps prevent unexpected heavy loads on the server. The settings apply to all users on the system.

Settings

Using the HCL Traveler administration database, select the Device Settings view and then edit the Default Settings document. Select the Preferences tab and then the Filter Settings tab. The default value will be set to Unlimited, meaning that no filter is applied by the server by default. To set a filter limit, enter a number in days for one of the following settings. While mobile device users can set their filter limit lower than the defined maximum, anything higher will not be honored by the server.

Table 1. Filter settings
Setting	Description
Email filter limit	Mail older than the Email filter limit will not be synchronized with the device.
Past events filter limit	Calendar events older than the past events filter limit will not be synchronized with the device. Note that recurring events that have an instance within the filter window will be synchronized, even if they have instances that start earlier that the past events filter limit.
Future events filter limit	Calendar events in the future that occur beyond the future events filter limit will not be synchronized with the device. Note that recurring events that have an instance within the filter window will be synchronized, even if they have instances that occur beyond the future events filter limit.
Journal filter limit	Journal entries modified earlier than the limit will not be synchronized to mobile devices that support Journal sync.

Note: In earlier HCL Traveler releases 8.5.2.3 to 8.5.3.3, data sync limits were set for the server using a setting in the NTSConfig.xml file. During upgrade, these settings, if found, will be migrated to the corresponding notes.ini setting, such as NTS_USER_EMAIL_LIMIT, NTS_USER_EVENTS_LIMIT and NTS_USER_NOTES_LIMIT. These notes.ini settings are no longer used, except when migrating from a pre-8.5.3.100 version. In this case, their value will be migrated into the Default Settings document.