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.
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.
Type of mobile user
Not all mobile device users are created equal and it is important to understand your user base to plan accordingly.

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 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.
    - Physical vs. virtual hardware
      Most customers run at least some part of their Traveler environment on virtual hardware. Doing so is fully supported however to avoid pitfalls, use the following best practices.
    - Central processing units (CPUs)
      These days it doesn’t make sense to talk much about processing speed, as most CPUs are 2GHZ or better, which is more than sufficient for use with the Traveler product. Instead we discuss the number of CPUs allocated to the physical or virtual system.
    - Memory
      Similar to CPU, it’s no longer interesting to discuss memory speed as most memory is now capable of transfer rates of 2400MB per second or greater which is more than sufficient. Instead, it’s important to review the amount of available memory.
    - Disk configuration
      The number one recommendation for disk architecture to support an HCL Traveler deployment is to use solid state disks (SSDs) for the Traveler database volume. For a standalone environment, this is the volume used by the Traveler server. For HA environments, this is the volume used by the enterprise database server.
    - Enterprise database configuration
      A Traveler HA environment should be set up over a Traveler standalone environment. A Traveler HA environment offloads all the work to store, index, sort and retrieve relational data to an enterprise database management server (DBMS) like DB2 or MS SQL Server. This greatly improves the performance and availability of the Traveler environment.
    - Network and geography
      Network is a broad term that encompasses any component that the Traveler server uses to communicate to service mobile devices.
    - Co-locating Traveler with other Domino applications
      In general, running other Domino applications on the Traveler server isn't recommended, including mail, Sametime, SMTP, POP, and so forth. Maximum performance of the Traveler environment is best achieved on dedicated hardware whether it be virtual or physical. That said, there are some cases where you may want to investigate running Traveler along with other Domino services.
    - Number of mobile devices
      When talking capacity, we always talk about the number of devices that will be connected to a particular Traveler environment rather than the number of users.
    - Type of mobile user
      Not all mobile device users are created equal and it is important to understand your user base to plan accordingly.
    - Theoretical device capacity
      There is no hard and fast statement when it comes to device capacity. It takes work to estimate and understand your user base, plan and set up the appropriate environments, then monitor to see how you are doing.
    - Monitoring for capacity
      In general, the best metric to monitor for capacity is the Traveler server Availability Index (AI). The AI is a measure of the overall server 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.

Type of mobile user

Not all mobile device users are created equal and it is important to understand your user base to plan accordingly.

Which type of users do you have?

A light weight mobile device user has less than 500 documents being tracked, has one device, and a three-day mail filter.
An average mobile device user has around 1000 documents being tracked by the Traveler server, a 1-week mail filter on their devices and 1.2 devices per user.
A power user has around 5000 - 10000 documents being tracked by the Traveler server, likely has more than one device and may or may not be running with unlimited mail filters.
A super user has more than 50,000 documents in their mail file, more than one device and unlimited mail filters.

As you can see there is a big difference between these users in terms of performance and capacity. A single super user on your system can use up as much resources as 1000 lightweight users. This often surprises customers when learning their performance problems are the result of a few power or super users. It is important to understand the usage patterns for your mobile user base when planning for capacity.