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.
If you are using MobileIron and setting up IBM Traveler ToDo and IBM Traveler Companion, see
on how to set the External URL setting.
This URL sets the IBM Traveler servlet URL as the URL through which to perform all IBM Traveler
transactions and data synchronization. This value should be a URL that IBM Traveler users can always
access, whether on an internal network or the internet, and should not change.
If there is a reverse proxy in use, the URL should be set using this reverse proxy name. If there
is a DNS name or IP that is used to route external traffic to the IBM Traveler server from the
internet, the URL should be set using this DNS name or IP address.
This field should specify the complete path to the Traveler servlet,
including http:// or https://, any
port numbers if non-default values are in use, and should end in /traveler.
The URL may be case-sensitive depending on the HTTP server. For
After making a change to the external server URL in the server document, restart the IBM Traveler
task. The external server URL field will only be present if the server's address book is at the
8.5.2 template level or above. If the field is not present in the server document because the
address book is on an older template version, the external server URL can be set in
with the parameter NTS_EXTERNAL_URL
. For example:
If the proxy is not using the default :80
then the port number must be in the URL. For example:
is added to or changed in notes.ini
restart the IBM Traveler task to make the change effective.
NTS_EXTERNAL_URL parameter in notes.ini will take precedence over
the external server URL field in the Server document. If NTS_EXTERNAL_URL was added
to notes.ini while using Traveler version 8.5.1, ensure that the value is correct
as described in this article, as this parameter's usage has changed in versions 8.5.2 or later.
Problems may occur due to an incorrect URL setting that were not experienced in version