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

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

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.

HCL Traveler uses a relational database to store configuration settings as well as meta-data for sync engine operation. By default, HCL Traveler uses a Derby database which is located in the <Domino Data>\traveler\ntsdb directory. If HCL Traveler has been configured to use an enterprise database, then the Derby database in the directory previously listed is not used.

To estimate how much space is needed for the HCL Traveler database, use the following heuristic equation:

U * (D * (700 * V + 4000)) = Recommended DB space available in bytes

where

U = number of users 
D = number of documents per user (a document is a mail message, a contact, a calendar entry, etc...)
V = number of devices per user

This equation applies when estimating the space needed for a local Derby database or for an enterprise database used for HCL Traveler. The equation also intentionally overestimates the size to ensure adequate space for the HCL Traveler database.

Some examples:

An HCL Traveler server database servicing 1,000 users with 5,000 documents per user and 1.5 devices per user should allow for 25GB of database space.
An HCL Traveler server database servicing 3,000 users with 10,000 documents per user and 1.25 devices per user should allow for 146GB of database space.