Home
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.
Clustering and failover
The key to any production environment is the enablement of redundancy to account for planned or unplanned outages.
Disaster recovery
There are several methodologies to employ with HCL Traveler to recover from a server crash or failure.

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.
  - Choosing a deployment configuration
    The HCL Traveler server can be deployed using several different configurations.
  - Planning HCL Traveler on Docker
    HCL Traveler on Docker is a full-function Domino on Docker server with Traveler preinstalled and configured to start whenever the Domino server starts. The Docker container runs Red Hat Linux, so Domino and Traveler are Linux also. As with any other Linux-based Domino, the HCL Domino Administrator Client must be run remotely on a Windows server connected to the the Docker image over the network.
  - Planning HCL Traveler on IBM® i
    There are several IBM® i operating system considerations to be aware of when planning the HCL Traveler server installation on IBM i.
  - Clustering and failover
    The key to any production environment is the enablement of redundancy to account for planned or unplanned outages.
    - High Availability (HA)
      HCL Traveler servers can be configured to use a shared enterprise database. This configuration is referred to as a High Availability (HA) pool.
    - Disaster recovery
      There are several methodologies to employ with HCL Traveler to recover from a server crash or failure.
    - Domino® mail clustering
      By default, The HCL Traveler service detects mail file replicas by reading the replica entries in the HCL Domino® cluster directory database (cldbdir.nsf) on the mail server of the user. This database must grant at least reader access to the HCL Traveler server or servers (in an HA pool). Otherwise, the HCL Traveler server never fails over the connection to an alternate server for mobile users if their primary Domino® mail server is down. If configured, the HCL Traveler service will look for an instance of the user's mail file on the Traveler server ahead of what is specified in the cluster directory.
  - Planning for device security
    This section provides information about each HCL Traveler security option and how they can be applied by device type. You can use this information to plan your security configuration for HCL Traveler on your devices.
  - Planning for user authentication
    HCL Traveler requires every HTTP request to be authenticated for the operations being done to be correctly associated with the proper user. Hence, anonymous access is not supported. This validation of identity, referred to as authentication, is typically handled by the HCL Domino HTTP task or a secure proxy such as HCL SafeLinx. This section provides information on the supported authentication types by client to help plan for the Traveler server's authentication configuration.
  - Planning for migration
    Migration covers a number of scenarios.
  - Language support
    This section lists and provides information on all supported languages for HCL Traveler.
  - Sync protocol support
    When data is synced between the server and device, it is done so utilizing a protocol which controls what the message content (the HTTP body) contains.
  - Capacity planning guidelines
    This section provides guidance on capacity planning for various deployment configurations of the HCL Traveler server. It also touches on best practices for monitoring capacity.
  - Estimating the space needed for the HCL Traveler database
    You can estimate how much space is needed for the HCL Traveler database before it is installed.
- 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.

Disaster recovery

There are several methodologies to employ with HCL Traveler to recover from a server crash or failure.

Deploying a HCL Traveler High Availability (HA) pool inherently provides recovery from a server crash or hardware failure. In the event of a failure, device requests and mail monitoring is shifted to the remaining servers in the pool. For more information, refer to High Availability (HA).

Alternatively, it is also possible to set up multiple standalone HCL Traveler servers as potential disaster recovery servers for each other. Each server could have the same access to all the mail files for a user on remote servers. If a HCL Traveler server is not responsive, the user can manually reconfigure the device client settings to point to another HCL Traveler server. Alternatively this failover could be automated using a front end proxy (for example, HCL Safelinx). After a device switches to a new server, the sync anchors no longer match between the server and device. The protocol initiates a sync refresh, where all of the data on the device is replaced by a fresh copy of the data from your mail database. Internally, the HCL Traveler server keeps track of each piece of data that is on a device. If a device switches to another server, then this history is lost due to the fact that these tracking databases are not on the network or shared between HCL Traveler servers. Likewise, switching back to the original server can also result in a sync refresh. This kind of configuration is useful in a disaster recovery scenario where High Availability is not required.