After the Lotus Notes Traveler server is installed, follow the steps below to configure the Notes Traveler and verify the installation:
- Opening the the Server document using the Domino Administrator client.
- On the Basics tab, ensure the "Server name" and "Fully qualified Internet host name" are set correctly.
- On the Internet Protocols, HTTP tab, review the value of "Number of active threads". By default, this value is set to 400 on a 64-bit server and this value can be a good starting point. However, review this value regularly and update the value as necessary. If the number of active threads is too low, HTTP 503 (Service not available) errors are generated. If the value is too high, an excess amount of memory is used. For information about how to set this value, see 8.4.5 Internet protocols tab. A good rule of thumb for the proper settings of the "Number of active threads" is 1.2 * the number of devices serviced by the system, or are planned to be serviced by the system.
- Go to the Internet Protocols, Domino Web Engine tab.
Review the Memory Caches section.
The Maximum cached users field is used to store a users name, password, and a list of groups that the user belongs to. A user is added to this cache after they successfully authenticate with the Lotus Notes Traveler server. The default setting for this field is 64. If the number of current authenticated users logged in exceeds this value, some performance improvements may be gained by increasing the number of the Maximum cached users. To review the current values, look at the statistics from a recent NSD file. As a general guideline, when adjusting any of the "Domino.Cache.*.Count" statistics, they should be slightly less than their "Domino.Cache.*.MaxSize" counterpart. In this case, the "Domino.Cache.User Cache.Count" should be slightly less than the "Domino.Cache.User Cache.MaxSize". If the value listed in the Domino.Cache.User Cache.Count is larger than the Domino.Cache.User Cache.MaxSize, then try slowly incrementing the maximum value for the "Maximum cached users", as shown in the Memory Cache section screen capture above, until the Count no longer reaches the Maximum.
- Go to the Transactional Logging tab.
Disable Transactional Logging. The Lotus Notes Traveler server is not a typical server, as there is very little writing to Domino databases. With the small number of writes necessary, it is not necessary to enable Transactional Logging.
- Go to the Lotus Traveler tab.
Review the Basics
- Maximum Memory Size
This is the amount of Java Memory allocated. By default on a 64-bit Domino server, this is set to 1024 MB (1GB). The Lotus Notes Traveler process is written in Java, so Java memory must be allocated. The Java memory required also depends on the number of the devices connected to the Notes Traveler server. Evaluate the system load and adjust the memory size as necessary. See 9.1 Performance tuning
about the tips to increase this value as necessary.
- IPC Socket Ports
These are the TCP ports that are used for the communications between the Lotus Notes Traveler HTTP servlet and the Lotus Notes Traveler server task and also the communications among the Lotus Notes Traveler servers. These communications are only on the local system so no external firewalls ever see this traffic. Rarely, if ever, will this need to be changed.
- External Server URL
This value should be set to the DNS name or IP address that is used to route traffic to the Lotus Notes Traveler server from the internet or the intranet. This URL ensures that the server sends a link that the devices can use and should not change. Include the following in the URL:
Scheme, HTTP or HTTPS
Server host name
Port number (if not a default port)
Path, such as /traveler
If the server allows both HTTP and HTTPS, and HTTP is redirected to HTTPS, then the External URL should be the HTTPS version and not the HTTP version.
In an HA pool, all servers must be configured with the same value for this parameter. The servers are part of a service pool that is accessed through the same front end sprayer, and must be configured with the external URL that will send traffic through that sprayer.
Administrator tip: It may be simpler to create and use a Configuration document for all the Traveler servers to ensure that the NTS_EXTERNAL_URL parameter is pushed down to the notes.ini file on each server.
In the Lotus Traveler Access
section, the Administrators can select whom to allow access to the server and what controls the users may have.
When in edit mode the section looks like this:
- Access server
If this field is left to the default value of blank, all users are able to access the server, unless they are excluded in the "Not access sever" field. Optionally, the administrator can enter individual names of users, servers, and groups to allow access to the Lotus Notes Traveler server. Separate multiple names with commas or semicolons. To specify all members of a branch of a hierarchical name tree, enter an asterisk followed by a forward slash and certifier name, for example, */Sales/Acme. Only users with Person documents in either the primary directory of this server or any secondary directories that are trusted for credentials using Domino directory assistance can be added. These values must be consistent on all Lotus Notes Traveler servers in the pool.
- Remote user commands
Enabling this field allows users to issue commands from the Lotus Notes Traveler servlet, such as displaying all the information about their mobile device. For example, the users can open the web page http(s):/travelerservername.com/traveler
and the following will be displayed on the web page. The user can select their device and perform any of the displayed commands.
- User managed security
If this field is enabled, users can issue a remote wipe command if their device is lost or stolen. For example, the users will be able to open the web page http(s)://travelerservername.com/traveler and the following will be displayed on the web page. The user will be able to select their device and perform any of the displayed commands.
Review the Log Settings
You can set the logging levels here. Do not change the default values unless debugging is enabled on the server.
Any changes done here for debugging purposes requires a restart of the Traveler process to enable the changes. An alternative is to change the logging levels using the server console commands, which will go into effect immediately without a restart. See 8.1 Server console commands
for a full listing of the console commands on changing logging levels.
Review the Auto Sync Settings
The last section of the Lotus Traveler tab is Auto Sync settings. These should rarely need to be changed, if ever. So this will be for informational purposes only.
- Polling interval
This set how often the Lotus Notes Traveler server polls the Mail server for any changes, such as a new email, change in contacts, etc. If changes are found, a prime sync is created and the mobile device is notified changes have been found.
- Port for TCP Connections
This is the TCP Port used by the push engine for communications.
Normally, it is not necessary to modify the heart beat interval. The heartbeat interval for each connected client is automatically adjusted by Lotus Notes Traveler to be optimal. However, the configuration parameters can be tweaked to slightly improve operation. By default, the Heartbeat Algorithm Maximum Interval is set to 15 minutes in the Lotus Notes Traveler server configuration document.
If you have devices earlier than Lotus Notes Traveler 8.5.2 that use TCP push, leave the maximum at 15 minutes. But, if you are running all devices on Lotus Notes Traveler 8.5.2 or later using HTTP push, there are advantages to increasing the maximum setting to 30, 45, or 60 minutes. If you do modify the heartbeat algorithm maximum interval, set it to a number slightly less than the timeout of the underlying network connection for all users, if known. For example, if all Lotus Notes Traveler clients are connecting over a VPN that has an idle timeout of 30 minutes, then set the maximum heartbeat interval to 28 or 29 minutes.
Apple devices use a different heartbeat algorithm (the ActiveSync algorithm). The ActiveSync algorithm uses the Lotus Notes Traveler minimum and maximum intervals, so these apply to all devices. The other Lotus Notes Traveler heartbeat algorithm settings apply only to other devices.
- Device Offline Timeout
The Lotus Notes Traveler server will continue to poll the Mail server every 3 seconds (see Polling Interval above) until the device is considered to be offline. The administrator can set the amount of timeout period here.
- User Cleanup Timeout
This is the number of days a device must be offline before the Lotus Notes Traveler server will cleanup information in the Lotus Notes Traveler derby database. Note that this does not remove the entry from the lotustraveler.nsf database, only from the Lotus Notes Traveler derby database.