Task 1: Configure a Directory Integration Profile for the Oracle Human Resources Connector

10-6 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform The oraclehragent.cfg.master file contains the following: ATTRNAME:COLUMN_NAME:TABLE_NAME:FORMAT:MAP PersonId:person_id:PER:NUMBER:Y PersonType:person_type_id:PER:NUMBER:Y PersonTypeName:system_person_type:PPT:ASCII:Y LastName:last_name:PER:ASCII:Y StartDate:start_date:PER:DATE:Y BirthDate:date_of_birth:PER:DATE:Y EMail:email_address:PER:ASCII:Y EmployeeNumber:employee_number:PER:NUMBER:Y FirstName:first_name:PER:ASCII:Y FullName:full_name:PER:ASCII:Y knownas:known_as:PER:ASCII:Y MaritalStatus:marital_status:PER:ASCII:Y middleName:middle_names:PER:ASCII:Y country:country:PA:ASCII:Y socialsecurity:national_identifier:PER:ASCII:Y Sex:sex:PER:ASCII:Y Title:title:PER:ASCII:Y suffix:suffix:PER:ASCII:Y street1:address_line1:PA:ASCII:Y zip:postal_code:PA:ASCII:Y Address1:address_line1:PA:ASCII:Y Address2:address_line2:PA:ASCII:Y Address3:address_line3:PA:ASCII:Y TelephoneNumber1:telephone_number_1:PA:ASCII:Y TelephoneNumber2:telephone_number_2:PA:ASCII:Y TelephoneNumber3:telephone_number_3:PA:ASCII:Y town_or_city:town_or_city:PA:ASCII:Y state:region_2:PA:ASCII:Y Start_date:effective_start_date:PER:DATE:Y End_date:effective_end_date:PER:DATE:Y per_updateTime:last_update_date:PER:DATE:Y pa_updateTime:last_update_date:PA:DATE:Y

10.3.2.1 Modifying Additional Oracle Human Resources Attributes for Synchronization

To include additional Oracle Human Resources attributes for synchronization, follow these steps: 1. Copy the oraclehragent.cfg.master file and name it anything other than Agent_ Name.cfg. This is because the Oracle Directory Integration Platform generates a configuration file with that name, using it to pass the configuration information to the Oracle Human Resources agent at run time. 2. Include an additional Oracle Human Resources attribute for synchronization by adding a record to this file. To do this, you need this information: FORMAT The column data type of this attribute ASCII, NUMBER, DATE. MAP Indicator of whether to extract this attribute from Oracle Human Resources. A value of Y indicates that it will be extracted, and a value of N indicates that it will not be. Table 10–4 Cont. Oracle Human Resources Attributes Synchronized with Oracle Internet Directory by Default Column Description Synchronizing with Oracle Human Resources 10-7 ■ Table name in the database from which the attribute value is to be extracted. These tables are listed in Table 10–1 on page 10-2. The file uses abbreviated names for the four tables used in the synchronization. ■ Column name in the table. ■ Column data type. Valid values are ASCII, NUMBER, and DATE. You also need to assign an attribute name to the column name. This acts as the output tag that is used to identify this attribute in the output file. This tag is used in the mapping rules to establish a rule between the Oracle Human Resources attribute and the Oracle Internet Directory attribute. You must also ensure that the map column—that is, the last column in the record—is set to the value Y.

10.3.2.2 Excluding Oracle Human Resources Attributes from Synchronization

To exclude an Oracle Human Resources attribute that is currently being synchronized with Oracle Internet Directory:

1. Copy the oraclehragent.cfg.master file and name it anything other than Agent_

Name.cfg. This is because the directory integration server generates a configuration file with that name, using it to pass the configuration information to the Oracle Human Resources connector at run time.

2. Do one of the following:

■ Comment out the corresponding record in the attribute list by putting a number sign in front of it. ■ Set the value of the column map to N. 10.3.2.3 Configuring a SQL SELECT Statement in the Configuration File to Support Complex Selection Criteria If the previous supporting attribute configuration is not sufficient to extract data from the Oracle Human Resources database, then the Oracle Human Resources agent can also execute a preconfigured SQL SELECT statement in the configuration file. There is a tag to indicate this in the configuration file, namely, a [SELECT] in the configuration file. The following example shows a sample select statement to retrieve some information from the Oracle Human Resources database. Note that only the SQL statement should follow the [SELECT] tag. The BINDVAR bind variable needs to be there to retrieve incremental changes. The substitutes passes this value the time stamp to the Oracle Human Resources connector. All the column expressions retrieved in the SELECT statement must have column names—for example, REPLACEppx.email_address,ORACLE.COM, is retrieved as EMAILADDRESS. The Oracle Human Resources connector writes out EMAILADDRESS as the attribute name in the output file with its value as the result of the expression REPLACEppx.email_address,ORACLE.COM. Note: If you add a new attribute in the attribute list, then you must define a corresponding rule in the orclodipAttributeMappingRules attribute. Otherwise the Oracle Human Resources attribute is not synchronized with the Oracle Internet Directory even if it is being extracted by the Oracle Human Resources connector. 10-8 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform The following is an example of a a SELECT statement in a configuration file. [SELECT] SELECT REPLACEppx.email_address,ORACLE.COM, EMAILADDRESS , UPPERppx.attribute26 GUID, UPPERppx.last_name LASTNAME, UPPERppx.first_name FIRSTNAME, UPPERppx.middle_names MIDDLENAME, UPPERppx.known_as NICKNAME, UPPERSUBSTRppx.date_of_birth,1,6 BIRTHDAY, UPPERppx.employee_number EMPLOYEEID, UPPERppos.date_start HIREDATE FROM hr_organization_units hou, per_people_x ppx, per_people_x mppx, per_periods_of_service ppos WHERE pax.supervisor_id = mppx.person_id+ AND pax.organization_id = hou.organization_id+ AND ppx.person_id = ppos.person_id AND ppx.person_id = pax.person_id AND ppos.actual_termination_date IS NULL AND UPPERppx.current_employee_flag = Y AND ppx.last_update_date = :BINDVAR,’YYYYMMDDHH24MISS’

10.3.3 Task 3: Configure Mapping Rules for the Oracle Human Resources Connector

Attribute mapping rules govern how the Oracle Directory Integration Platform converts attributes between Oracle Human Resources and Oracle Internet Directory. You can customize the mapping rules you want the Oracle Directory Integration Platform to use. The Oracle Human Resources agent profile has a default mapping file with a set of mapping rules in the attribute orclodipAttributeMappingRules. This information is also stored in the file named oraclehragent.map.master located under the ORACLE_HOMEldapodiconf directory.

10.3.4 Task 4: Prepare to Synchronize from Oracle Human Resources to Oracle Internet Directory

This section explains how to set up synchronization from Oracle Human Resources to Oracle Internet Directory.

10.3.4.1 Preparing for Synchronization

To prepare for synchronization between Oracle Human Resources and Oracle Internet Directory, follow these steps: Note: Do not modify the oraclehragent.map.master file. It serves as a backup. See Also: Mapping rules and formats on page 5-2 for the contents of the oraclehragent.map.master file and a description of the format of the mapping rules records