Identifier Translation Options: SSN/UFID/UUID

The University of Florida is a complex and diverse organization. Unit missions and staffing capabilities vary widely and preferred computing environments are equally diverse. Unit programmers involved in translating identifiers may choose to utilize mainframe-based API functions directly or may prefer to use Java, perl, C, C++, Visual Basic or other languages to support local systems.

All options described below require pre-approved authorization. Approval requirements for software created to use either of these two programming options are documented on the UF Directory Project web site (see “Obtaining Authority to call an API by Registering Applications.”) located on the API page.

Option 1: Software access using DB2 database APIs or views.

IBM’s DB2 Run-Time Client (version 7.2) must be installed locally to gain ODBC access to a DB2 stored procedure API or Identifier view managed by UF Enterprise Systems. Contact Debbie Sams at UF Enterprise Systems or Richard Marquis at CNS if you have any questions concerning client configuration issues.

Units utilizing this approach for interacting with the UF Identity Registry are responsible for developing software applications to maintain or update local database applications. Unit programmers must handle all details associated with making database connections and calling available stored procedures. This option may be useful in automating routine, repetitive processes.

Information on the use of DB2 stored procedure APIs associated with the UF Identity Registry is can be found in the technical data section under UF Identity Registry docs on the APIs page.

Download and install the runtime client from:

Information needed to configure the client to work with the UF Directory:

  • host:
  • port: 3700
  • database: NERDB0P
  • alias: BADBPROD (or whatever you want)
  • host:
  • port: 3700
  • database: NERDB0T
  • alias: BADBTEST (or whatever you want)

IBM DB2 manuals

From the Open Systems Group DB2 documentation site (

A DB2 Run-Time Client provides the functions to enable your applications to access DB2 Universal Database servers and DB2 Connect gateways. JDBC, SQLJ, ODBC and OLE DB are all supported by this client.

Hardware and software requirements (for Windows)

  • 16 MB RAM minimum
  • One of the following operating systems:
    • Microsoft Windows 95 4.00.950 or later
    • Microsoft Windows 98
    • Microsoft Windows NT Version 4.0 with Service Pack 4 or later
    • Microsoft Windows Terminal Server
    • Microsoft Windows 2000

Hardware and software requirements (for Linux)

  • Linux kernel 2.2.12 or higher
  • glibc Version 2.1.2 or higher
  • pdksh package (required to run the DB2 command line processor)
  • libstdc++ Version 2.9.0
  • rpm

Back to top

Option 2: Software access using Java APIs.

Classes contained in Production and Test versions of a Remote Client JAR files have been developed by the UF Identity Registry Project team. The appropriate jar file must be downloaded and placed in the appropriate classpath (e.g., JAVA_HOME/LIB/EXT). As the example code shown at “Using JAVA to call the Identifier Translate API (BAUli250)” (found on the Identity Registry Project Programming page) indicates, standard Java method calls are to be used for this access method. All connection and call details are handled automatically by the Identity Registry Java API. No additional software is required to use this resource.

Units taking this approach to working with the UF Identity Registry are responsible for developing software applications to maintain or update local database systems.

A typical process will involve using locally-authored software to obtain identifier data from a local database, calling the UF Identity Registry Java API, obtaining a result from the call, and then using or storing the corresponding identifier information.

This option may be useful in automating routine, repetitive processes.

Back to top