Understanding SAIP LDAP Integration
In addition to the web service support, SAIP provides the ability to provision person, enrollment, and course data to an LDAP directory. This enables applications that cannot consume web services but can read groups from an LDAP directory to be provisioned. The data is fundamentally the same as that which is provisioned via web services. All XML record types are replicated as LDAP directory subtrees. Because common LDAP practice discourages use of object hierarchy within records, there is an additional subtree type of Person Detail which contains a subset of the data that is contained within the Person XML record in the SOAP integration.
With LDAP integration, SAIP generates one or more LDIF files that may be imported into an LDAP directory. The process of generating LDIFs is conceptually similar to running a batch process for SOAP integration, with two important differences. First, the LDIF process is initiated within SAIP rather than by the consuming application. Second, LDAP integration checks the target system when generating an LDIF in order to validate the delta between the two systems.
Note: The Student Administration Integration Pack is a single target (multi-consumer) mechanism, meaning that it is currently designed to produce a single output stream, although multiple applications can consume that output simultaneously. An LDAP directory would be considered a "target" in the same way that an integration gateway would be considered target. Therefore, you can run either the web serviced binding of the SAIP, or the LDAP binding, but you cannot run the two bindings simultaneously. Doing so will produce unpredictable results.