Server document settings

You can change a variety of server document settings.

To display the HCL Traveler server document, open the HCL Domino® Administrator client, click Configuration tab > Server > Current Server Document > Notes 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 HCL Traveler server.

Table 1. Basics settings
Setting	Default value	Description
Maximum Memory Size	Calculated	This is the maximum amount of Java™ memory that is allocated to the HCL Traveler server task. It is calculated automatically and not read from the server document: For 32-bit systems, the value is configured for 512MB. For 64-bit systems, the value will be a minimum of 1024MB or 25% of the physical memory, whichever value is greater.
External URL	Blank	The complete URL used by devices to connect to the server to perform all HCL 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 HCL 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 `/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 HCL 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 HCL 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.
IPC Socket Ports	50125 50126	TCP ports that are used for communications between the HCL Traveler HTTP servlet and the HCL Traveler server task. This communication is only on the local system so no external firewalls should ever see this traffic.

Table 2. HCL Traveler access settings
Setting	Default value	Description
Access server	Blank	Controls access to the HCL 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 HCL Traveler server. The default blank value means that all certified users and servers can access the HCL 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 HCL 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 HCL Traveler users to issue remote user commands from the HCL 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 HCL Traveler server and the user mail database.
Port for TCP Connections	8642	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.
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 HCL Traveler server by activating the device or starting the HCL 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 HCL Traveler database. The user can still connect by activating the HCL Traveler client, but the client must register again with HCL Traveler server. The data must also sync as if it is from a new user.

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

Note: If your Traveler deployment currently uses the legacy client-side notes.ini setting OutlookEnv=1 to override Traveler settings in the Server document, change the setting to OutlookEnv=0. This change ensures that Traveler settings are displayed. OutlookEnv=1 should no longer be used. For more information on removing this setting, see Configuring server settings in the HTMO documentation. If you previously configured Traveler for HTMO monitoring with the instructions from the HCL Traveler 11.0 documentation on Monitoring HCL Traveler for Microsoft Outlook users, you should revert the change by following the 11.0 instructions in Step 3 for setting the client-side notes.ini variable to OutlookEnv=0 and re-editing the server config document. This restores the Traveler Settingstab in the server doc.