Home
Administering HCL Traveler
Information on planning, installing, configuring, and administering HCL Traveler.
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.
Maintaining the HCL Traveler database
Whether running standalone HCL Traveler servers with the internal database or a pool of servers with an enterprise database, the database requires periodic maintenance to maintain optimal performance.
Updating the enterprise database credentials
When the password for an enterprise database expires or has been changed, HCL Traveler will need to be updated with the new credentials.

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.
- 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.
  - Starting and stopping the server
    The HCL Traveler server and the HTTP server automatically start if you accept the default settings during installation. Use the commands in this topic to manually start or stop the HCL Traveler server.
  - Using the administration application
    The HCL Traveler administration database is contained in the LotusTraveler.nsf. This database contains the user interface that is used to view mobile user and device information, as well as set default device preference and security policies.
  - Assigning preferences and security settings to devices
    There are different ways to assign settings that determine how users work with the HCL Traveler server. You can use the built-in set of default device preferences and security settings that HCL Traveler provides, which is simpler. Or you can create a HCL Traveler policy settings document, which provides greater flexibility and control but is more complex to configure.
  - Device security
    There are a number of considerations to be aware of when securing different device types.
  - Working with attachment security settings
    You can control how HCL Traveler clients manage file attachments and images.
  - Remote wipe
    If a mobile device is lost or stolen, an administrator can issue a remote wipe command to remove all sensitive data from the device. You can remove the HCL Traveler application and data from the device and, depending on the device, restore the device to the factory default settings.
  - Console commands
    This topic provides a detailed description of the HCL Traveler console commands.
  - ***
  - ***
  - Controlling access to HCL Traveler
    When a user leaves the company or a device is lost or stolen, you must remove or restrict access to the HCL Traveler server. This section covers methods for removing and restricting access.
  - Deleting a user from HCL Traveler
    An administrator can remove old or invalid users from the HCL Traveler administrator UI and database. This should only be done for users where access is already restricted using a HCL Traveler or Domino® server access list, or who are no longer listed in the Domino directory.
  - Creating links to start the HCL Verse mobile app
    Create links that a user can click to start the HCL Verse mobile app from a web page or email.
  - Enabling syncing of read or unread changes
    Unread replication is enabled for each user automatically by the HCL Traveler server so that unread marks sync correctly with the device. This section explains how to activate unread replication manually using the Domino® Administrator client.
  - Repeated crash protection
    When certain Notes® documents are corrupted or contain non-standard content, they can cause the HCL Traveler server to repeatedly crash as it tries to process these documents. A repeating crash prevention feature exists to help minimize HCL Traveler server outage in these instances.
  - Maintaining the HCL Traveler database
    Whether running standalone HCL Traveler servers with the internal database or a pool of servers with an enterprise database, the database requires periodic maintenance to maintain optimal performance.
    - Defragmenting the internal database for improved performance
      As HCL Traveler installations become larger and run for extended periods of time, the internal database will grow in size. This can affect system performance. You can defragment the database to compact and optimize its performance.
    - Maintaining the enterprise database
      The enterprise database used with a HCL Traveler High Availability pool requires periodic maintenance just like the internal database used by a standalone server.
    - Updating the enterprise database credentials
      When the password for an enterprise database expires or has been changed, HCL Traveler will need to be updated with the new credentials.
    - HCL Traveler database maintenance for standalone servers
      HCL Traveler can be configured to perform defragmentation on a configured interval for stand alone servers.
    - HCL Traveler database maintenance for HA deployments
      The HCL Traveler server has the ability to perform basic database maintenance tasks including reorganizing indexes and running statistics.
  - ***
  - Enforcing data sync limits
    Administrators can enforce synchronization data limits for all users using a setting in the Default Settings document.
  - Log types
    HCL Traveler has many different logs with a variety of purposes.
  - HTTP request handling and 409 responses
    HCL Traveler handles HTTP requests in specific ways that may result in 409 responses.
  - Confirming external recipients on Android devices
    For HCL Verse for Android clients, you can choose to prompt the user to confirm the sending of mail to external recipients. This provides an extra step to help prevent the unintentional sending of mail outside of your organization.
  - Adaptive Initial Sync
    Adaptive Initial Sync (AIS) helps ensure server availability in certain server bring up or recovery situations.
  - FCM messaging for HCL Verse for Android clients
    HCL Traveler server can use Firebase Cloud Messaging (FCM) for real time push notifications to keep your Mail, Calendar, Contact and To Do data on your HCL Verse for Android clients up to date. Google has deprecated GCM and replaced it with FCM.
  - How synced data moves through the system
    When a device needs to sync data with the user's mail server, the user registers that device with the HCL Traveler server. This involves some initial setup which includes negotiating security settings as well as data options and filters to be used when syncing the data from the user's mail database to the device and vice versa.
  - How HCL Traveler processes attachments
    There are several issues to be aware of in how HCL Traveler processes attachments.
  - ***

Updating the enterprise database credentials

When the password for an enterprise database expires or has been changed, HCL Traveler will need to be updated with the new credentials.

You can do this using the travelerUtil utility. For HCL Traveler Servers running on Windows™, update the database credentials with the following command:

travelerUtil db set user=[userName] pw=[newPassword]

For HCL Traveler Servers running on Linux™ or AIX, update the database credentials with the following command:

./travelerUtil db set user=[userName] pw=[newPassword]

For HCL Traveler Servers running on IBM i, do the following:

Run the following command to start the QShell Interpreter:
```
QSH
```
Navigate to the HCL Traveler utility directory:
```
cd /<domino data>/traveler/util
```
Update the database credentials with the following command:
```
./travelerUtil db set user=[userName] pw=[newPassword] 
```

In all cases, the user and pw parameters can be omitted. If you do omit them, you will be prompted to enter their values.

Since you are not changing the database type or the database the HCL Traveler Server is using, you do not need to specify the JDBC URL as you were instructed to in Configuring HCL Traveler for enterprise database.

The travelerUtil will validate the user and password by attempting to connect to the database. Once a connection has successfully been made, the connection will be closed and the new credentials will be encrypted and stored in the LotusTraveler.nsf.

Repeat this process for every HCL Traveler server in the high availability pool.

Important: Changing the database user name is not recommended unless you are certain the user has appropriate access to the database. If you are using DB2, you must also ensure the correct schema is used by setting NTS_DB2_SCHEMA in the notes.ini file to the correct schema name, generally the old DB user name.