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.
Configuring the HCL Traveler High Availability Pool
Configuring HCL Traveler to use a High Availability Pool requires special configuration steps.
Deploy an IP sprayer or load balancer
To support a pool of HCL Traveler Servers, you will need to provide a single URL entry point for the devices. This can be accomplished by employing an IP sprayer or load balancer, allowing a device to connect to one URL and have the request routed to any of the HCL Traveler servers in the pool.

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.
    - Understanding the HCL Traveler schema
      Since the HCL Traveler server comes with two options for configuring the enterprise database, it is necessary to understand the basic differences in schema creation for each of the two options. This will help you choose the correct schema configuration for your environment, as well as how to customize it.
    - Database permissions
      For the enterprise database that HCL Traveler supports (DB2, MySQL, or SQL Server ), it is necessary to grant the appropriate level of permissions for running the HCL Traveler server with either automatic schema migration or DDL schema.
    - Schema migration requirements
      There are some ground rules you should consider during migration.
    - Frequently asked questions about the enterprise database
      There are several common questions concerning the deployment and configuration of the enterprise database.
    - Deploying and configuring the enterprise database
      This section contains instructions for deploying and configuring DB2, SQL, and MySQL enterprise databases for HCL Traveler.
    - Configuring HCL Traveler for enterprise database
      You can configure the HCL Traveler server to use the database created in the previous steps. Use this section when creating a High Availability (HA) pool or adding a server to an existing HA pool.
    - Configuring the HCL Traveler High Availability pool on IBM® i
      This section describes how to configure the HCL Traveler server to use IBM® i DB2®. Use this section when creating a High Availability (HA) pool or adding a server to an existing HA pool.
    - Updating the enterprise database
      When upgrading the HCL Traveler servers in the HA Pool, it is necessary to upgrade the database schema level of the database used by the HA pool.
    - Deploy an IP sprayer or load balancer
      To support a pool of HCL Traveler Servers, you will need to provide a single URL entry point for the devices. This can be accomplished by employing an IP sprayer or load balancer, allowing a device to connect to one URL and have the request routed to any of the HCL Traveler servers in the pool.
    - Setup for common configuration (optional)
      In a HCL Traveler pool, it is critical that each server is configured identically.
    - Enable server to server secure communications (optional)
      By default, HCL Traveler uses regular TCP sockets for communication between the HCL Traveler server and the HTTP server, as well as for communications between the HCL Traveler servers within an HA pool.
    - Removing a server from a High Availability pool
      A HCL Traveler High Availability (HA) pool is a group of servers that are all configured to use the same enterprise database.
  - 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.
  - 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.

Deploy an IP sprayer or load balancer

To support a pool of HCL Traveler Servers, you will need to provide a single URL entry point for the devices. This can be accomplished by employing an IP sprayer or load balancer, allowing a device to connect to one URL and have the request routed to any of the HCL Traveler servers in the pool.

HCL Traveler has minimal requirements for an IP sprayer:

Provides a single URL entry point and supports the proxying of device requests to two or more HCL Traveler servers
Round robin load balancing. This will spread the load evenly across the Domino® HTTP tasks as desired. HCL Traveler provides its own load balancing based on server load characteristics after it has received the requests from Domino® HTTP .
Ability to detect when a HCL Traveler server is no longer responding (to allow for failover).

After configuring an IP Sprayer, you must update the HCL Traveler external URL to point the devices to the URL of the sprayer. Refer to Setting the external server URL for more information. The external URL setting must be updated on each HCL Traveler server in the high availability pool.

Note: The primary link for HCL Traveler has been changed from /servlet/traveler to /traveler, so as to make it easier for users to enter the link into their mobile devices.