Server document settings

You can change a variety of server document settings.

To display the IBM Traveler server document, open the IBM® Domino® Administrator client, click Configuration tab > Server > Current Server Document > IBM Traveler. For additional more information, refer to Server Document settings.

Note: All changes to the server document settings, except log settings, require a restart of the IBM Traveler server.

Table 1. Basics settings
Setting	Default value	Description
Maximum Memory Size	512 MB	This is the maximum amount of Java™ memory that is allocated to the IBM Traveler server task.
External URL	Blank	The complete URL used by devices to connect to the server to perform all IBM Traveler transactions and data synchronization. This URL ensures that the server sends a link that the devices can use and should be a URL that IBM Traveler users can always access, whether on an internal network or the internet, and should not change. The URL should include the scheme (HTTP or HTTPS), the server host name, the port number (if not a default port) and the path, such as `/servlet/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. If there is a reverse proxy in use, the URL should be set using this reverse proxy name. If there is a DNS name or IP that is used to route external traffic to the IBM Traveler server from the internet, the URL should be set using this DNS name or IP address. 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. There are two ways this can be accomplished: The administrator can configure the value to be the same in the IBM® Traveler tab in the server document of each server in the pool. The administrator can use the common configuration. See Setup for common configuration (optional) to ensure that the NTS_EXTERNAL_URL parameter is pushed down to the notes.ini file on each server. Note: If you are using MobileIron and setting up IBM Traveler ToDo and IBM Traveler Companion, see this article for considerations on how to set the External URL setting.
IPC Socket Ports	50125 50126	TCP ports that are used for communications between the IBM Traveler HTTP servlet and the IBM Traveler server task. This communication is only on the local system so no external firewalls ever see this traffic.

Table 2. IBM® Traveler access settings
Setting	Default value	Description
Access server	Blank	Controls access to the IBM Traveler server for 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. You can also select individual names of users, servers, and groups to allow access to the IBM Traveler server. The default blank value means that all certified users and servers can access the IBM Traveler server except any listed in the Not access server field. 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.
Not access server	Blank	Select names of users, servers, or groups who should not have access to the IBM Traveler server. The default blank value means that no users are denied access. You can also use the Access server field to deny access; entering names in the Access server field automatically denies access to those not listed in the field. 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`.
Remote user commands	Disabled	Allows IBM Traveler users to issue remote user commands from the IBM Traveler user home page.
User managed security	Enabled	This controls whether the user has access to user managed security commands.

Table 3. Auto Sync settings
Setting	Default value	Description
Monitor polling interval	3 seconds	How frequently a user mail database is checked for changes when it is actively being monitored for Auto Sync. This check is made between the IBM Traveler server and the user mail database.
Port for TCP Connections	8642	This TCP port is used for Auto Sync communications between version 8.5.1 and earlier IBM Traveler servers and clients. If you are using an 8.5.2 version or later client, this port is not used and can be disabled. If you are using a version earlier than 8.5.2, this port must not be used by other applications on this server. If the IBM Traveler server is behind a firewall, this port must be open on the firewall or the IBM Traveler client must use a VPN to tunnel through the external firewalls. To disable the Auto Sync TCP port, set the port value to 0. If this server is configured for High Availability, the Auto Sync TCP port should be disabled as this is not a supported option in this mode.
Heartbeat algorithm	Indefinite Detection	The algorithm to use when sending the connection keep alive message. The keep alive message is sent only if there is no other Auto Sync activity. Indefinite Detection is the only supported option. Do not change this value.
Heartbeat initial interval	30 seconds	The initial interval to use for keepalive polling. This value should not be shorter than any network timeout values and not shorter than the minimum interval specified in the next setting.
Heartbeat algorithm minimum interval	30 seconds	The minimum interval allowed for keepalive polling. The heartbeat algorithm is not allowed to calculate a value smaller than this value.
Heartbeat Algorithm Maximum Interval	15 minutes	The maximum interval allowed for keepalive polling. The heartbeat algorithm is not allowed to calculate a value greater than this value. If you are using a Windows™ Mobile or Nokia client version 8.5.2 or later, you might want to increase the maximum, but keep it still less than your network/VPN timeout.
Heartbeat Retry Interval	30 minutes	How long to use the optimal keepalive interval before calculating a new optimal value.
Device Offline Timeout	24 hours	If a user is inactive for a time greater than this value, the user mail database is no longer actively monitored. The user can still access the IBM Traveler server by activating the device or starting the IBM Traveler client. As soon as the device is detected by the server after this timeout, the server resumes active monitoring of the mail database.
User Cleanup Timeout	30 days	If a user is inactive for a time greater than this value, the user is purged from the IBM Traveler database. The user can still connect by activating the IBM Traveler client, but the client must register again with IBM Traveler server. The data must also sync as if it is from a new user.

Note: Log setting are now managed by IBM Traveler tell commands to make them consistent across all servers in a IBM Traveler pool. See Console commands for more information on changing log settings