Name lookup
For HCL 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.
There are three types of lookups. All three are Domino® API calls that use the directories
as configured by Domino®.
Depending on the configuration, this can be the local names.nsf,
or through Directory Assistance. The caches are included in the SystemDump.
As a result, you can see the contents by running SystemDump,
using either the default options or the Sync option.
Traveler user lookup
This lookup type attempts to find out information about specific users, such as mail addresses,
mail servers, and ACLs. It is always done on the HCL Traveler server. The results of this lookup are
cached for up to 4 hours (240 minutes) by default. Depending on circumstances, such as errors, HCL
Traveler may clear the user's cached results and perform the lookup again. The administrator can
force this cache to be refreshed for the user by using the tell traveler user
<username> tell command. The options for this lookup are controlled by the
NTS_USERCACHE* notes.ini properties. For more information, see Notes.ini settings.
Address substitution lookup
Whenever data is being synchronized between the server and the device and contains a mail address (mails, invitations, meetings, contacts, and so on), HCL Traveler may convert the address, as some devices tolerate all forms of addresses and some do not. In particular, many devices only fully support internet addresses and do not work with, or give warnings about, other address formats. Therefore, HCL Traveler will attempt to substitute the given address with one that the device prefers. To perform this address substitution, HCL Traveler must do a lookup to find all addresses. This is occasionally referred to as the "Address Cache".
By default, this lookup is always done on the user's mail server and not the HCL Traveler server.
However, the NTS_TRAVELER_AS_LOOKUP_SERVER notes.ini property can be used to force
these lookups to be done on the HCL Traveler server instead. These results are cached for up to 24
hours and are not allowed to exceed 10,000 entries. Because different mail servers may have
different results, results are cached on a per result, per mail server basis.
The options for this lookup are controlled
by the NTS_ADDRESSCACHE* notes.ini properties. For
more information, see Notes.ini settings.
Corporate lookup
This is a lookup done by a user on their device to find addresses. Any lookup being done from the device that accesses the server is a corporate lookup. Examples of places where this is done are addressing a mail, creating a meeting, searching in contacts, and using the name lookup application.
By default, this lookup is always done on the user's mail server and not the HCL Traveler server.
However, the NTS_TRAVELER_AS_LOOKUP_SERVER notes.ini property can be used to force
these lookups to be done on the HCL Traveler server instead.
Due to the shear volume of the results per lookup, these results are not cached.
The options for this lookup are controlled by the NTS_NAME_LOOKUP*
notes.ini properties. For more information, see Notes.ini settings.