33
Synchronization with Oracle Human Resources

If you store employee data in Oracle Internet Directory, and if you use Oracle Human Resources to create, modify, and delete that data, then you must ensure that the data is synchronized between the two. The Oracle Human Resources connector enables you to do this.

This chapter introduces the Oracle Human Resources connector and explains how to deploy it. It contains these topics:

• Introduction

• Data that You Can Import from Oracle Human Resources

• Managing Synchronization with Oracle Human Resources

Introduction

The Oracle Human Resources connector enables you to import a subset of employee data from Oracle Human Resources into Oracle Internet Directory. It is installed, with a default configuration, along with Oracle Internet Directory. It is ready to run out of the box.

You can schedule the Oracle Human Resources connector to run at any time, configuring it to extract incremental changes from the Oracle Human Resources system as often as every second. You can also set and modify attribute mapping between Oracle Human Resources and Oracle Internet Directory.

The Oracle Human Resources connector executable name is odihragent and is located in the $ORACLE_HOME/ldap/odi/bin directory. You can manage the Oracle Human Resources connector by using Oracle Directory Manager.

Data that You Can Import from Oracle Human Resources

Table 33-1 lists the tables in the Oracle Human Resources schema, most of whose attributes you can import into Oracle Internet Directory:

Table 33-1 Tables in Oracle Human Resources Schema

Table Name	Alias Used in the Connector Config Info Field
PER_PEOPLE_F	PER
PER_ADDRESSES	PA
PER_PERIOD_OF_ SERVICE	PPS
PER_PERSON_TYPE	PPT

All of these tables are visible if the login to the Oracle Human Resources database is done with the apps account.

Because attributes can be added or deleted at runtime from the configuration file, the Oracle Human Resources connector dynamically creates a SQL statement that selects and retrieves only the required attributes.

Table 33-2 shows some of the fields in the Oracle Human Resources user interface. These fields appear when you add or modify employee data.

Table 33-2 Fields in the Oracle Human Resources User Interface

ATTRIBUTE NAME	DESCRIPTION	FORM/CANVAS/FIELD_NAME
LAST_NAME	Last name of the person	People/Name/Last
FIRST_NAME	First name of the person	People/Name/First
TITLE	Title of the person	People/Name/Title
SUFFIX	Suffix--for example, Jr, Sr, Ph.D.	People/Name/Suffix
MIDDLE_NAME	Middle name	People/Name/Suffix
SEX	Sex	Gender List box
START_DATE	Hiring date	People/Hire Date
DATE_OF_BIRTH	Date of birth	People/Personal Information/Birth Date
MARITAL_STATUS	Marital status	People/Personal Information/Status
NATIONAL_ INDENTIFIER	Social security number for US residents	People/Identification/Social Security
EMPLOYEE_NUMBER	Employee number	People/Identification/Employee
REGISTERD_ DISABLED_ FLAG	Indicator that the employee has a disability	People/Personal Information/Has Disability
EMAIL_ADDRESS	Electronic mail address	People/Personal Information/EMail
OFFICE_NUMBER	Office location	People/Office Location Info/Office
MAILSTOP	Mail delivery stop	People/Office Location Info/Mail Stop
INTERNAL_LOCATION	Location	People/Office Location Info/Location
ADDRESS_LINE1		Personal Address Information/Address line 1
ADDRESS_LINE2		Personal Address Information/Address line 2
ADDRESS_LINE3		Personal Address Information/Address line 3
TOWN_OR_CITY		Personal Address Information/City
REGION_1		Personal Address Information/County
REGION_2		Personal Address Information/State
POSTAL_CODE		Personal Address Information/Zip Code
COUNTRY		Personal Address Information/Country
TELEPHONE_ NUMBER_1		Personal Address Information/Telephone
TELEPHONE_ NUMBER_2		Personal Address Information/Telephone2

Managing Synchronization with Oracle Human Resources

This section contains these topics:

• Configuring a Directory Integration Profile for the Oracle Human Resources Connector

• Customizing the List of Attributes to Be Synchronized with Oracle Internet Directory

• Customizing Mapping Rules for the Oracle Human Resources Connector

• Running Synchronization from Oracle Human Resources to Oracle Internet Directory

Configuring a Directory Integration Profile for the Oracle Human Resources Connector

To deploy the Oracle Human Resources connector, you must create a directory integration profile for it in Oracle Internet Directory. You can do this by using the procedures outlined in Chapter 30, "Oracle Directory Integration Server Administration". However, if you have a server installation--that is, a typical installation--then you can use the default integration profile that the Oracle Universal Installer created in the directory for you. A client-only installation does not include this integration profile.

The integration profile contains several attributes and attribute values. Table 33-3 lists these attributes by both their friendly names as used by Oracle Directory Manager--for example, Agent Name--and their actual names--for example, orclodipAgentName. It provides a description of each attribute, and, where appropriate, the default values in the Oracle Human Resources connector integration profile. Some cells in Table 33-3 contain italicized text providing information and instructions specific to the Oracle Human Resources connector.

Table 33-3 Attributes in the Oracle Human Resources Connector Integration Profile

Attribute	Description
General Information
Profile Name (orclODIPAgentName)	Unique name by which the connector is identified in the system, used as an RDN component of the DN that identifies the integration profile. The name can contain only alpha-numeric characters. This attribute is mandatory and not modifiable. The default name is OracleHRAgent.
Profile Status (orclODIPAgentcontrol)	Indicates whether the connector is enabled or disabled. Valid values are ENABLE or DISABLE. The default is DISABLE. This attribute is mandatory and modifiable. You must set this value to ENABLE.
Profile Password (orclODIPAgentPassword)	This is the password that the directory integration server uses to bind to Oracle Internet Directory on behalf of the profile. This attribute is mandatory and modifiable. Set this value to whatever password you want the Oracle Human Resources Profile to use.
Execution Host (orclODIPAgentHostName)	Host on which the connector runs. This attribute is mandatory and modifiable. This attribute is currently ignored.
Synchronization ModeorclODIPSynchronizationMode)	The direction of synchronization between Oracle Internet Directory and a connected directory. IMPORT indicates importing changes from a connected directory to Oracle Internet Directory. EXPORT indicates exporting changes from Oracle Internet Directory to a connected directory. The default is IMPORT. This attribute is mandatory and modifiable. Note: Oracle Internet Directory release 9.0.2 support import operations only, for the Oracle HR.
Scheduling Interval (orclODIPSchedulingInterval)	Time interval in seconds after which a connected directory is synchronized with Oracle Internet Directory. The default is 600. This attribute is mandatory and modifiable.
Max Number of Retries (orclODIPSyncRetryCount)	Maximum number of times the directory integration server would try to perform synchronization before giving up. It will then retry at the next scheduled time. The default is 5. This attribute is mandatory and modifiable.
Execution Information
Agent Execution Command (orclODIPAgentExeCommand)	Connector executable name and argument list used by the directory integration server to execute the connector. This attribute is mandatory and modifiable. The default is: odihragent connect=hrdb \ login=%orclodipConDirAccessAccount \ pass=%orclodipConDirAccessPassword \ date=%orclODIPLastSuccessfulExecutionTime \ You must set the value in the argument connect=hrdb to the connect string of the Oracle Human Resources system database.
Connected Directory Account (orclODIPConDirAccessAccount)	Valid user account in the Oracle Human Resources system that you want to access changes in the Oracle Human Resources system. This information is passed by the directory integration server to the connector in the command line at time of connector's invocation. This attribute is optional and modifiable.
Connected Directory Account Password (orclODIPConDirAccessPassword)	Password for the user account accessing the Oracle Human Resources system. It is passed by the Directory integration server to the connector at time of connector invocation. This attribute is optional and modifiable.
Additional Config Info (orclODIPAgentConfigInfo)	Any configuration information that you want an connector to store in Oracle Internet Directory. It is passed by the directory integration server to the connector at time of connector invocation. The information is stored as an attribute and the directory integration server does not have any knowledge of its content. The value stored in this attribute represents (for Oracle Human Resources connector) all attributes that need to be synchronized from Oracle Human Resources. It is discussed in "Customizing the List of Attributes to Be Synchronized with Oracle Internet Directory". This attribute is mandatory for Oracle Human Resources connector, and modifiable by editing the configuration file and uploading it again into the profile.
Interface Type (orclODIPInterfaceType)	The Interface being used for data transfer. Since it is in the form of a TAGGED file, it is set to `TAGGED'. Note: You should not modify this attribute for Oracle HR Profile.
Mapping Information
Mapping Rules (orclODIPAttributeMappingRules)	The mapping rules for mapping data between a connected directory and Oracle Internet Directory. The value stored in this attribute is discussed under "Mapping Rules". This attribute is mandatory for Oracle HR and modifiable.
Connected Directory Matching Filter (orclODIPConDirMatchingFilter)	This is not used in Oracle HR Connectivity.
OID Matching Filter (orclODIPOIDMatchingFilter)	This attribute names an LDAP filter that is used to search for a target entry in OID. The Server uses this filter to find out what kind of LDAP operation it needs to do to synchronize. It is of the form "employeenumber=%" It is optional and modifiable.
Status Information
Synchronization Status (orclODIPSynchronizationStatus)	Indicates the execution status of the profile as it is synchronizing. This is read-only.
Synchronization Errors (orclODIPSynchronizationErrors)	Error message for the last error encountered in synchronization. This is read-only.
Last Execution Time (orclODIPLastExecutionTime)	Time of the most recent profile execution. It is generally read-only. It can be modified to re-sync from a different point in time.
Last Successful Execution Time (orlcODIPLastSuccessfulExecutionTime)	Time of the most recent successful profile execution. It is generally read-only. It can be modified to re-sync from a different point in time.
Connected Directory Last Applied Change Number (orclODIPConDirLastAppliedChgNum)	This attribute, standard for all profiles, does not apply to the Oracle HR Synchronization.
OID Last Applied Change Number (orcllastappliedChangenumber)	This attribute, standard for all EXPORT profiles, does not apply to Oracle HR sync.

Customizing the List of Attributes to Be Synchronized with Oracle Internet Directory

You can customize the list of Oracle Human Resources attributes you want to synchronize with Oracle Internet Directory. To help you do this, Oracle Internet Directory includes a default list of Oracle Human Resources attributes to be synchronized. You can modify this list by including additional attributes in it, or excluding some from it.

The default attribute list is stored in the orclodipAgentConfigInfo attribute as part of the integration profile. The integration profile is loaded into Oracle Internet Directory as part of a typical installation. The list is also contained in the file named oraclehragent.cfg.master and is located under the $ORACLE_HOME/ldap/odi/conf directory.

Note: Do not modify the oraclehragent.cfg.master file; it serves as a backup.

The columns in the default list of Oracle Human Resources attributes are:

Column	Description
ATTRNAME	The output tag generated in the output data file
COLUMN_NAME	Database column name from where to obtain this value
TABLE_NAME	Database table name from where to obtain this value
FORMAT	The column data type of this attribute. (ASCII, NUMBER, DATE)
MAP	Indicator of whether to extract this attribute from Oracle Human Resources or not. A value of Y indicates that it will be extracted and a value of N indicates that it will not be.

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

Including 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 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. Include an additional Oracle Human Resources attribute for synchronization by adding a record to this file. To do this, you need this information:
   • Table name in the database from which the attribute value is to be extracted. These tables are listed in Table 33-1. The file uses abbreviated names for the four tables used in the synchronization.

   • Column name in the table

   • Column datatype. Valid values are ASCII, NUMBER, DATE

   You also need to assign an attribute name to the column name. This acts as the output tag by which this attribute is identified in the output file. This tag is also 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.

   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. See "Creating Oracle Human Resources Attribute Mapping Rules" for instructions about creating mapping rules.

3. Load the file into the orclodipAgentConfigInfo attribute by using the ldapmodify tool. The changes take effect the next time the connector runs.

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 hash sign (#) in front of it

   • Set the value of the column map to N

3. Load the file into the orclodipAgentConfigInfo attribute by using the ldapmodify tool. The changes take effect the next time the connector runs.

Configuring a SQL SELECT Statement in the Configuration File to Support Complex Selection Criteria

If the above supporting Attribute Configuration is not sufficient to extract data from the HR Database, then the Oracle Human Resources connector also supports execution of a pre-configured SQL SELECT statement in the configuration file. There is a TAG to indicate this in the config file, namely, a "[SELECT]" in the config file.

The following example shows a sample select statement to fetch some information from the HR database. Note that only the SQL statement should be below the [SELECT] Tag. The BINDVAR Bind Variable needs to be there to fetch incremental changes. The substitutes passes this value (the time stamp) to the Oracle Human Resources connector.

All the columns expressions fetched in the SELECT must have column names--for example, REPLACE(ppx.email_address),'@ORACLE.COM','') is fetched 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 REPLACE(ppx.email_address),'@ORACLE.COM'''.

[SELECT]

SELECT
     REPLACE(ppx.email_address),'@ORACLE.COM',''), EMAILADDRESS ,
     UPPER(ppx.attribute26) GUID,
     UPPER(ppx.last_name) LASTNAME,
     UPPER(ppx.first_name) FIRSTNAME,
     UPPER(ppx.middle_names) MIDDLENAME,
     UPPER(ppx.known_as) NICKNAME,
     UPPER(SUBSTR(ppx.date_of_birth,1,6)) BIRTHDAY,
     UPPER(ppx.employee_number) EMPLOYEEID,
     UPPER(ppos.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 UPPER(ppx.current_employee_flag) = 'Y'
  AND ppx.last_update_date >= (:BINDVAR,'YYYYMMDDHH24MISS')

Customizing Mapping Rules for the Oracle Human Resources Connector

Attribute mapping rules govern how the directory integration server converts attributes between Oracle Human Resources and Oracle Internet Directory. You can customize the mapping rules you want the directory integration server to use.

To help you do this, Oracle Internet Directory includes a default list of Oracle Human Resources mapping rules for the Oracle Human Resources system. You configure, modify, and delete mapping rules by editing this list.

The default list of mapping rules is stored in the orclodipAttributeMappingRules attribute in the integration profile. In addition, the rules are also in the file named oraclehragent.map.master located under the $ORACLE_HOME/ldap/odi/conf directory.

Note: Do not modify the oraclehragent.map.master file; it serves as a backup.

Default Oracle Human Resources Connector Mapping Rules

The oraclehragent.map.master file contains the following:

DomainRules
DomainRules
NONLDAP:dc=metaagt,dc=com:uid=%dc=metaagt,dc=com
AttributeRules
firstname: : : :cn: :person
email : : : :cn: :person: trunc(email,'@')
email : : : :uid: :person:trunc(email,'@')
firstname,lastname: : : :cn: :person: firstname+","+lastname
lastname,firstname: : : :cn: :person: lastname+","+firstname
firstname,lastname: : : :sn: :person: lastname | firstname
EmployeeNumber: : : :employeenumber: :inetOrgperson
EMail: : : :mail: :inetOrgperson
TelephoneNumber1: : : :telephonenumber: :person
TelephoneNumber2: : : :telephonenumber: :person
TelephoneNumber3: : : :telephonenumber: :person
Address1: : : :postaladdress: :person
state: : : :st: :locality
street1: : : :street: :locality
zip: : : :postalcode: :locality
town_or_city: : : :l: :locality
Title: : : :title: :organizationalperson
#Sex: : : :sex: :person

In the sample mapping file, `dc=metaagt,dc=com' is assumed as the `synchronization domain'. This domain name needs to be changed according to deployment requirements.

AttributeRules
firstname: : : :cn: :person
lastname: : : :sn: :person
lastname: : : :cn: :person
 : : : :cn: :person: trunc(email,'@')
 : : : :cn: :person: firstname+","+lastname
 : : : :cn: :person: lastname+","+firstname
EmployeeNumber: : : :employeenumber: :inetOrgperson
EMail: : : :mail: :inetOrgperson
TelephoneNumber1: : : :telephonenumber: :person
TelephoneNumber2: : : :telephonenumber: :person
TelephoneNumber3: : : :telephonenumber: :person
Address1: : : :postaladdress: :person
Address1: : : :postaladdress: :person
Address1: : : :postaladdress: :person
state: : : :st: :locality
street1: : : :street: :locality
zip: : : :postalcode: :locality
town_or_city: : : :l: :locality
Title: : : :title: :organizationalperson
Sex: : : :sex: :person
socialsecurity: : : :ssn: :person
country: : : :c: :country
BirthDate: : : :birthday: :organizationalperson
 : : : :userpassword: :person: "welcome"
changetype
###

The default mapping rules in the orclodipAttributeMappingRules attribute correspond to the default Oracle Human Resources attributes list in the orclodipAgentConfigInfo attribute. To establish mappings between Oracle Human Resources attributes and Oracle Internet Directory attributes, the mapping rules use the ATTRNAME column in each record of the Oracle Human Resources attributes list.

See Also: "Mapping Rules and Formats" for the description of the format of the mapping rules records

Creating Oracle Human Resources Attribute Mapping Rules

To create Oracle Human Resources attribute mapping rules, you modify the orclodipAttributeMappingRules attribute. To do this:

1. Copy the oraclehragent.map.master file to Agent_Name.map.

2. Add a new rule to this file by adding a record to it. To do this, you need this information:
   • The Oracle Human Resources attribute name that is mapped to Oracle Internet Directory

   • The corresponding attribute in Oracle Internet Directory and its object class to which the Oracle Human Resources attribute are to map

   • The import rule that determines how to map the Oracle Human Resources attribute to the Oracle Internet Directory attribute

3. Load the file into the orclodipAttributeMappingRules attribute by using the following script:
   $ORACLE_HOME/ldap/odi/admin/ldapUploadAgentFile.sh. The changes take effect the next time the profile runs.

   Note: To run shell script tools on the Windows operating system, you need one of the following UNIX emulation utilities: Cygwin 1.0. Visit: http://sources.redhat.com/cygwin/ MKS Toolkit 5.1 or 6.0. Visit: http://www.datafocus.com/products/

Modifying Oracle Human Resources Attribute Mapping Rules

To modify existing Oracle Human Resources attribute mapping rules, you modify the orclodipAttributeMappingRules attribute. To do this:

1. Copy the oraclehragent.map.master file Agent_Name.map.

2. Edit this file.

3. Load the file into the orclodipAttributeMappingRules attribute by using the ldapmodify tool. The changes take effect the next time the connector runs.

Deleting Oracle Human Resources Attribute Mapping Rules

To delete existing Oracle Human Resources attribute mapping rules, you modify the orclodipAttributeMappingRules attribute. To do this:

1. Copy the oraclehragent.map.master file and name it anything other than Agent_Name.map, which is reserved for use by the directory integration server.

2. Do one of the following:
   • Delete the rule from the file

   • Comment it out by putting a hash (#) sign in front of it.

3. Load the file into the orclodipAttributeMappingRules attribute by using the following script:
   $ORACLE_HOME/ldap/odi/admin/ldapUploadAgentFile.sh. The changes take effect the next time the profile runs.

   Note: To run shell script tools on the Windows operating system, you need one of the following UNIX emulation utilities: Cygwin 1.0. Visit: http://sources.redhat.com/cygwin/ MKS Toolkit 5.1 or 6.0. Visit: http://www.datafocus.com/products/

Running Synchronization from Oracle Human Resources to Oracle Internet Directory

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

During synchronization, the Oracle Directory Integration platform uses an import file. This file can contain a few or many changes that the Oracle Human Resources connector extracts from the Oracle Human Resources system.

This file is in the tagged format and acts as input to the Oracle directory server. It is named Oracle_HR_Agent_Name.data and is located in $ORACLE_HOME/ldap/odi/import.

You do not need to modify this file, but the last version of it is stored in the directory $ORACLE_HOME/ldap/odi/import/archive to help you with troubleshooting.

This is an example of an Oracle Human Resources change record in the import file:

FirstName: John
LastName: Liu
EmployeeNumber: 12345
Title: Mr.
Sex: M
MaritalStatus: Married
TelephoneNumber: 123-456-7891
Mail: Jliu@my_company.com
Address: 100 Jones Parkway
City: MyTown

Preparing for Synchronization

To prepare for synchronization between Oracle Human Resources and Oracle Internet Directory, follow these steps:

1. Ensure that the Oracle Human Resources connector and the directory integration server are installed on the host from which you want to run the Oracle Human Resources connector.

   See Also: The file install.txt and the Readme file for Oracle Internet Directory Release 9.0.2 for more details

2. Ensure that you have the information for accessing the Oracle Human Resources system, including:
   • Connect string to the Oracle Human Resources system database

   • Access account

   • Password

3. Ensure that the directory integration server on this host is registered in Oracle Internet Directory.

   See Also: "Registering the Oracle Directory Integration Server" for registration instructions

4. Configure an integration profile for the Oracle Human Resources connector, as described in "Configuring a Directory Integration Profile for the Oracle Human Resources Connector". Ensure that all values in the integration profile are properly set, including:
   • Oracle Human Resources attribute list

   • Oracle Human Resources attribute mapping rules

   • Scheduling interval

5. Once everything is properly set, set the orclodipAgentControl attribute to ENABLE. This indicates that the Oracle Human Resources connector is ready to run.

6. Start the Oracle directory server and the Oracle Human Resources system if they are not already running on the respective hosts.

7. When everything is ready, start the directory integration server if it is not already running on this host.

   See Also: "Managing the Oracle Directory Integration Server" for instructions about starting and stopping the directory integration server

The Synchronization Process

Once the Oracle Human Resources system, Oracle Internet Directory, and the directory integration server are running and the Oracle Human Resources connector is enabled, the directory integration server automatically starts synchronizing changes from the Oracle Human Resources system into Oracle Internet Directory. It follows this process:

1. Depending on the value specified in the `Last Execution Time' (orclodipLastExecutionTime) and the `scheduling interval' (orclodipschedulinginterval) the directory integration server invokes the `Oracle Human Resources Connector'.

2. The Human Resources Connector extracts all the changes from the Oracle Human Resources System based on the time specified in the orclodipLastSuccessfulExecutionTime attribute in the integration profile. It writes the changes into the Oracle Human Resources Import file, namely $ORACLE_HOME/ldap/odi/import/HR_Agent_Name.dat. It extracts only the attributes specified in the orclodipAgentConfigInfo attribute in the Integration Profile.

3. After the agent completes the execution, the directory integration server imports the changes to Oracle Internet Directory by doing the following:
   • It reads each change record from the import file.

   • It converts each change record into and LDAP change entry based on the rules specified in the `Mapping Rules' (orclodipAttributeMappingRules) in the Integration Profile.

4. After successfully importing all the changes successfully to Oracle Internet Directory, Oracle Human Resources Connector moves the import file to the archive directory, $ORACLE_HOME/ldap/odi/import/archive. The Status attributes Last Execution Time' (orclodipLastExecutionTime) and `Last Successful Execution Time' orclodipLastSuccessfulExecutionTime attributes to the current time.

5. If the import operation fails, only the `Last Execution Time' is updated, and the connector will once again attempt to extract the changes from Human Resources System based on the `Last Successful Execution Time'. The reason for failure will be logged in the trace file in $ORACLE_HOME/ldap/odi/HR_Agent_Name.trc file.

Boostrapping Oracle Internet Directory from Oracle HR

There are two ways to bootstrap Oracle Internet Directory from Oracle HR:

• Use the Oracle Human Resources connector. In the integration profile, set the orclodipConDirLastAppliedChgTime to a time before Oracle Human Resources was installed.

• Use external tools to migrate data from Oracle Human Resources into Oracle Internet Directory

  See Also: Chapter 32, "Bootstrapping of a Directory in the Oracle Directory Integration Platform" for further instructions about initial bootstrapping