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.