3 Creating an Application for a Disconnected Resource By Using the Flat File Connector
Learn about onboarding applications for a disconnected resource by using the connector.
You can onboard an application for a disconnected resource into Oracle Identity Governance from the connector package by creating a Target application or an Authoritative application. To do so, you must log in to Identity Self Service and then choose the Applications box on the Manage tab.
3.1 Navigating to the Create Application Screen for a Disconnected Resource
To navigate to the Create Application screen, you must log in to Identity Self Service and then choose the Applications box on the Manage tab.
- Log in to Identity Self Service either by using the System Administration account or an account with the ApplicationInstanceAdministrator admin role.
- On the Applications page, click the Create menu on the toolbar, and then select one of the following options:
- Target - to create a Target application.
- Authoritative - to create an Authoritative application.
3.2 Providing Basic Information for a Disconnected Resource
You must provide configuration-related details on the Basic Information page. The connector uses these details while performing reconciliation.
3.3 Updating Schema Information for a Disconnected Resource
The Schema page for a Target or an Authoritative application displays the schema of your flat file with mappings with Oracle Identity Governance attributes and flat file attributes. The connector uses these mappings during reconciliation.
If you are creating a Target application, then the table on the Schema page lists the user-specific attribute mappings between the process form fields in Oracle Identity Governance and your flat file attributes. The table also lists the data type for a given attribute and specifies whether it is mandatory for reconciliation and whether it is a matching key field for fetching records during reconciliation. By default, the flat file attributes that were designated as Name and UID attributes in the Flat File Schema Properties table on the Basic Information page are marked as the matching key in the Key Field column on the Schema page.
The Schema page also displays the child attribute mappings for any complex multivalued attributes that you may have added to the Flat File Schema Properties table on the Basic Information page. You must ensure that you designate an attribute as the key field to be used for entity matching during reconciliation.
If you are creating an Authoritative application, then the table on the Schema page lists all the flat file attributes and their data types, and specifies whether a given attribute is a mandatory attribute for reconciliation. Note that this page does not list the user attribute mapping between the flat file attributes and reconciliation fields in Oracle Identity Governance. Therefore, you must map each flat file attribute listed in the Target Attribute column with the corresponding Oracle Identity Governance field in the Identity Display Name column.
Perform the following procedure on the Schema page:
- Review the user-specific attribute mappings and then in the Mandatory column, select or deselect the checkbox corresponding to an attribute to specify whether it is mandatory for reconciliation, if required.
- For any target system attribute of the Date data type that must be mapped to a String type attribute in Oracle Identity Governance, click the icon and select the Date checkbox.
- If you are creating a Target application, then in the child attribute mapping table:
- If you are creating an Authoritative application, then in the Identity Display Name column, enter the name of the OIG User form field to which a given flat file attribute in the Target Attribute column must be mapped to. Repeat this for all the attributes in the table.
- Click Next to proceed to the Settings page.
3.4 Providing Settings Information for a Disconnected Resource
Apart from reviewing the provisioning, reconciliation, and organization settings for your application and customizing them if required, you must specify values for the mandatory parameters of the reconciliation jobs.
The Settings page provides a preview of all settings related to provisioning, reconciliation, and organizations. You can review these settings and customize them if required. On the Reconciliation tab of the Settings page, expand the Reconciliation Jobs section to view the reconciliation jobs that the connector automatically creates after you create a Target or an Authoritative application. Ensure that you enter values for the mandatory parameters (marked by the asterisk (*) symbol) of all the reconciliation jobs and then click Next to proceed to the Finish page.
- Flat File Full
- Flat File Diff Sync
- Flat File Delete Sync
- Flat File Entitlement
Note:
The Flat File Entitlement reconciliation job is available if you are creating a Target application. - Flat File Delete
Flat File Full
The Flat File Accounts Loader reconciliation job is used for reconciling accounts from a flat file and creating corresponding accounts in Oracle Identity Governance.
Table 3-2 describes the parameters of the Flat File Accounts Loader reconciliation job.
Table 3-2 Parameters of the Flat File Accounts Loader
Parameter | Description |
---|---|
FlatFile Instance Name | This parameter holds the name of the application for your flat file. This value is the same as the value that you provided for the Application Name field while creating the flat file application. |
Flat File directory | Enter the name and complete path to the directory containing the flat file that the connector needs to parse.
Note: The OIG administrator must have read and write permissions on this directory. |
Archive directory |
Enter the name of the directory in which the processed flat files must be saved. If you do not specify a value for this attribute, the connector creates a directory named "archived" within the directory containing the flat file, and the processed files are saved in this location. Note: The OIG administrator must have read and write permissions on this directory to enable adding of the processed flat files to the archive directory. |
Filter | Enter the expression for filtering records that the scheduled job must reconcile.
Sample value: 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 flat file column that holds the time stamp at which the record was last modified. The value in this attribute is used during incremental reconciliation to determine the newest or latest record reconciled from the flat file. Sample value: |
Latest Token |
This parameter holds the value of the Incremental Recon Attribute. Note: The reconciliation engine automatically enters a value for this attribute after execution. It is recommended that you do not change the value of this attribute. If you manually specify a value for this attribute, then the connector reconciles only user accounts that have been modified after the time stamp specified as the value of this parameter. If you want to perform a full reconciliation run, then clear the value in this field. |
Scheduled Task Name |
This parameter holds the name of the scheduled job. Default value: APP_NAME Flat File Accounts Loader Here, APP_NAME is the Application Name you provided while creating the application. |
Flat File Diff Sync
The Flat File Accounts Diff Sync Reconciliation job is used for performing diff-based reconciliation.
-
Previous Flat File directory
This is the flat file containing all the accounts before delete.
-
Current Flat File directory
This is the flat file that is exported from the enterprise target system after accounts have been deleted in the enterprise target system.
When you run this reconciliation job, the connector will detect the accounts that are missing in the current flat file by comparing them with the accounts in the previous flat file, and will generate delete reconciliation events only for the missing accounts.
Table 3-3 describes the parameters of the Flat File Accounts Diff Sync Reconciliation job.
Table 3-3 Parameters of the Flat File Accounts Diff Sync Reconciliation Job
Parameter | Description |
---|---|
FlatFile Instance Name | This parameter holds the name of the application for your flat file. This value is the same as the value that you provided for the Application Name field while creating the flat file application. |
Previous Flat File directory |
Enter the name and complete path of the flat file directory that contains the records from the enterprise target system that were present previously. |
Current Flat File directory |
Enter the name and complete path of the flat file directory that contains the current records from the enterprise target system. |
Archive directory |
Enter the name of the directory in which the processed flat files must be saved. If you do not specify a value for this attribute, the connector creates a directory named "archived" within the directory containing the flat file, and the processed files are saved in this location. Note: The OIG administrator must have read and write permissions on this directory to enable adding of the processed flat files to the archive directory. |
Sync Token |
If you are using this reconciliation job for the first time, do not specify a value for this parameter. For subsequent runs, the reconciliation engine automatically enters a value for this parameter. Sample value: |
Scheduled Task Name |
This parameter holds the name of the scheduled job. Default value: APP_NAME Flat File Accounts Diff Sync Reconciliation Here, APP_NAME is the Application Name you provided while creating the application. |
Flat File Delete Sync
The Flat File Accounts Delete Sync Reconciliation job is used to perform a delete reconciliation run.
-
Delete Attribute
-
Delete Attribute Value
If you do not specify a value for the preceding attributes, then all the records in the flat file are considered as deleted records.
Table 3-4 describes the parameters of the Flat File Accounts Delete Sync Reconciliation job.
Table 3-4 Parameters of the Flat File Accounts Delete Sync Reconciliation Job
Parameter | Description |
---|---|
FlatFile Instance Name | This parameter holds the name of the application for your flat file. This value is the same as the value that you provided for the Application Name field while creating the flat file application. |
Flat File directory | Enter the name and complete path to the directory containing the flat file that the connector needs to parse.
Note: The OIG administrator must have read and write permissions on this directory. |
Archive directory |
Enter the name of the directory in which the processed flat files must be saved. If you do not specify a value for this attribute, the connector creates a directory named "archived" within the directory containing the flat file, and the processed files are saved in this location. Note: The OIG administrator must have read and write permissions on this directory to enable adding of the processed flat files to the archive directory. |
Delete Attribute |
Enter the name of the column in the flat file that represents whether an account is deleted or not. Enter a value for this attribute if you want to perform filtered delete reconciliation. Default value: None Sample value: |
Delete Attribute Value |
Enter the value that is mentioned in the column that specifies whether an account is deleted. This column is the value that you specified as the value of the Delete Attribute parameter. Sample value: |
Sync Token |
If you are using this schedule job for the first time, do not specify a value for this attribute. For subsequent runs, the reconciliation engine automatically enters a value for this attribute. Sample value: |
Scheduled Task Name |
This parameter holds the name of the scheduled job. Default value: APP_NAME Flat File Accounts Delete Sync Reconciliation Here, APP_NAME is the Application Name you provided while creating the application. |
Flat File Entitlement
The Flat File Entitlements Loader reconciliation job is used to reconcile both lookup values and entitlements from a flat file.
In addition to reconciling the lookups from a flat file, this reconciliation job also adds the entitlements for lookups that are associated with an Entitlement, and synchronizes the catalog with the entitlements automatically. The Flat File Entitlements Loader reconciliation job also supports full and incremental reconciliation of lookup values and entitlements.
Table 3-5 describes the parameters of the Flat File Entitlements Loader reconciliation job.
Table 3-5 Parameters of the Flat File Entitlements Loader Reconciliation Job
Parameter | Description |
---|---|
FlatFile Instance Name | This parameter holds the name of the application for your flat file. This value is the same as the value that you provided for the Application Name field while creating the flat file application. |
Flat File directory | Enter the name and complete path to the directory containing the flat file for your entitlements that the connector needs to parse.
Note: The OIG administrator must have read and write permissions on this directory. |
Archive directory |
Enter the name of the directory in which the processed flat files must be saved. If you do not specify a value for this attribute, the connector creates a directory named "archived" within the directory containing the flat file, and the processed files are saved in this location. Note: The OIG administrator must have read and write permissions on this directory to enable adding of the processed flat files to the archive directory. |
Lookup Name |
Enter the name of the lookup definition into which the connector must load all the values fetched from the flat file for entitlements. Note: The name of this lookup definition must be the same as the one that you specified on the Schema page for Entitlement lookup. Sample value: |
Code Key Attribute | Enter the name of the flat file attribute whose values you want to populate into the Code Key column the of lookup definition specified as the value of the Lookup Name parameter.
Default value: |
Decode Attribute | Enter the name of the flat file attribute whose values you want to populate into the Decode column of the lookup definition specified as the value of the Lookup Name parameter.
Default value: |
Mode | Enter the mode in which the job must run. The possible value for this parameter are:
Default value: |
Is Entitlement? |
Enter Enter This flag will decide if the ENT_LIST and Catalog should be updated with the lookup values. Default value: |
Flat File Delete
The Flat File Accounts Delete Reconciliation job is used to reconcile data about deleted accounts. During a reconciliation run, for each account deleted on the enterprise target system, the corresponding OIG account is deleted.
Use this reconciliation job if you cannot export flat files containing only a list of deleted accounts, but can periodically export flat files containing all accounts in the enterprise target system.
Note:
This process is resource consuming as Oracle Identity Governance has to verify all the records from the flat file and compare it with existing records to identify whether each record has been deleted or not.
Table 3-6 describes the parameters of the Flat File Accounts Delete Reconciliation job.
Table 3-6 Parameters of the Flat File Accounts Delete Reconciliation Job
Parameter | Description |
---|---|
FlatFile Instance Name | This parameter holds the name of the application for your flat file. This value is the same as the value that you provided for the Application Name field while creating the flat file application. |
Flat File directory | Enter the name and complete path to the directory containing the flat file that the connector needs to parse.
Note: The OIG administrator must have read and write permissions on this directory. |
Archive directory |
Enter the name of the directory in which the processed flat files must be saved. If you do not specify a value for this attribute, the connector creates a directory named "archived" within the directory containing the flat file, and the processed files are saved in this location. Note: The OIG administrator must have read and write permissions on this directory to enable adding of the processed flat files to the archive directory. |
3.5 Reviewing and Submitting the Application Details for a Disconnected Resource
On the Finish page, review your application summary and click Finish to submit the application.
On the Finish page, review the summary of the Target or Authoritative application you are creating. If required, click Back to make any changes to the application details. If no changes are required, click Finish to submit the application details. The application is created in Oracle Identity Governance.
When you are prompted whether you want to create a default request form, click Yes or No. If you click Yes, then the default form is automatically created and is attached with the newly created application. The default form is created with the same name as the application. You cannot modify the default form later. Therefore, if you want to customize it, click No to manually create a new form and attach it with your application.