It is not necessary to create JDBC attributes for the phone1
user_id and country1 id columns, because these
columns only contain the values that are present in EMPLOYEE.ID for
which an LDAP attribute uid is already created.

Create a JDBC object class for the LDAP person object
class.

In this step, the employee1 table is
identified as the primary table, and the country1 and phone1 tables are identified as secondary tables. The creation of
a JDBC object class also requires a DN. In this example, the DN is constructed
from the uid attribute and the base DN of the data view.