Traveler has minimal requirements for an IP sprayer:
- Provides a single URL entry point and supports the proxying of device requests to two or more Lotus Notes Traveler servers
- Round robin load balancing. This will spread the load evenly across the Domino® HTTP tasks as desired. Lotus Notes Traveler provides its own load balancing based on server load characteristics after it has received the requests from Domino HTTP. Note that pure round robin without session affinity is recommended. Because the Notes Traveler server is designed to perform dynamic routing of the incoming requests from the mobile device to the Notes Traveler server that currently owns the user's master monitor, session affinity does not provide any efficiency. And in some cases session affinity could cause an imbalance of HTTP requests coming into one or just a few servers in the Notes Traveler HA pool, instead if being spread out more evenly across the pool servers.
- Ability to detect when a Lotus Notes Traveler server is no longer responding (to allow for failover).
After configuring an IP Sprayer, you must update the Lotus Notes
Traveler external URL to point the devices to the URL of the sprayer. Refer to Setting the external server URL
for more information. The external URL setting must be updated on each Lotus Notes
Traveler server in the high availability pool.
The primary link for Lotus Notes
Traveler has been changed from /servlet/traveler
, so as to make it easier for users to enter the link into their mobile devices.
Parent topic: Configuring the Lotus Notes Traveler High Availability Pool