HCL Traveler

The Cloud Extender® integrates with HCL Traveler and IBM SmartCloud® environments to provide complete visibility to all ActiveSync devices connected to the mail system.

With HCL Traveler and IBM SmartCloud integration, the Cloud Extender functions in the following ways.

  • Queries the mail server by using APIs to discover ActiveSync devices.
  • Uploads the device list to the IBM® MaaS360® Portal for reporting and management functions.
  • Supports all ActiveSync device actions such as approve, block, or remove a device from the mailbox. Wipes the IBM MaaS360 Portal initiated devices either through administrative action or automated rules.
  • Enables Auto-Quarantine (AQ) to prevent new devices from connecting to HCL Traveler servers or IBM SmartCloud environments. The quarantine process does not affect the connections since the existing ActiveSync devices are approved. Auto-Quarantine is supported on HCL Traveler 9+ and IBM SmartCloud.
  • Supports approval of Secure Mail connections, native connections from enrolled devices, and connections to the IBM Verse® email client.
Important: The Cloud Extender integration with HCL Traveler and IBM SmartCloud does not affect the flow of email traffic because the Cloud Extender is not an email proxy. The Cloud Extender instance does not sit between email and devices. This integration provides visibility only to your email environment where you can manage devices. If the Cloud Extender is unavailable, users can continue to send and receive email.

Supported versions of HCL Traveler

The Cloud Extender integrates with both the on-premises and cloud versions of HCL Traveler. The Cloud Extender supports the following versions of HCL Traveler:
  • On-Premises - Lotus Notes® 8.5.2+
  • Cloud - IBM SmartCloud

Requirements and scaling

The IBM MaaS360 Portal offers a Cloud Extender Scaling Tool at Setup > Services > Enterprise Email Integration. Enter the number of mailboxes and devices that you plan to enroll for MaaS360 and determine how many Cloud Extenders you might need to support integration with HCL Traveler.

Consider the following guidelines for scaling the HCL Traveler integration:
  • Gather times for device data does not exceed 60 minutes and averages 25 - 40 minutes for 5,000 devices. Current and average gather times are available on the Cloud Extender Status page in the IBM MaaS360 Portal.
  • To determine the number of Cloud Extender instances for your environment, divide the potential number of ActiveSync connected devices by 5000, and the Mailboxes by 10000, and use the higher of the two values.
  • To minimize latency, regional Cloud Extenders might be more appropriate to use.
Table 1. Scaling requirements for HCL Traveler integration module
Item Requirement
HCL Traveler (less than 10,000 mailboxes) Mailboxes - less than 10,000 mailboxes
Devices - less than 5,000 devices
CPU - 2 cores
Memory - 8 GB
HCL Traveler (more than 10,000 mailboxes) Mailboxes - more than 10,000 mailboxes
Devices - more than 5,000 devices
CPU - Use more Cloud Extenders
Memory - Not applicable
IBM SmartCloud

Mailboxes - All

Devices - All
CPU - 2 cores
Memory - 8 GB
Scaling - Supports only one instance of the Cloud Extender for each URL.

For accurate scaling of your environment, see the Cloud Extender scaling document at Setup > Services > Enterprise Email Integration.
Module requirements -
  • IBM SmartCloud Notes® or Lotus® Domino® 8.5.2 or later
  • For HCL Traveler integration - The Cloud Extender must be installed on a computer with the Lotus Notes client.
  • For IBM SmartCloud - Network access from the Cloud Extender server to the IBM SmartCloud URL.
  • .NET 3.5 or higher
Permission requirements -
  • For Lotus Notes 8.5.2+ - A Domino account and credentials with sufficient rights for the Domino or Traveler Admin. You must have at least an access level of Server Remote Admin Manager with delete access to Traveler.nsf.
  • For IBM SmartCloud - Account with Administrator rights in the IBM SmartCloud environment.