Installing IBM Traveler for High Availability
Every server that is to be deployed as part of a IBM Traveler High Availability pool is first deployed the same way you install a stand-alone server.
For more information on installing IBM Traveler on a stand-alone server, refer to Installing the IBM Traveler server.
A IBM Traveler server becomes part of a High Availability pool as a post-installation,
configuration step. For more information, see Configuring the IBM 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 IBM Traveler should be registered for the same domain
- Each Domino® Server running IBM Traveler should be co-located to reduce latency for inter-server communication
- The external URL setting for IBM Traveler must be the same for each IBM Traveler in the pool, and can be setup after installation
- All Domino servers in the HA pool hosting the IBM Traveler server component must be the same version and fix level
- All IBM Traveler servers in the HA pool must the running the same version and fix level. The only exception is when upgrading the IBM Traveler server code in the HA pool, where for a short period of time the IBM Traveler servers will be at different versions during the pool upgrade.
Refer to High Availability (HA) for information on topology for the IBM Traveler High Availability pool.