Overview#As part of a a Novell led team to design and build synchronization from Edirectory to Custom Oracle Database.
Designed and implemented Novell's JDBC driver to meet the requirements.
NYCT previously stored all functional data for Photo Identification Card application in an Oracle 8i database. Employee information was needed to be synchronized from I-Vault to the PIC System, and Cardholder information will be synchronized from the PIC System to I-Vault. Card holder data is needed to authenticate new users in I-Vault.
Implementation Overview#This implementation deviates from the standard IDM JDBC driver design to support the overall goals and technical requirements of the PIC Identity solution. These decisions were made after weighing several options carefully, and were decision points made between the joint team during the discovery and design phase of this engagement.
The normal “goal” of the “standard” IDM JDBC connector is to maintain synchronization between a SQL table and a Edirectory ObjectClass. The design requirements prevent the normal implementation of the IDM JDBC driver. The IDM PIC connector is implemented as two instances of the IDM JDBC driver. One driver handles data flow “To PIC” and one handles data flow “From PIC”. The implementation provides a clean separation of the duties of each instance of the driver while allowing the design requirements to be obtained.
The design requirements may be classified in two basic functional requirements.