HCL Domino® setup considerations
There are considerations to be aware of when setting up HCL Domino®.
- The end user must have Editor access (plus Delete) or higher in the ACL of their primary mail file and any replica mail files that will be used to sync data to the user's mobile devices.
- The end user must have Editor access or higher for the Maximum Internet name and password field on the Advanced tab of the ACL for their primary mail file and any replica mail files that will be used to sync data to the user's mobile devices.
- The HCL Traveler server must be listed as a Trusted Server on the Security tab of the Server document for every mail server that will be accessed by the Traveler server. Typically, this is done through a group such as LocalDomainServers.
- The Domino® server that hosts HCL Traveler must have access to user mail servers and Manager plus delete access to mail files. This access is typically granted by adding the Traveler server to the LocalDomainServers group.
- 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 more information, see The Domino mail router in the Domino documentation.
- In a multi-domain environment, the Domino® server hosting HCL Traveler might need to be cross certified with the other Domain mail servers for access to be granted.
- Each user must have an HTTP password, or directory assistance must be configured so that the user ID and password can be validated.
- Each user should have an Internet address specified in their person document. In general, mobile devices work better with Internet addresses than with Domino® style addresses.
- Each user must be in the local
names.nsf
database of this Domino® server or directory assistance must be configured so the users can be found. - If you are using Internet Site documents and plan on syncing Apple devices, ensure that the Options command is enabled on the Configuration tab of the Internet Site document. This is required to register and sync Apple devices.
- Set More name variations with less security in the Internet authentication parameter on the Security tab of the server document. This action resolves many login issues.
- Review the HCL Domino® documentation before installing HCL Traveler. In particular, read the sections on SSL, directory assistance, HCL Domino® domains, and HCL Domino® mail router. These are HCL Domino® functions and not controlled by HCL Traveler.
- HCL Traveler requires the following
notes.ini
parameters during startup. Review them and be sure that they have the correct values, or HCL Traveler can fail to start.NotesProgram
Directory
ServerName
Domain
- 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.
- HCL Traveler does not support Roaming Users or Roaming Profiles. All of the user's data must exist in the mail file on the mail server.