ldapDriver-LdapServer (Ldap Server)

This component manages the connection to the LDAP server.
Figure 93.   LdapServer Properties
Image

To view these properties, expand the Config > Drivers > LdapNetwork and double-click LdapServer

In addition to the standard properties (Status, Enabled, Fault Cause, Health and Alarm Source Info), these properties are unique to this Property Sheet.

Property Value Description
Ldap Connection additional properties Configure additional parameters for ldap connection.
Vendor Name read only Identifies the name of the LDAP server vendor.
Vendor Version read only Reports the software version of the LDAP server.
Users additional properties Configure discovery preferences. The separate topic, ldapDriver-LdapUsersDeviceExt, documents these properties.
Attributes additional properties Configure object and group attributes. The topic, ldapDriverLdapAttributesDeviceExt documents these properties.
User Search Base text Defines where to start searching for personnel in the LDAP server hierarchy.

ou stands for organizational unit.

dc stands for domain controller.

dn stands for distinguished name. This name both uniquely identifies an entry in the LDAP database and describes its position in the hierarchy.

User Search Filter text Defines the objectClass (metadata) associated with each personnel record that identifies it as a personnel record versus a system or other record type in the server database.
Search Scope drop-down list Defines how much of the User Search Base to actually search.

Object Scope

One Level Scope

Subtree Scope extends the scope to the child nodes of the node defined in the Group Search Base expression.

Polling Interval hrs:min:sec (defaults to 5 minutes) Defines how frequently to poll the LDAP server.
Periodic Purge Schedule time stamp Determines when a TimeTrigger fires.

Daily fires the trigger at a specific time on selected days of the week, and includes a randomized interval so that the trigger does not fire at exactly the same time every day. Randomized firing is useful when handling large volumes of data.

Interval fires a trigger each time the specified interval elapses. You would use it to fire the trigger several times per day (for example, every 5 minutes).

Manual requires a human to fire a trigger.

When this trigger fires for a station database, a system indexer (LocalSystemIndexer or GlobalNiagaraNetworkIndexer) executes its index operation.
 CAUTION: Indexing a database is a memory- and CPU-intensive operation that affects the availability of your SystemDb and remote stations. Do not configure a re-index to occur too often so your SystemDb and remote stations can maintain availability throughout the day. If your SystemDb is indexed frequently, query performance degrades.