Home
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.
Choosing a deployment configuration
The HCL Traveler server can be deployed using several different configurations.
Planning your network topology
Where to place your HCL Traveler server in your network depends on the types of devices used and sync types. This section includes a list of possible scenarios and why one might be selected over another.
Direct connection
Use either the virtual private network or the reverse proxy solution to ensure the best overall security. However, it is also possible to use SSL from the mobile device to connect directly to the HCL Traveler server or HA pool of servers inside the DMZ.

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.
  - Choosing a deployment configuration
    The HCL Traveler server can be deployed using several different configurations.
    - Planning your server topology
      The HCL Traveler server can be deployed using several different configurations. Considerations should be given to capacity and availability needs of the HCL Traveler servers, location of mail servers, domain of mail servers and directory server compatibility.
    - Planning your network topology
      Where to place your HCL Traveler server in your network depends on the types of devices used and sync types. This section includes a list of possible scenarios and why one might be selected over another.
      - Using a reverse proxy, IP sprayer or load balancer
        The diagrams in this topic shows a network topology where a reverse proxy resides in your DMZ and provides authentication services for the mobile device clients.
      - Using a virtual private network
        The diagram in this topic shows a network topology that uses a Virtual Private Network (VPN) server as the secure access point to the company intranet from mobile devices.
      - Direct connection
        Use either the virtual private network or the reverse proxy solution to ensure the best overall security. However, it is also possible to use SSL from the mobile device to connect directly to the HCL Traveler server or HA pool of servers inside the DMZ.
    - Remote and local mail file considerations
      HCL Traveler user mail databases do not need to reside on the same Domino® server as the HCL Traveler service, unless the client that requiures a local mail file is being used (HTMO, for example). In a remote configuration, the HCL Traveler service looks up the HCL Traveler mail server name and file name of the user from the local names.nsf and remotely connects to that mail server when needed.
    - Domino® directory server version compatibility
      If you are installing HCL Traveler into a HCL Domino® domain that is running with a HCL Domino directory template older than the version shipped with your version of HCL Traveler, upgrade the design of the directory server template before installing the HCL Traveler server in the domain.
    - Supporting multiple HCL Domino® domains
      Typically, the HCL Traveler server deploys in the same Domino® domain as production mail servers. However, there are a number of reasons why you may want to separate your HCL Traveler server domain and your production mail server domains.
  - Planning HCL Traveler on IBM® i
    There are several IBM® i operating system considerations to be aware of when planning the HCL Traveler server installation on IBM i.
  - Clustering and failover
    The key to any production environment is the enablement of redundancy to account for planned or unplanned outages.
  - Planning for device security
    This section provides information about each HCL Traveler security option and how they can be applied by device type. You can use this information to plan your security configuration for HCL Traveler on your devices.
  - Planning for migration
    Migration covers a number of scenarios.
  - Language support
    This section lists and provides information on all supported language for HCL Traveler.
  - Sync protocol support
    When data is synced between the server and device, it is done so utilizing a protocol which controls what the message content (the HTTP body) contains.
  - Capacity planning guidelines
    This section provides guidance on capacity planning for various deployment configurations of the HCL Traveler server. It also touches on best practices for monitoring capacity.
  - Estimating the space needed for the HCL Traveler database
    You can estimate how much space is needed for the HCL Traveler database before it is installed.
- 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.
- 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.

Direct connection

Use either the virtual private network or the reverse proxy solution to ensure the best overall security. However, it is also possible to use SSL from the mobile device to connect directly to the HCL Traveler server or HA pool of servers inside the DMZ.

When using this configuration, take steps to ensure that the HCL Domino® server has been secured and does not contain unnecessary data. For example, it is not recommended to host user mail files on the HCL Domino® server in this configuration. Consider installing this HCL Domino® server in a Domino® domain different from your production mail domain. This configuration has the advantage that no personal records for users are present in the local names.nsf, and directory assistance will be configured to remotely access the actual directory inside the production domain. For more information, see Supporting multiple HCL Domino domains.

The first diagram shows a direct connection to a stand alone HCL Traveler server within this topology.

Direct connection

The second diagram shows a direct connection to an HA pool of HCL Traveler servers. In this case, the IP sprayer and the HCL Traveler servers are in the DMZ and the DB Server and Mail servers are in the trusted domain.

The HCL Traveler server sits inside your DMZ and should not contain any user mail files. You must open port 443 on the Internet-facing firewall to the HCL Traveler server for data syncing. Then, on the intranet firewall, you must open up Notes® RPC port 1352 to each HCL Domino® mail server that contains user mail files. For an HA pool, on the intranet firewall, open the JDBC port for the Data Base server that contains the HCL Traveler Data. The port will depend upon the database server used and the configuration (for example, port 50000 for the JDBC connection to a DB2® Server instance).

Direct connection

The third diagram shows the network topology with the authentication proxy also providing the ability to spray the mobile requests to the HA pool of HCL Traveler servers.

Direct connection HA sprayer

This configuration is shown using only HTTPS (SSL) connections between the device and the HCL Traveler server. While it is technically possible to connect the device to the server using HTTP (port 80), do not use this configuration.