In this scenario, we deploy an IBM Lotus Notes Traveler server with the same mentality that a small business would use. This solution encapsulates introducing a Lotus Notes Traveler server into an existing Lotus Domino environment. The Lotus Notes Traveler Server uses internet through a DMZ (or firewall) and allows devices and browsers to connect directly to the Lotus Notes Traveler server through HTTP/HTTPS. Lotus Notes Traveler then is communicating with the mail servers via the internal network.
Although this is a common scenario it is preferred to use an authenticating proxy server in the DMZ and move the Notes Traveler server inside the firewall. For more information on using a proxy server in this configuration see 3.4.3 Additional configurations
This following figure depicts the topology of the scenario.
In this section we walk through both the the Linux and Windows installation procedures.
When making the considerations as to what type of server to deploy, we take into account the size of the user base that is going to be catering to, the necessity for the server to be available 100% of the time, and the cost of the hardware be required.
First, we choose to go with a stand-alone server to cater to the 25 devices that we will be servicing in this scenario. This being a small number and less than 2,000 devices, we knew that we do not need to have more than one server in the environment to service these devices.
Second, in this operation we understand that if the Lotus Notes Traveler server is to become unavailable for one reason or another, all of the employees could simply use their Lotus Notes Client or iNotes to retrieve email, and manage their calendars and contacts. This being said, we did not need to add additional servers for high availability.
Based on these two reasons, there is no need to have more than one server purchased to give us the mobile functionality.
See 2.2 Choosing a stand-alone or high availability configuration for Lotus Notes Traveler
for further information about the decision of choosing stand-alone versus high availability topology.