Home
Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
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.
HCL Traveler server settings
You can configure a variety of HCL Traveler server settings, including server document settings and notes.ini settings.
Push messaging through a proxy
HCL Traveler supports the sending of APNS and FCM messages through a proxy server.

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.
  - Configuring HCL Traveler on Docker
    This topic describes Traveler specific configuration items for Docker.
  - HCL Traveler server settings
    You can configure a variety of HCL Traveler server settings, including server document settings and notes.ini settings.
    - Server document settings
      You can change a variety of server document settings.
    - Notes.ini settings
      These notes.ini parameters can be used to change or override HCL Traveler default values. For most installations, changing these settings is unnecessary. They are provided here for your reference in cases where the default values are not compatible with an existing system.
    - Push messaging through a proxy
      HCL Traveler supports the sending of APNS and FCM messages through a proxy server.
  - HTTP
    All communication between HCL Traveler-supported clients and the Traveler server use the HTTP protocol. On the Domino server where HCL Traveler is deployed, this http-based communication is handled by the Domino Web server.
  - Setting the external server URL
    There are times when a device needs to connect to a link sent by the server. For example, downloading client files, web page URLs, and Apple encrypted mail retrieval. To make sure that the server sends an appropriate link that the device can use, you must first set the External Server URL field on the HCL Traveler tab in the Server document.
  - Configuring the server for Certificate Based Authentication with Android devices
    There are several reasons why companies may wish their users to authenticate using a client certificate. Admins can easily issue and revoke certificates using MDM solutions. There is no need for users to remember or provide credentials. And there is additional security with two factor authentication using the certificate.
  - Mobile client support for SAML authentication
    HCL Verse mobile clients now support federated-identity authentication using Security Assertion Markup Language (SAML). This allows mobile users to authenticate to a customer’s identity provider prior to accessing the HCL Traveler services.
  - Mobile client support for TOTP authentication
    HCL Domino 12.0.0 introduces support for requiring a Time-based One-Time Password (TOTP), which is in addition to their user names and passwords for http authentication. For more information, see Time-based One-Time Password (TOTP) authentication. The HCL Verse Mobile clients, starting with the 12.0.0 versions, support the Traveler server endpoint configured for TOTP authentication.
  - Configuring the HCL Traveler High Availability Pool
    Configuring HCL Traveler to use a High Availability Pool requires special configuration steps.
  - Configuring the HCL Traveler server for Microsoft Outlook
    For information on how to configure the Traveler server for Microsoft Outlook, see the steps in Configuring Traveler for use with Outlook in the HTMO documentation.
  - Setting auto sync options
    You can use auto sync options to maximize the battery life of mobile devices.
  - Tuning performance of the server
    This topic describes memory, thread, logging and other considerations for the performance of the HCL Traveler server.
  - Configuring ports for a partition
    HCL Traveler supports running on multiple Domino® partition servers on the same physical machine. The server must be configured to avoid port conflicts among the partition instances.
  - Converting Notes® document links to web links
    When a Rich Text document (for example, an email composed in the Notes client) is synced by HCL Traveler to a mobile device, its body is converted from Rich Text to HTML. If the document contains a link to an Application, View, or Document, the HTML reference created by the conversion process is a relative URL which is missing the protocol, hostname, and port number needed by the mobile device to access the linked object.
  - Customizing the device configuration process for Apple
    There is no additional client code that must be installed on an Apple device for it to connect to an HCL Traveler server. However, you must configure the Microsoft™ Exchange account on the device so that it can use Exchange ActiveSync to connect to the HCL Traveler server. Apple devices can be configured either manually or by using profiles. This topic also describes how to customize profiles (also known as .mobileconfig files) to work in your environment.
  - Customizing the generated email for encrypted or private mail
    To enforce security settings, some emails only sync to HCL clients. This includes Notes-encrypted mails and mails marked as private (prevent copy). For any third party client (for example, the iOS Mail app), Traveler syncs a placeholder email indicating that the mail can be viewed with another client.
  - Name lookup
    For HCL Traveler to function properly, it must be able to lookup user information. Depending on the type of lookup, a variety factors can change, including where the lookup is performed, what parameters are used on the lookup, and how long the results are cached.
  - Configuring corporate look up for devices
    The corporate look up feature of HCL Traveler allows mobile users to search for and find information about other users in the Domino® directory. It also allows them to find information using remote directories if directory assistance is configured. This is useful when a user must contact another person in the organization who is not in the user's local contact store.
  - Configuring and using out of office replies
    The out of office service can be managed from your Apple, Android, BlackBerry 10, or Windows™ Phone device.
  - HCL Traveler Companion security settings
    There are security settings available that control how Companion connects to the HCL Traveler server and how attachments in encrypted mails can be used on the mobile device.
- 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.

Push messaging through a proxy

HCL Traveler supports the sending of APNS and FCM messages through a proxy server.

Note: Support for Google's FCM (Firebase Cloud Messaging) HTTP v1 API has been added to provide push functionality to Android devices which have used GCM (Google Cloud Messaging) or older FCM APIs in the past. Google has deprecated GCM and older FCM APIs and replaced them with FCM HTTP v1 API. FCM messages are sent over HTTPS to https://fcm.googleapis.com/v1/projects/notes-traveler-2014/messages:send, so any firewalls or proxies will need to be updated to allow https://fcm.googleapis.com/v1/projects/notes-traveler-2014/messages:send. If you customized any GCM or FCM notes.ini's, consult Notes.ini settings as the GCM ini's are no longer supported and some of the FCM notes.ini's changed with the change to the FCM HTTP v1 API.

If you need to send APNS or FCM message through a proxy server in your environment, you need to configure the set of notes.ini settings that begin with NTS_PUSH and contain _PROXY for the messages you want routed through the proxy. The full list can be found in Notes.ini settings. Servers that do not have outgoing internet access allowed would be candidates for using a proxy so that the APNS or FCM messages can be sent through a proxy server that is allowed outgoing internet access.

For each message type, you would need to set the _SERVER and _PORT values. If the proxy requires authentication, then you would also need to set _PASSWORD and _USER to allow HCL Traveler to authenticate with the proxy. All settings can be configured using notes.ini, but _PASSWORD and _USER can also be configured using the offline utilities command. The _TYPE will vary per the set of notes.ini settings that you are configuring – see the notes.ini setting's description in Notes.ini settings.

Each Apple app has its own APNS configuration, its own certificate used for signing, and its own server to send the message to, so there are many combinations of those settings for APNS. The app versions that come from the Apple App Store would all be using the non-sandbox, production settings. As a result, those are the only ones that would need to be configured.

Note: It is not possible to bind the libraries to a particular network interface when there is more than one network interface.