Poll Rate in Seconds

This is the interval at which the driver will check the LDAP server's change log. When new changes are found, they are applied to Novell eDirectory^TM.

The recommended polling rate is 120 seconds.

Change Log Entries to Process on Startup

This parameter specifies where in the change log the Publisher looks for change entries.

• 1-All: The Publisher will attempt to process all of the changes found in the change log. It will continue until all changes have been processed. It will process new changes according to the poll rate.
• 2-None: The Publisher will not process any of the changes from the change log when the driver starts running. It will process new changes according to the poll rate.
• 3- Previously Unprocessed: This setting is the default. If this is the first time the driver has been run, it behaves like 1-All, processing all changes in the change log.

  If the driver has been run before, this setting causes the Publisher to process only changes that are new since the last time the driver was running. Thereafter, it will process new changes according to the poll rate.

Maximum Batch Size for Change Log Processing

When the Publisher processes new entries from the LDAP change log, it will ask for them in batches of this size. If there are fewer than this number of change log entries, all of them will be processed immediately. If there are more than this number, they will be processed in consecutive batches of this size.

Prevent Loopback

This is an advanced parameter and is not present in the sample configuration because you will seldom need to change the default behavior. The default behavior for the Publisher channel is to avoid sending changes that were made by the Subscriber channel. The way the Publisher channel detects subscriber channel changes is by looking in the LDAP change log at the creatorsName or modifiersName to see whether the authenticated entry that made the change is the same entry that the driver uses to authenticate to the LDAP server. If the entry is the same, then the Publisher channel assumes that this change was made by the driver's Subscriber channel and will not synchronize the change.

If you are certain that you want to allow this type of loopback to occur (for example, if you don't have a Subscriber channel configured for this driver and you want to be able to use the same DN and password as other processes use to make changes with), then you can set the parameter by editing the driver parameter XML.

To edit the driver parameter:

1. In iManager, click DirXML Management > Overview.

2. Find the driver in its driver set.

3. Click the driver to open the Driver Overview page, then click the driver again to open the Modify Object page.

4. Scroll to the bottom of the Driver Configuration parameters and click Edit XML.

5. In the Driver Parameters XML, find the line that contains </publisher-options> and add the following line immediately above it:

   <prevent-loopback display-name="Prevent loopback">no</prevent-loopback>

6. Click OK, click Apply, then restart the driver for this parameter to function.

Preferred Object Classes

An optional driver parameter has been added to let you specify preferred object classes on the Publisher channel.

DirXML requires that objects be identified using a single object class. However, many LDAP servers and applications can list multiple object classes for a single object. By default, when the DirXML Driver for LDAP finds an object on the LDAP server or application that has been added, deleted or modified, it sends the event to the DirXML engine and identifies it using the object class that has the most levels of inheritance in the schema definition.

For example, if a user object in LDAP is identified with the object classes of inetorgperson, organizationalperson, person, and top, then by default the driver will use inetorgperson as the object class it reports to the DirXML engine because inetorgperson has the most levels of inheritance in the schema (inheriting from organizationalperson, which inherits from person, which inherits from top).

If you want to change the default behavior of the driver, you can add the optional driver Publisher parameter named preferredObjectClasses. The value of this parameter can be either one LDAP object class, or a list of LDAP object classes separated by spaces.

When this parameter is present, the DirXML Driver for LDAP examines each object being presented on the Publisher channel to see if it contains one of the object classes in the list. It looks for them in the order they appear in the preferredObjectClasses parameter. If it finds that one of the listed object classes matches one of the values of the objectclass attribute on the LDAP object, it uses that object class as the one it reports to the DirXML engine. If none of the object classes match, it resorts to its default behavior for reporting the primary object class.

To add the optional driver Publisher parameter preferredObjectClasses, do the following:

1. In iManager, navigate to the DirXML Driver Overview page for the LDAP driver.

2. Click the LDAP driver icon to access the Modify Object page for that driver.

3. If necessary, scroll to the Driver Parameters section.

4. Click the Edit XML button for that section.

5. On the Driver Parameters (XML) page that opens, check the Enable XML Editing checkbox.

6. Below the <publisher-options> open tag (but before the closing tag) insert the following XML element. Replace the example of inetorgperson with your list of preferred object classes.

   <preferredObjectClasses display-name="Preferred object classes">inetorgperson</preferredObjectClasses>

7. Click OK to save and close the Driver Parameters (XML) page.

8. Click OK to save and close the Modify Object page for the driver.

9. If the driver was running, restart it.