Choosing a deployment configuration

The HCL Traveler server can be deployed using several different configurations.

The HCL Traveler server is installed and runs on an HCL Domino® server. The server must have access to the mail files of mobile HCL Traveler users. These mail files are either located on the same server as the HCL Traveler server or they are hosted on remote Domino® servers. HCL Traveler uses a HCL Domino® directory to find the home mail server for a HCL Traveler user. If the mobile users are not present in the local Domino® directory (names.nsf), then HCL Domino® directory assistance must be configured so that these users can be found in remote Domino® directories.

HCL Traveler servers can be deployed as standalone servers, or if a highly available environment is required, as part of a pool of servers.

The HCL Domino® server that is hosting each HCL Traveler service must have the HTTP web server component installed. This component is installed by default when you install your HCL Domino® server.

HCL Domino® service provider configuration is not supported by HCL Traveler. HCL Domino® Service Provider setup does not allow servlets which are required for HCL Traveler to function.

The Domino® server hosting HCL Traveler should have mail routing configured to/from the mail servers. This is only an issue for HCL Traveler servers that are not also mail servers. See Notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER in Notes.ini settings as an alternative if there is a concern with setting up mail routing on the Traveler server.

For information about the types of server and network topologies to consider and details about local and remote mail files, see these topics: