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.
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.

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.
    - Deleting a user FAQ
      The following is a set of frequently asked questions about deleting a user from HCL Traveler.
  - 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.
  - Address conversion
    Not all devices support the full range of acceptable HCL Domino® mail addresses as well as they support internet addresses.
  - Address encoding for Microsoft Exchange ActiveSync devices
    Exchange ActiveSync devices, such as Windows Phone and Tablet, BlackBerry 10, and Apple iOs, cannot support the full range of acceptable Domino® mail addresses. To allow the device to properly handle non-standard internet address formats, HCL Traveler has a feature that encodes them into internet addresses supported by these devices.
  - 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.

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.

About this task

In Traveler 9.0.1.10 and later, it is no longer mandatory to manually perform tell traveler security delete to remove the device security administration data from Traveler after a device has been deleted or reset. Starting with version 9.0.1.10, Traveler automatically quarantines deleted devices and moves them into the deleted state. These deleted devices are not seen in the "Devices" view, however they will continue to be seen in the "Devices Security" view for up to 30 days. Administrators can customize the number of days that the deleted devices are stored in the security view by adding this parameter in the notes.ini: NTS_ADMIN_CLEANUP_TIMEOUT (default 30 days)

Traveler users inactive for longer than one month will be removed from the database automatically. To completely remove a user from HCL Traveler:

Procedure

Run the following command:
```
tell traveler security delete * <username>
```
Note: If the user has already been deleted from the Domino® Directory, then the full user name must be specified. For example:
```
tell traveler delete * CN=John Doe/OU=Raleigh/O=HCL
```
Run the following command:
```
tell traveler delete * <username>
```
Any Remote Wipe commands performed on users/devices must be cleared before the entries can be deleted.
The above two steps should completely remove the user, but you can verify with the following additional step:
Use the HCL Traveler administration application to verify that there are no records for the user. See Using the administration application for more information.

What to do next

For information about deleting a user from the Domino® server, see the topic "Deleting a User" in the Domino® Administrator documentation.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.