Home
Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
Configuring HCL Traveler server
The HCL Traveler configuration settings are part of the Domino® server document. The first time that the HCL Traveler server is started, it performs any necessary configurations. You might want to perform additional configurations beyond the basics. The following topics describe additional configuration options.
Tuning performance of the server
This topic describes memory, thread, logging and other considerations for the performance of the HCL Traveler server.
Server Document settings
The following settings are specified in the Server Document for the HCL Traveler server that are of interest. Some settings affect HCL Traveler and others do not. Some settings will vary if Internet Site Documents are enabled.

Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
- Planning for installation and configuration
  There are many installation and configuration considerations you should review before installing the HCL Traveler server.
- Installing the HCL Traveler server
  The following topics describe options for installing and uninstalling the server:
- Configuring HCL Traveler server
  The HCL Traveler configuration settings are part of the Domino® server document. The first time that the HCL Traveler server is started, it performs any necessary configurations. You might want to perform additional configurations beyond the basics. The following topics describe additional configuration options.
  - HCL Traveler server settings
    You can configure a variety of HCL Traveler server settings, including server document settings and notes.ini settings.
  - HTTP
    For increased security, HTTP traffic to and from the HCL Traveler server should be secured by enabling SSL or using a VPN. For SSL, at least the component that is terminating SSL connections from the clients should have SSL enabled. The SSL termination can be done at the proxy, load balancer, or IP sprayer layer (common when configuring high availability mode but also possible for single HCL Traveler server configurations) or Domino HTTP layer. Other layers beyond the SSL termination of clients' requests do not need to have SSL enabled too (HTTP is normally sufficient), but it is possible to have the other layers have SSL enabled for even greater security.
  - Setting the external server URL
    There are times when a device needs to connect to a link sent by the server. For example, downloading client files, web page URLs, and Apple encrypted mail retrieval. To make sure that the server sends an appropriate link that the device can use, you must first set the External Server URL field on the HCL Traveler tab in the Server document.
  - Configuring the server for Certificate Based Authentication with Android devices
    There are several reasons why companies may wish their users to authenticate using a client certificate. Admins can easily issue and revoke certificates using MDM solutions. There is no need for users to remember or provide credentials. And there is additional security with two factor authentication using the certificate.
  - Configuring the HCL Traveler High Availability Pool
    Configuring HCL Traveler to use a High Availability Pool requires special configuration steps.
  - Configuring Traveler for use with Outlook
    After installing the Traveler server, configure it for use with HCL Traveler for Microsoft™ Outlook (HTMO).
  - Setting auto sync options
    You can use auto sync options to maximize the battery life of mobile devices.
  - Tuning performance of the server
    This topic describes memory, thread, logging and other considerations for the performance of the HCL Traveler server.
    - Tuning the HTTP user cache
      All mobile devices connecting to an HCL Traveler server connect through the HCL Domino HTTP server component. It is important to tune this component for mobile traffic, as data traffic from mobile devices while syncing is much different than normal web site data traffic.
    - Tuning active HTTP threads for HCL Traveler
      HCL Traveler devices utilize Domino® web server HTTP threads when communicating with the server.
    - Server Document settings
      The following settings are specified in the Server Document for the HCL Traveler server that are of interest. Some settings affect HCL Traveler and others do not. Some settings will vary if Internet Site Documents are enabled.
  - Configuring ports for a partition
    HCL Traveler supports running on multiple Domino® partition servers on the same physical machine. The server must be configured to avoid port conflicts among the partition instances.
  - Converting Notes® document links to web links
    Notes® links that are contained in mail messages and viewed on HCL Traveler clients will now include an additional URL hotspot which points to the web address of the application server. It may be possible to open the linked application using a browser on the mobile device, similar to how applications can be opened using an iNotes® application.
  - Customizing the device configuration process for Apple
    There is no additional client code that must be installed on an Apple device for it to connect to an HCL Traveler server. However, you must configure the Microsoft™ Exchange account on the device so that it can use Exchange ActiveSync to connect to the HCL Traveler server. Apple devices can be configured either manually or by using profiles. This topic also describes how to customize profiles (also known as .mobileconfig files) to work in your environment.
  - Name lookup
    For HCL Traveler to function properly, it must be able to lookup user information. Depending on the type of lookup, a variety factors can change, including where the lookup is performed, what parameters are used on the lookup, and how long the results are cached.
  - Configuring corporate look up for devices
    The corporate look up feature of HCL Traveler allows mobile users to search for and find information about other users in the Domino® directory. It also allows them to find information using remote directories if directory assistance is configured. This is useful when a user must contact another person in the organization who is not in the user's local contact store.
  - Configuring and using out of office replies
    The out of office service can be managed from your Apple, Android, BlackBerry 10, or Windows™ Phone device.
  - HCL Traveler Companion security settings
    There are security settings available that control how Companion connects to the HCL Traveler server and how attachments in encrypted mails can be used on the mobile device.
- Administering HCL Traveler
  The HCL Traveler server component functions as a Domino® server add-in task and responds to Domino server console commands. Topics in this section describe common administrative tasks for administering a HCL Traveler server.

Server Document settings

The following settings are specified in the Server Document for the HCL Traveler server that are of interest. Some settings affect HCL Traveler and others do not. Some settings will vary if Internet Site Documents are enabled.

Table 1. Server Document - Basics
Setting	Field name	Description
Load Internet configurations from Server\Internet Sites documents	LdISite	0 Disabled, 1 Enabled

Table 2. Server Document - Internet Protocols - HTTP - Basics
Setting	Field name	Description
Host name(s)	HTTP_HostName	Host Name
Number active threads	HTTP_MaxActiveThreads	Number of HTTP threads to process HTTP requests thereby limiting how many devices can be connected simultaneously.

Table 3. Server Document - Internet Protocols - HTTP - Timeouts
Setting	Field name	Description
HTTP persistent connections	HTTP_11Connections	0 Disabled, 1 Enabled
Maximum requests per persistent connection	HTTP_Max11Requests	Maximum requests per persistent
Persistent connection timeout	HTTP_PersistentTimeout	Persistent connection timeout (seconds)
Request timeout	HTTP_RequestTimeout	Request timeout (seconds)
Input timeout	HTTP_RNInputTimeout	Input timeout (seconds)
Output timeout	HTTP_RNOutputTimeout	Output timeout (seconds)
CGI timeout	HTTP_RNCGITimeout	CGI timeout (seconds) - not applicable

Table 4. Server Document - Internet Protocols - HTTP - R5 Timeouts
Setting	Field name	Description
Input timeout	HTTP_InputTimeout	Input timeout (minutes) - not applicable
Output timeout	HTTP_OutputTimeout	Output timeout (minutes) - not applicable
CGI timeout	HTTP_ScriptTimeout	CGI timeout (minutes) - not applicable
Idle timeout	HTTP_IdleThreadTimeout	Idle thread timeout (minutes) - not applicable

Table 5. Server Document - Internet Protocols - HTTP - Protocol Limits
Setting	Field name	Description
Maximum URL length	HTTP_MaxURLBytes	Kilobytes
Maximum number of URL path segments	HTTP_MaxURLPathSegment	Number
Maximum number of request headers	HTTP_MaxHeaderLines	Number
Maximum size of request headers	HTTP_MaxHeaderBytes	Kilobytes
Maximum size of request content	HTTP_MaxContentLength	This limit (in kilobytes) is normally only reached when trying to send mail from the device with large attachments which might put the request over this limit. Because attachments must be encoded for HTTP transport, mail messages may be as much as 1/3 larger than their original size. You can raise this setting to address this issue, but take into account the HTTP JVM heap memory, the number of concurrent requests, and the size of those requests, which will all vary greatly over time. In general, it is recommended that you not increase the file attachment size to more than 20MB.

Table 6. Server Document - Internet Protocols - Domino Web Engine - HTTP Sessions
Setting	Field name	Description
Session authentication	HTTP_EnableSessionAuth	0 Disabled, 1 Single, 2 Multiple
Maximum active sessions	HTTP_MaxActiveSessions	Number

Table 7. Server Document - Internet Protocols - Domino Web Engine - Memory Caches
Setting	Field name	Description
Maximum cached users	HTTP_MaxCachedUsers	Number. Generally, this should be over 1024 to handle the HCL Traveler load.
Cached user expiration interval	HTTP_ExpireCachedUsers	Seconds. Generally, this should be above 3600 to avoid expiring entries too quickly.

Table 8. Server Document - Internet Protocols - Domino Web Engine - Java Servlets
Setting	Field name	Description
Maximum active sessions	HTTP_MaxActiveJSessions	Number

Table 9. Server Document - Internet Protocols - Domino Web Engine - POST Data
Setting	Field name	Description
Maximum POST data (in kilobytes)	HTTP_maxPostDataLength	This limit (in kilobytes) is normally only reached when trying to send mail from the device with large attachments which might put the request over this limit. Because attachments must be encoded for HTTP transport, mail messages may be as much as 1/3 larger than their original size. You can raise this setting to address this issue, but take into account the HTTP JVM heap memory, the number of concurrent requests, and the size of those requests, which will all vary greatly over time. In general, it is recommended that you not increase the file attachment size to more than 20MB.

Table 10. Server Document - Internet Protocols - Domino Web Engine - Domino Access Services
Setting	Field name	Description
Enabled Services	HTTP_EnabledServices	Requires TravelerAdmin, PUT, and DELETE for the xPages admin to work properly.

Table 11. Web Site - Configuration - Allowed Methods
Setting	Field name	Description
Methods	WSHTTPMthds	1 GET, 2 HEAD, 3 POST, 4 OPTIONS, 5 TRACE, 6 PUT, 7 DELETE, 8 PATCH. GET and POST are always required. If Exchange ActiveSync is needed, then OPTIONS is also required. If using xPages admin, you also need PUT and DELETE.

Table 12. Web Site - Configuration - Domino Access Services
Setting	Field name	Description
Enabled Services	WSEnabledServices	Needs to include TravelerAdmin for the xPages admin to work properly.