Home
Administering IBM Traveler
Information on planning, installing, configuring, and administering IBM Traveler.
Configuring IBM Traveler server
The IBM Traveler configuration settings are part of the Domino® server document. The first time that the IBM 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 IBM Traveler High Availability Pool
Configuring IBM Traveler to use a High Availability Pool requires special configuration steps.
Enable server to server secure communications (optional)
By default, IBM Traveler uses regular TCP sockets for communication between the IBM Traveler server and the HTTP server, as well as for communications between the IBM Traveler servers within an HA pool.

Administering IBM Traveler
Information on planning, installing, configuring, and administering IBM Traveler.
- Planning for installation and configuration
  There are many installation and configuration considerations you should review before installing the IBM Traveler server.
- Installing the IBM Traveler server
  The following topics describe options for installing and uninstalling the server:
- Configuring IBM Traveler server
  The IBM Traveler configuration settings are part of the Domino® server document. The first time that the IBM 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.
  - IBM Traveler server settings
    You can configure a variety of IBM Traveler server settings, including server document settings and notes.ini settings.
  - Manually configuring the HTTP server
    This topic includes a complete list of all Domino® HTTP configuration changes required to successfully start and run IBM Traveler. In general it is not necessary to make any manual configuration changes to the Domino server. However, in some environments the IBM Traveler server may not have write access to the Domino server document. In this case, add NTS_AUTO_CONFIG=false to the Notes®.ini file to suppress any error messages, and then make the required changes to the server document as specified in this topic.
  - HTTP authentication
    This section provides HTTP authentication information.
  - Configuring the IBM Traveler High Availability Pool
    Configuring IBM Traveler to use a High Availability Pool requires special configuration steps.
    - Understanding the IBM Traveler schema
      Since the IBM 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 IBM Traveler supports (DB2 or SQL Server ), it is necessary to grant the appropriate level of permissions for running the IBM Traveler server with either autoschema 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 both DB2® and SQL enterprise databases for IBM® Traveler.
    - Configuring IBM® Traveler for enterprise database
      You can configure the IBM® 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 IBM Traveler High Availability pool on IBM® i
      This section describes how to configure the IBM 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 IBM 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 IBM 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 IBM Traveler servers in the pool.
    - Setup for common configuration (optional)
      In a IBM Traveler pool, it is critical that each server is configured identically.
    - Enable server to server secure communications (optional)
      By default, IBM Traveler uses regular TCP sockets for communication between the IBM Traveler server and the HTTP server, as well as for communications between the IBM Traveler servers within an HA pool.
    - Removing a server from a High Availability pool
      A IBM Traveler High Availability (HA) pool is a group of servers that are all configured to use the same enterprise database.
  - 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 IBM Traveler server.
  - Configuring ports for a partition
    IBM 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.
  - Securing the device connection
    It is recommended that you secure the HTTP traffic to and from the IBM Traveler server. The traffic can be secured by enabling SSL for the Domino® HTTP server or reverse proxy, or by using a VPN.
  - Converting Notes® document links to web links
    Notes® links that are contained in mail messages and viewed on IBM 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.
  - 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 IBM® Traveler tab in the Server document.
  - 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 IBM Traveler server. However, you must configure the Microsoft™ Exchange account on the device so that it can use Exchange ActiveSync to connect to the IBM 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 IBM 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 IBM 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.
  - IBM Traveler Companion security settings
    Starting with IBM® Traveler Companion 2.0.5 and IBM Traveler server 8.5.3.2, there are new security settings available that control how Companion connects to the IBM Traveler server and how attachments in encrypted mails can be used on the mobile device.
  - 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.
- Administering IBM Traveler
  The IBM 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 IBM Traveler server.

Enable server to server secure communications (optional)

By default, IBM Traveler uses regular TCP sockets for communication between the IBM Traveler server and the HTTP server, as well as for communications between the IBM Traveler servers within an HA pool.

It may be desirable to use secure sockets for this communication if the networking between the IBM Traveler servers is not isolated or secure. Note that requiring secure server to server communications will impact overall performance.

To enable the use of SSL sockets between the IBM Traveler servers, the following steps can be used:

To generate a self-signed certificate with an expiration date far in the future, use the following example:
```
<domino>\jvm\bin\keytool -genkey -v 
   -alias "Traveler" 
   -validity 9999 
   -keystore traveler.jks
   -storepass <password>
   -keypass <password>
```
Note: For IBM® i, the keytool is located at: /QOpenSys/QIBM/ProdData/JavaVM/jdk80/32bit/bin or /QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit/bin
It is recommended you use the same password for the storepass and the keypass. If the password parameters are omitted, the keytool will prompt for them.
Copy the traveler.jks that was just created to each server. A suggested location is <domino data>\traveler\cfg. It is important for the servers to use the same certificate file, so the keytool command should not be run on each server.
Open a command prompt.
Change the directory to <domino data>\traveler\util.
Run travelerUtil to configure IBM Traveler to use SSL:
```
travelerUtil ssl set keystore=<domino data>\traveler\cfg\traveler.jks key=<password>
```
Specify the same password that was used for the storepass and keypass parameters with the keytool command.

After making these changes, both the Traveler task and the HTTP task must be restarted on the IBM Traveler Server. When the IBM Traveler server restarts, it will use SSL sockets to communicate with other IBM Traveler servers.

Repeat these steps for each IBM Traveler server in the pool. All the IBM Traveler servers in the pool must be configured the same way; otherwise, they will not be able to communicate with each other.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.