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.
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.
Restricting access using server document access fields
An administrator can define which users are allowed to connect to the HCL Traveler server, or create explicit denial lists for users that should be denied access to the server. In a Traveler HA environment, repeat the procedure on each server in the pool.

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.
  - travelerUtil commands
    The travelerutil is a command line tool located in the <domino data>\traveler\util directory. Enter travelerUtil help while running the tool to display the full list of options.
  - Delegation support
    HCL Traveler can allow delegates to access mail files owned by other users.
  - 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.
    - Denying or allowing access to a device
      An administrator can prevent individual devices that are registered with HCL Traveler from syncing by using the Deny Access action in the HCL Traveler administration database.
    - Restricting access using server document access fields
      An administrator can define which users are allowed to connect to the HCL Traveler server, or create explicit denial lists for users that should be denied access to the server. In a Traveler HA environment, repeat the procedure on each server in the pool.
    - Requiring approval for device access
      HCL Traveler gives administrators the ability to require approval before a user's device can sync data.
    - Restricting access by device category
      An administrator can restrict access to devices that do not support device security using HCL Traveler or devices by their device type or user agent values.
  - 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.
  - Mail address handling
  - 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
  - How HCL Traveler processes attachments
    There are several issues to be aware of in how HCL Traveler processes attachments.
  - How HCL Traveler processes SmartForward/SmartReply requests
    A SmartForward/SmartReply (SFSR) request is an email that is a forward or reply of a previously received email that does not include the body or attachments from the original email which is being forwarded or replied to. Instead, a SFSR contains just the forward/reply body text and any additional attachments, plus an identifier of the original email.

Restricting access using server document access fields

An administrator can define which users are allowed to connect to the HCL Traveler server, or create explicit denial lists for users that should be denied access to the server. In a Traveler HA environment, repeat the procedure on each server in the pool.

About this task

The server access depends on the user's identity, so it requires NTS_USER_SESSION set to TRUE (default in HCL Traveler 11 and up). If NTS_USER_SESSION has been explicitly set to FALSE, the server's identity will be used.

Procedure

From the Domino® Administrator client, select the HCL Traveler server document.
Click Edit Server.
Click the HCL Traveler tab.

Populate either the Access Server or Not Access Server field with the names of users and groups.

Table 1. Server access fields
Field	Description
Access Server	Select the option Users listed in all trusted directories to allow access to HCL Traveler only to people that have person documents in either the primary directory of this server or any secondary directories that trusted credentials using Domino® directory assistance. You can also select individual names of users and groups to allow access to this HCL Traveler server. A blank entry means that all users can access HCL Traveler except any who are listed in the Not Access Server field.
Not Access Server	Select the names of users and groups that should be denied access to this HCL Traveler server. A blank entry means that no users are denied access. Note: Entering names in the Access Server field automatically denies access to those names not listed.

Click Save & Close.

What to do next

Note: Users defined as Domino® 'Full Access Administrators' have access to HCL Traveler regardless of how the Not Access Server or Access Server fields are configured.

Note: Users denied access to Domino® through the Domino® Not Access Server or Access Server fields under the Security tab of the server document cannot access HCL Traveler.