Back to Documents

 

NED System Configuration

 

1. Relational Database (RDB): Stores

 

·         NIH UIDs and associated individual identifying information

·         public "white pages" information that is published in the LDAP directory

·         other private information that is not published in the LDAP directory

·         tables describing NIH buildings and organizations

·         data validation tables

·         tables holding working copies of other connected directories and databases

·         tables used by the AO registration and update web service for authorization and workflow

 

Currently, the NED RDB is implemented in Oracle 8 running on the Enterprise Open System operated by CIT/DCSS.  See Section 3.3 of the Fast Track Directory Definition for further details.

 

2. Directory Registration and Update Services: Applications that enable registration authorities to register/deregister individuals to/from the NED, and update an individual’s directory information.  NED Phase 1 includes a web application used by IC Administrative Officers (AOs) and Administrative Technicians (ATs) to perform these functions for NIH FTEs, fellows, tenants, and on-site contractors, guests, and volunteers.  This application currently runs on an NT/IIS server maintained by OCTO staff and located in FED/814.

 

In the future, additional registration/update services will be required as NED is extended to cover additional populations, e.g. CIT data center customers from other Federal agencies, NIH grantees, or outside participants in NIH training programs.  COTS software such as Oblix may be used to implement some or all of these.

 

3. LDAP Directory Server: Contains a writable copy of the same information stored in the NED RDB (except for the AO registration and update service authorization and workflow tables), and provides access to this information via the Lightweight Directory Access Protocol (LDAP).  Currently, we are evaluating ISOCOR’s Global Directory Server running on a Solaris machine maintained by OCTO staff and located in FED/814.  However, we plan to migrate this function to Microsoft Active Directory as soon as possible, and prior to production operation.

 

4. Connected Databases and Directories: Other NIH databases and directories that exchange data with the NED.  For NED Phase 1 these include:

 

·         The Human Resources Database (HRDB)

·         The Fellowship Payment System (FPS)

·         The J. E. Fogarty database of visiting fellows, scientists, and guest researchers

·         The ID badge, Parking, and TRANSHARE database (PAID)

·         The NIH Telephone and Service Directory

·         The NIH Email Directory and Forwarding Service (PH)

·         The Integrated Time and Attendance System (ITAS)

 

Future NED phases will connect to additional databases and directories, for example:

 

·         FPS-2

·         New ID Badge/Card Key

·         Exchange/NT Domain/Active Directory

·         Novell Directory Service (NDS)

·         Remedy/Web Sponsor/…

·         Data Warehouse

·         Mail Office

·         Central Facilities and Maintenance Mgt Systems

·         IMPAC 2

·         NIH Library

·         Radiation Safety

·         VEDS

·         WATSON

 

5. Meta-Directory Join Engine: Joins the information contained in multiple connected databases and directories that belongs to the same individual into a single meta-directory entry, and propagates changes to this information bidirectionally among them. Currently, we are evaluating ISOCOR MetaConnect running on an NT server maintained by OCTO staff and located in FED/814.

 

6. Record Linking Engine:  Calculates the odds that two records identify the same individual, often using individual identifying information covered under the Privacy Act.  Used to:

 

·         eliminate duplicate records in existing databases;

·         link records in connected legacy databases and directories to NED entries so they can be associated with the correct NIH UID;

·         search the NED when a “new” employee is registered to determine if the individual has already been assigned an NIH UID; and

·         Operate with the Join Engine to link newly-created entries from connected directories and databases to the NED.

 

The first two functions will be performed by batch programs running on NT and Solaris.  The third function is currently running as a web service on cecil.cit.gov, a Solaris 2.5 machine maintained by ALW and located in the Bg. 12 machine room.  The fourth function will be performed by a Perl script integrated with the Meta-Directory Join Engine.