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.
Choosing a deployment configuration
The HCL Traveler server can be deployed using several different configurations.
Remote and local mail file considerations
HCL Traveler user mail databases do not need to reside on the same Domino® server as the HCL Traveler service, unless the client that requires a local mail file is being used (HTMO, for example). In a remote configuration, the HCL Traveler service looks up the HCL Traveler mail server name and file name of the user from the local names.nsf and remotely connects to that mail server when needed.

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 your server topology
      The HCL Traveler server can be deployed using several different configurations. Considerations should be given to capacity and availability needs of the HCL Traveler servers, location of mail servers, domain of mail servers and directory server compatibility.
    - Planning your network topology
      Where to place your HCL Traveler server in your network depends on the types of devices used and sync types. This section includes a list of possible scenarios and why one might be selected over another.
    - Remote and local mail file considerations
      HCL Traveler user mail databases do not need to reside on the same Domino® server as the HCL Traveler service, unless the client that requires a local mail file is being used (HTMO, for example). In a remote configuration, the HCL Traveler service looks up the HCL Traveler mail server name and file name of the user from the local names.nsf and remotely connects to that mail server when needed.
    - Domino® directory server version compatibility
      If you are installing HCL Traveler into a HCL Domino® domain that is running with a HCL Domino directory template older than the version shipped with your version of HCL Traveler, upgrade the design of the directory server template before installing the HCL Traveler server in the domain.
    - Supporting multiple HCL Domino® domains
      Typically, the HCL Traveler server deploys in the same Domino® domain as production mail servers. However, there are a number of reasons why you may want to separate your HCL Traveler server domain and your production mail server domains.
  - 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.
  - 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 migration
    Migration covers a number of scenarios.
  - Language support
    This section lists and provides information on all supported language 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.

Remote and local mail file considerations

HCL Traveler user mail databases do not need to reside on the same Domino® server as the HCL Traveler service, unless the client that requires a local mail file is being used (HTMO, for example). In a remote configuration, the HCL Traveler service looks up the HCL Traveler mail server name and file name of the user from the local names.nsf and remotely connects to that mail server when needed.

See the Traveler server notes.ini setting NTS_MAIL_SERVERS_ALGORITHM for more information on how Traveler builds the list of mail server(s)/files(s) for a user.

Remote mail databases

Make sure that the HCL Traveler server or each HCL Traveler server in an HA pool can physically connect to the remote mail servers. To verify this connection, from the Domino® server console on the HCL Traveler server, enter this command:

trace remote_server_name

This command shows connection routing information that shows you if there are any problems with the route between the HCL Traveler server and the specified remote server.

Local mail databases

It is possible to run the HCL Traveler service on the same Domino server that is hosting mail files. This is useful for small installations or when utilizing the HTMO clients that require a mail database to be local. In general, the HCL Traveler service runs on a machine separate from other applications, such as HCL Sametime®.

HTMO only supports like replicas on group servers where Traveler is installed. The replicas must have the same replication settings in order to function correctly for Microsoft™ Outlook.

If you use a Server List Group to hold your Traveler servers, the database path for each replica of the mail file is required to be the same for each server in the group server configuration. For the server configuration document associated with the group, any changes affect all servers, but setting the database administrator user name and password must be performed on each server using travelerUtil.

Remote mail database support

HCL Traveler server can connect to remote mail databases hosted by Domino® 7.0.2 servers or greater. The Domino® remote mail server can be any operating system supported by Domino®.

Mail file template support

HCL Traveler server supports standard and iNotes® mail file templates, version 6.5 and greater.