Parameter:
LDAPConfigUpdateIntervalShort description: Interval (in minutes) at which the LDAP task reloads its configuration from the Domino directory. Default: 3 minutes.
Profile
Parameter | LDAPConfigUpdateInterval |
Category | General (LDAP service) |
Available since | At least 9.0.1 (HCL docs 9.0.1 – 14.5.1) |
GUI equivalent | No direct GUI — changes the reload interval of the LDAP configuration |
Possible values | Integer in minutes (e.g. 1, 3, 5, 10) |
Default | 3 (minutes) |
Description
According to HCL product documentation (14.5.1, Customizing the LDAP service configuration):
Except where noted in the table, restarting the LDAP task or the HCL Domino® server is unnecessary after changing a setting because the task checks for setting changes automatically, by default at three-minute intervals. You can use the NOTES.INI settingLDAPConfigUpdateIntervalto change the interval at which the LDAP service checks for changes to its settings.
LDAPConfigUpdateInterval defines how often the LDAP server task reloads its configuration from the Domino directory. Sources for LDAP configuration are:- Server document (port/TLS settings)
- Configuration Settings document (LDAP tab; anonymous fields, schema enforcement, timeouts, maximum entries, etc.)
- Domino directory's own LDAP settings
Most LDAP settings are picked up dynamically — a server restart or LDAP restart is only required for a few settings (explicitly identified in the HCL table). With
LDAPConfigUpdateInterval, the polling interval can be shortened (faster pickup during change-intensive phases) or lengthened (reduce load on servers with rarely changed LDAP settings).Example configuration
Default behavior (omit the parameter) corresponds to 3 minutes:
LDAPConfigUpdateInterval=3
Faster pickup for test/tuning phases (1 minute):
LDAPConfigUpdateInterval=1
Production with rarely changed settings (10 minutes):
LDAPConfigUpdateInterval=10
Notes & pitfalls
- Value in minutes, not seconds — a value of
30means 30 minutes, not 30 seconds.
- The parameter only affects settings that can be picked up dynamically. Settings that, according to the HCL table, require a restart (e.g. port settings, Allow LDAP users write access, schema changes) are not picked up without a restart even with a short interval.
- Very short intervals (1–2 minutes) increase the load on the Domino directory through frequent re-reads — only useful in exceptional cases.
- Very long intervals (>15 minutes) can cause confusion when changes "don't take effect" — a typical support trigger.
- For immediate pickup of a single change:
tell ldap reloadon the server console, independent of this interval.
Sources (HCL Product Documentation)
- HCL Domino 14.5.1 – Customizing the LDAP service configuration: help.hcl-software.com/domino/14.5.1/admin/conf_customizingtheldapserviceconfiguration_c.html
- HCL Domino 11.0.1 – Customizing the LDAP service configuration: help.hcl-software.com/domino/11.0.1/admin/conf_customizingtheldapserviceconfiguration_c.html
- HCL Domino 9.0.1 – Customizing the LDAP service configuration: help.hcl-software.com/domino/9.0.1/admin/admin/conf_customizingtheldapserviceconfiguration_c.html