This task should only be configured when you are connecting your installation to an LDAP server. It is optional to run this task. When it is running, it will synchronize the LDAP server data that is required within ExtraView, on a periodic basis. This avoids ExtraView reaching out to the LDAP server for user information on each occasion it is required, and uses the information previously read into ExtraView. Simply adding, or editing may often require reading many users' details, and this task makes this operation much more efficient. This task should be configured in preference to the LDAP Synchronization Task. You should not configure both tasks.
Without this task being started, ExtraView makes a call to the LDAP server for each and every requirement for any user's information that is required. This ensures that ExtraView always receives up-to-date information. Unless the LDAP server is configured to offer high speed delivery of all responses, this can lead to minor delays in the processing within ExtraView and a resultant slow response to end users.
However, user data within an LDAP server is typically "slow-moving", and changes infrequently. This task will refresh the data for users whose information is stored within ExtraView on a timed basis. There is a possibility that the user's data may have changed in the LDAP server, but as long as the poll interval is kept to a modest time, the chances are that the cached data within ExtraView will be correct.
This task should only be run on a single node within a clustered environment.
