Preparing the Additional Configuration Information File

Synchronizing with Relational Database Tables 9-5 ■ The name of the table is Employee ■ The Profile Name is TESTDBIMPORT. ■ The employee number EMPNO is used to join a database record with a directory entry. It is specified in the OID Matching Filter orclOdipOIDMatchingFilter attribute described in the attributes reference chapter of the Oracle Identity Management User Reference. ■ This table is present in the testsynctestsyncpwd schema in a database. The database is located on the host machine.acme.com, the database listener port is 1526, and the SID is iasdb. The database URL is machine.acme.com:1526:iasdb. ■ Appropriate readwrite permissions were given explicitly to this profile, namely, orclodipagentname=testdbimport, cn=subscriber profile, cn=changelog subscriber, cn=oracle internet directory ■ The profile is created in configuration set 1.

9.4.1 Configuring the Additional Configuration Information File

This example uses the same Additional Configuration Information file described earlier in Preparing the Additional Configuration Information File on page 9-2.

9.4.2 Configuring the Mapping File

The mapping file for this example contains the following: DomainRules NONLDAP:dc=testdbsync,dc=com:uid=,dc=testdbsync,dc=com AttributeRules ename: : : :cn: :person ename : : : :sn: :person uid : : : :uid: :inetOrgperson: EMail: : : :mail: :inetOrgperson Telephone: : : :telephonenumber: :inetOrgperson empnum: : : :employeenumber: :inetOrgperson This mapping file specifies the following: ■ Directory entries are created as uid=,dc=testdbsync,dc=com. The percent sign is a placeholder for the actual value of uid. The uid must be present in the mapping rules so that it has a value after the mapping. Otherwise, the DN construction fails. ■ Both the cn and sn attributes need to have the same value as ename. ■ The uid element must have the value of the EMail prefix, which is the element of the e-mail address prior to the at sign character. ■ The empnum attribute becomes employeenumber in the directory entry. ■ The telephone attributes becomes telephone number in the directory entry.

9.4.3 Configuring the Directory Integration Profile

The directory integration profile for this example contains the attribute values as described in Table 9–1 on page 9-6. A sample integration profile with these values populated and the corresponding mapping and configuration files are available in 9-6 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform ORACLE_HOMEldapodiconf directory. You can create the profile by using Oracle Enterprise Manager Fusion Middleware Control or following the instructions described in Creating Synchronization Profiles on page 7-1.

9.4.4 Uploading the Additional Configuration Information and Mapping Files

Use the update operation of the manageSyncProfiles command to update the additional configuration information and mapping files, as follows: Table 9–1 Directory Integration Profile for TESTDBIMPORT Attribute Value Profile Name odip.profile.name TESTDBIMPORT Synchronization Mode odip.profile.syncmode IMPORT Profile Status odip.profile.status ENABLE Agent Execution Command odip.profile.agentexecommand null Advanced Configuration Information odip.profile.configfile Maintains configuration details which are not individually maintained in LDAP attributes. Connected Directory Account odip.profile.condiraccount testdbsync Connected Directory Account Password odip.profile.condirpassword testdbsyncpwd Connected Directory URL odip.profile.condirurl machine.acme.com:1526:iasdb Interface Type odip.profile.interface DB Mapping File odip.profile.mapfile Attribute for storing mapping rules. OID Matching Filter odip.profile.oidfilter employeenumber This means that employeenumber is used to search the directory while looking for a match. If a match is found, then the directory entry is modified. Otherwise, a new entry is created. This is necessary to ensure that the orclOdipOIDMatchingFilter attribute is unique in the database also. Once a database row is retrieved, the Oracle Directory Integration Platform searches the directory for that employeenumber in the domain dc=testdbsync,dc=com according to the domain rules. If it gets a match, it updates that entry with the latest values of the columns in the row retrieved. If it does not get a match, it creates a new entry in the directory with all the attributes from the column values. Last Applied Change Number odip.profile.lastchgnum 20000101000000 This means that the first time the profile executes, it retrieves and synchronizes all four rows. Subsequently, it retrieves rows only when the LAST_UPDATE_DATE column in the table is updated to the time last modified.