1. Some issues in databse-directory integration
Shridhar Shukla
LDAP-RDBMS integration product group, PSPL
Persistent Systems Private Limited (

2. An Example of where LDAP fits
Persistent Systems Private Limited (

3. Database/LDAP integration
Application
RDBMS
Server
SQL to
LDAP (PS EnList)
LDAP
to SQL (?)
Synchronization
(PS EnSure)
Persistent Systems Private Limited (

4. Persistent Systems Private Limited (http://www.pspl.co.in)
LDAP to SQL
(&(Objectclass=*)(cn =‘sha*’))
Option 1: A schema that fits the hierarchy
Unique id, an entry table per objectclass, indexed thin tables (IBM)
Option 2: Represent the hierarchy using foreign relations
mismatch
Option 3: Expose existing schema as LDAP
What will it take? How will write performance get affected? Can there be a general model?
Persistent Systems Private Limited (

5. Persistent Systems Private Limited (http://www.pspl.co.in)
SQL to LDAP
A structured approach to splitting the query
between the LDAP server and PS EnList
Caching of query results
Consolidation of schema across servers
High-value operators and SQL extensions
Recognize LDAP usage and optimize
Persistent Systems Private Limited (

6. LDAP to DB synchronization
application
Directory
application
Join Engine 1 5
Do we not need to show that the config info gets into the MDS at this point?
Also, we need to make it explicit that the instrumentation operation includes successful execution of the scripts (which is done outside the DCC GUI). 3 4
Dir
Source DB
Change
log DB 2
Persistent Systems Private Limited (

7. Synchronization issues
The source DB data model cannot change.
Changes from multiple tables for an entity need to be synchronized with the directory
Large volumes
Selective policies, e.g., password
Persistent Systems Private Limited (