Home
Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
Installing the HCL Traveler server
The following topics describe options for installing and uninstalling the server:
Installing HCL Traveler for High Availability
Every server that is to be deployed as part of a HCL Traveler High Availability pool is first deployed the same way you install a stand-alone 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:
  - Before you install
    There are HCL Domino®, UNIX operating system, and Highly Available (HA) considerations to be aware of when planning the HCL Traveler server installation.
  - Installing HCL Traveler on Docker
    Begin here to install Traveler on Docker.
  - Installing the server on Windows™ operating systems
    Begin here to install the server on Windows™.
  - Installing the server on Linux® or AIX® operating systems
    Begin here to install the server on Linux® or AIX®.
  - Installing HCL Traveler on IBM® i
    Several steps are required to install HCL Traveler server on IBM® i operating systems.
  - Installing using a customized JVM on Windows™ operating systems
    You might want to use a customized Java™ virtual machine (JVM) during the installation. For example, if your custom JVM has been enabled to work with a screen reader, such as JAWS for Windows™. Make sure that you use Java 1.8 or later.
  - Installing using a customized JVM on Linux™ or AIX operating systems
    You might want to use a customized Java™ virtual machine (JVM) during the installation. For example, if your custom JVM has been enabled to work with a screen reader, such as JAWS for Linux™. Make sure that you use Java 1.8 or later.
  - Installing in silent mode on Windows™ operating systems
    Follow these steps to perform an automated installation of the HCL Traveler server.
  - Installing in silent mode on Linux™ or AIX operating systems
    Follow these steps to perform an automated installation of the HCL Traveler server.
  - Installing multiple instances of HCL Traveler on Linux® or AIX®
    You can install multiple instances of the HCL Traveler server on Linux® or AIX® operating systems.
  - Installing HCL Traveler for High Availability
    Every server that is to be deployed as part of a HCL Traveler High Availability pool is first deployed the same way you install a stand-alone server.
  - Uninstalling HCL Traveler on Windows and Linux or AIX
    To uninstall HCL Traveler from an HCL Domino® server on Windows or Linux or AIX, use the HCL Traveler uninstallation program.
  - Uninstalling HCL Traveler on IBM® i
    You can remove HCL Traveler files from a Domino® server without deleting the HCL Traveler software from your system.
- 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.

Installing HCL Traveler for High Availability

Every server that is to be deployed as part of a HCL Traveler High Availability pool is first deployed the same way you install a stand-alone server.

For more information on installing HCL Traveler on a stand-alone server, refer to Installing the HCL Traveler server.

A HCL Traveler server becomes part of a High Availability pool as a post-installation, configuration step. For more information, see Configuring the HCL Traveler High Availability Pool. The installation considerations for a server that is to be part of an HA pool are as follows:

Each Domino® Server running HCL Traveler should be registered for the same Domino domain.
Each Domino® Server running HCL Traveler should be co-located to reduce latency for inter-server communication.
The external URL setting for HCL Traveler must be the same for each HCL Traveler server in the pool, and can be setup after installation.
All Domino servers in the HA pool hosting the HCL Traveler server component are recommended to be at the same version and fix level.
All HCL Traveler servers in the HA pool must the running the same version and fix level. The only exception is when upgrading the HCL Traveler server code in the HA pool, where for a short period of time the HCL Traveler servers will be at different versions during the pool upgrade.

Refer to High Availability (HA) for information on topology for the HCL Traveler High Availability pool.

Note: Be sure to check specific version and operating system requirements. This article details a full list of system requirements.