Configuring the Oracle EBS Employee Reconciliation Connector for an Authoritative Application

4 Configuring the Oracle EBS Employee Reconciliation Connector for an Authoritative Application

You must configure connection-related parameters that the connector uses to connect Oracle Identity Governance with your target system and perform connector operations. In addition, you can view and edit mappings between reconciliation fields in Oracle Identity Governance and target system columns, predefined correlation rules, situations and responses, and reconciliation jobs.

4.1 Basic Configuration Parameters for the EBS ER Connector

These are the connection-related parameters that Oracle Identity Governance requires to connect to your target system. These parameters are applicable for authoritative applications only.

Table 4-1 Parameters in the Basic Configuration Section for the EBS ER Connector

Parameter	Mandatory?	Description
Connection URL	Yes	Enter the database connection string using the `host:post:sid` syntax format. Default value: `jdbc:oracle:thin:@%h:%p:%d` See Determining Values for the JDBC URL and Connection Properties Parameters for more information about the supported JDBC URL formats and the value that you need to enter depending on the security measures that you have implemented.
User	Yes	Enter the user name of the target system account created while performing the Prerequisites for Creating an Application By Using Connector procedure. This user is used for various connector operations.
Password	Yes	Enter the password for the user name of the target system account to be used for connector operations.
Connector Server Name	No	If you are using a Connector Server, then enter the name of its IT resource.
Batch Size	No	Enter the number of records that the connector must include in each batch that it fetches from the target system during reconciliation. Default value: `1000`
Database	No	Enter the name of the target system database against which connector operations must be performed.
Host	No	Enter the host name or IP address where the database is running.
Include Future Hires	No	Specifies whether the connector must detect and reconcile records with future-dated Start Date values. If you set the value of this parameter to `true`, then the connector reconciles all employee records with future-dated start Date values. If you set the value of this parameter to `false`, then the connector does not reconcile employee records with future-dated Start Date values. Default value: `true`
Port	No	Enter the number of the port at which the target system database is listening.

4.2 Advanced Setting Parameters for the EBS ER Connector

These are the configuration-related entries that the connector uses during reconciliation and provisioning operations.

Table 4-2 Advanced Setting Parameters for the EBS ER Connector

Parameter	Mandatory?	Description
Bundle Version	Yes	This parameter hods the version of the connector bundle class. Value: `1.0.1116`
Connector Name	Yes	This parameter holds the name of the connector class. Value: `org.identityconnectors.ebs.EBSConnector`
Bundle Name	Yes	This parameter holds the name of the connector bundle package. Value: `org.identityconnectors.ebs`
Pool Max Idle	No	Enter the maximum number of idle objects in a pool. Default value: `10`
Pool Max Size	No	Enter the maximum number of connections that the pool can create. Default value: `10`
Pool Max Wait	No	Enter the maximum time, in milliseconds, the pool must wait for a free object to make itself available to be consumed for an operation. Default value: `150000`
Pool Min Evict Idle Time	No	Enter the minimum time, in milliseconds, the connector must wait before evicting an idle object. Default value: `120000`
Pool Min Idle	No	Enter the minimum number of idle objects in a pool. Default value: `1`
FilterDateAttributes	No	Enter the target system date attribute that the connector must use for filtering user records. If you want to enter more than one date attribute, then ensure to include them as a comma-separated list. Default value: `HIRE_DATE`
FilterDateAttributeFormat	No	Enter the format of the attribute specified as the value of the FilterDateAttributes parameter. Default value: `dd-MMM-yyyy`

4.3 Attribute Mappings for the EBS ER Connector

The Schema page for an Authoritative application displays the default schema (provided by the connector) that maps Oracle Identity Governance attributes to target system columns. The connector uses these mappings during reconciliation operations.

Table 4-3 lists the user-specific attribute mappings between the reconciliation fields in Oracle Identity Governance and target system columns. The table also lists the data type for a given attribute and specifies whether it is a mandatory attribute for reconciliation.

You may use the default schema that has been set for you or update and change it before continuing to the next step. You can edit the attributes mappings by adding new attributes or deleting existing attributes on the Schema page as described in Creating an Authoritative Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

The Organization Name, Xellerate Type, and Role identity attributes are mandatory fields on the OIG User form that cannot be left blank during reconciliation. As there are no corresponding attributes in the target system for the Organization Name, Xellerate Type, and Role identity attributes, they have been mapped to attributes in Oracle identity Governance. In addition, the connector provides default values (as listed in the “Default Value for Identity Display Name” column of Table 4-3) that it can use during reconciliation. For example, the default target attribute value for the Organization Name attribute is Xellerate Users. This implies that the connector reconciles all target system user accounts into the Xellerate Users organization in Oracle Identity Governance. Similarly, the default attribute value for Xellerate Type attribute is End-User, which implies that all reconciled user records are marked as end users.

Table 4-3 Oracle EBS HRMS Trusted User Account Schema Attributes

Identity Display Name	Target Attribute	Data Type	Mandatory Reconciliation Property?	Recon Field?	Default Value for Identity Display Name
Role	NA	String	No	Yes	Full-Time
National Identifier	NATIONAL_IDENTIFIER	String	No	Yes	NA
Business Group ID	BUSINESS_GROUP_ID	String	No	Yes	NA
First Name	FIRST_NAME	String	No	Yes	NA
PersonType	PERSON_TYPE_ID	String	No	Yes	NA
Supervisor Name	SUPERVISOR_NAME	String	No	Yes	NA
Nationality	NATIONALITY	String	No	Yes	NA
Supervisor ID	SUPERVISOR_ID	String	No	Yes	NA
Job	JOB	String	No	Yes	NA
Grade	GRADE	String	No	Yes	NA
Status	__ENABLE__	String	No	Yes	NA
Email	EMAIL_ADDRESS	String	No	Yes	NA
Xellerate Type	NA	String	No	Yes	End-User
End Date	ACTUAL_TERMINATION_DATE	Date	No	Yes	NA
User Login	__UID__	String	No	Yes	NA
Date Of Birth	DATE_OF_BIRTH	Date	No	Yes	NA
Title	TITLE	String	No	Yes	NA
Manager Login	SUPERVISOR_ID	String	No	No	NA
Start Date	HIRE_DATE	Date	No	Yes	NA
Organization Name	NA	String	No	Yes	Xellerate Users
Department	DEPARTMENT	String	No	Yes	NA
Last Name	LAST_NAME	String	No	Yes	NA
Person ID	PERSON_ID	String	No	Yes	NA
Marital Status	MARITAL_STATUS	String	No	Yes	NA

Figure 4-1 shows the default Oracle EBS HRMS Trusted User account attribute mappings.

Figure 4-1 Oracle EBS HRMS Trusted User Account Schema Attributes

Description of "Figure 4-1 Oracle EBS HRMS Trusted User Account Schema Attributes"

4.4 Correlation Rules for the EBS ER Connector

When you create an Authoritative application, the connector uses correlation rules to determine the identity that must be reconciled into Oracle Identity Governance.

Predefined Identity Correlation Rules

By default, the EBS ER connector provides a simple correlation rule when you create a Authoritative application. The connector uses this correlation rule to compare the entries in Oracle Identity Governance repository and the target system repository, determine the difference between the two repositories, and apply the latest changes to Oracle Identity Governance.

Table 4-4 lists the default simple correlation rule for an Oracle EBS HRMS Employee Reconciliation. If required, you can edit the default correlation rule or add new rules. You can create complex correlation rules also. For more information about adding or editing simple or complex correlation rules, see Updating Identity Correlation Rule in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 4-4 Predefined Identity Correlation Rule for an Authoritative Application

Target Attribute	Element Operator	Identity Attribute	Case Sensitive?
__UID__	Equals	User Login	No

In this identity rule:

__UID__ is a single-valued attribute on the target system that identifies the user account.
User Login is the field on the OIG User form.

Figure 4-2 shows the simple correlation rule for an Authoritative application.

Figure 4-2 Simple Correlation Rule for an Authoritative Application

Description of "Figure 4-2 Simple Correlation Rule for an Authoritative Application"

Predefined Situations and Responses

The EBS ER connector provides a default set of situations and responses when you create an Authoritative application. These situations and responses specify the action that Oracle Identity Governance must take based on the result of a reconciliation event.

Table 4-5 lists the default situations and responses for an Authoritative application. If required, you can edit these default situations and responses or add new ones. For more information about adding or editing situations and responses, see Updating Situations and Responses in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance

Table 4-5 Predefined Situations and Responses for an Authoritative Application

Situation	Response
No Matches Found	Create User
One Entity Match Found	Establish Link

Figure 4-3 shows the situations and responses for an Authoritative application that the connector provides by default.

Figure 4-3 Predefined Situations and Responses for an Authoritative Application

Description of "Figure 4-3 Predefined Situations and Responses for an Authoritative Application"

4.5 Reconciliation Jobs for the EBS ER Connector

These are the reconciliation jobs that are automatically created in Oracle Identity Governance after you create the application for your target system.

You can either use these predefined jobs or edit them to meet your requirements. Alternatively, you can create custom reconciliation jobs. For information about editing these predefined jobs or creating new ones, see Updating Reconciliation Jobs in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Full Reconciliation Job

The Oracle EBS HRMS Trusted User Reconciliation job is used to reconcile all person records for an authoritative application.

Table 4-6 Parameters of the Oracle EBS HRMS Trusted User Reconciliation Job

Parameter	Description
Application Name	Name of the application you created for your target system. This value is the same as the value that you provided for the Application Name field while creating your authoritative application. Do not modify this value.
Filter	Enter the expression for filtering records that the scheduled job must reconcile. Sample value: `equalTo('__UID__','10533')` For information about the filters expressions that you can create and use, see ICF Filter Syntax in Developing and Customizing Applications for Oracle Identity Governance.
Incremental Recon Attribute	Enter the name of the target system attribute that holds the timestamp at which the person record was modified. Sample value: `PERSON_UPDATED_DATE`
Object Type	Type of object you want to reconcile. Default value: `__PERSON__`
Latest Token	The parameter holds the value of the target system column that is specified as the value of the Incremental Recon Attribute parameter. The Latest Token parameter is used for internal purposes. By default, this value is empty. Note: Do not enter a value for this attribute. The reconciliation engine automatically enters a value in this attribute.
Scheduled Task Name	Name of the scheduled job that is used for reconciliation. Note: For the scheduled job included with this connector, you must not change the value of this attribute. However, if you create a new job or create a copy of the job, then enter the unique name for that scheduled job as the value of this attribute.

Incremental Reconciliation Job

The Oracle EBS HRMS Trusted Incremental User Reconciliation job is used for performing incremental reconciliation.

Table 4-7 Oracle EBS HRMS Trusted Incremental User Reconciliation Job

Parameter	Description
Application Name	Name of the application you created for your target system. This value is the same as the value that you provided for the Application Name field while creating your authoritative application. Do not modify this value.
Sync Token	This attribute must be left blank when you run incremental reconciliation for the first time. This ensures that data about all records from the target system are fetched into Oracle Identity Governance. After the first reconciliation run, the connector automatically enters a value for this attribute in an XML serialized format. From the next reconciliation run onward, only data about records that are modified since the last reconciliation run ended are fetched into Oracle Identity Governance.
Object Type	Type of object you want to reconcile. Default value: `__PERSON__`
Scheduled Task Name	Name of the scheduled job used for reconciliation. Note: For the scheduled job included with this connector, you must not change the value of this attribute. However, if you create a new job or create a copy of the job, then enter the unique name for that scheduled job as the value of this attribute.

Delete Reconciliation Job

The Oracle EBS HRMS Trusted User Delete Reconciliation job is used to reconcile data about deleted person records in the target system. During a reconciliation run, for each deleted user account on the target system, the corresponding OIG User is deleted.

Table 4-8 Oracle EBS HRMS Trusted User Delete Reconciliation Job

Parameter	Description
Application Name	Name of the application you created for your target system. This value is the same as the value that you provided for the Application Name field while creating your authoritative application. Do not modify this value.
Filter	Enter the expression for filtering deleted person records that the connector must reconcile. Sample value: `equalTo('__UID__','10533')` For information about the filters expressions that you can create and use, see ICF Filter Syntax in Developing and Customizing Applications for Oracle Identity Governance.
Object Type	Type of object you want to reconcile. Default value: `__PERSON__`
Search Type	Type of search operation to perform during reconciliation. Default value: `delete` Note: Do not modify this value.