You can use the Concur connector for performing reconciliation and provisioning operations after configuring it to meet your requirements.
This chapter contains the following topics:
Note:
These sections provide both conceptual and procedural information about configuring the connector. It is recommended that you read the conceptual information before performing the procedures.
You can configure the connector to specify the type of reconciliation and its schedule.
This section provides details on the following topics related to configuring reconciliation:
Full reconciliation involves reconciling all existing user records from the target system into Oracle Identity Manager.
After you deploy the connector, you must first perform full reconciliation. To perform a full reconciliation run, ensure that no value is specified for the Filter attribute of the scheduled job for reconciling users. If the target system contains more number of records than what it can return in a single response, then use the Flat File connector to perform full reconciliation. For more information on reconciling large number of records, see Reconciling Large Number of Records.
You can perform limited reconciliation by creating filters for the reconciliation module, and reconcile records from the target system based on a specified filter criterion.
Limited or filtered reconciliation is the process of limiting the number of records being reconciled based on a set filter criteria. By default, all target system records that are added or modified after the last reconciliation run are reconciled during the current reconciliation run. You can customize this process by specifying the subset of added or modified target system records that must be reconciled.
This connector provides a Filter Suffix attribute (a scheduled task attribute) that allows you to use any of the attributes of the target system to filter target system records. You specify a value for the Filter Suffix attribute (for example, EmployeeID) while configuring the user reconciliation scheduled job.
Note:
If the target system contains more number of records than what it can return in a single response, then use the Flat File connector to perform limited reconciliation. See Reconciling Large Number of Records for more information.For more information on Concur filters, see information on user resources related to API Explorer on the Concur Developer Center page at https://developer.concur.com/.
During a reconciliation run, if the target system contains more number of records than what it can return in a single response, you can fetch all the records into Oracle Identity Manager using the Flat File connector. The Flat File connector consumes information in a flat file, and generates connector metadata using the metadata generation utility.
When you run the Connector Installer, reconciliation scheduled jobs are automatically created in Oracle Identity Manager. You must configure these scheduled jobs to suit your requirements by specifying values for its attributes.
The Concur User Reconciliation scheduled job is used to reconcile user account data from the target system in the target resource (account management) mode of the connector.
Table 3-1 describes the attributes of the scheduled job.
Table 3-1 Attributes of the Concur User Reconciliation Scheduled Job
Attribute | Description |
---|---|
Filter Suffix |
Enter the search filter for fetching user records from the target system during a reconciliation run. See Limited Reconciliation for the Concur Connector for more information. |
IT Resource Name |
Enter the name of the IT resource for the target system installation from which you want to reconcile user records. Default value: Concur |
Object Type |
This attribute holds the name of the object type for the reconciliation run. Default value: User Do not change the default value. |
Resource Object Name |
Name of the resource object against which reconciliation runs are performed. Default value: Concur User Do not change the default value. |
Configure scheduled jobs to perform reconciliation runs that check for new information on your target system periodically and replicates the data in Oracle Identity Manager.
These are the guidelines that you must apply while performing provisioning operations.
Ensure that you provision only one Concur account for an Oracle Identity Manager User.
During the Create User provisioning operation, if you want to assign a manager for the user, you must specify the Employee ID of the user that you want to assign as a manager in the Manager field.
While performing the Enable User, Disable User, or Reset Password provisioning operations for the first time for a Concur resource that is created in Oracle Identity Manager through a reconciliation run, ensure that values are populated for all the mandatory user fields in Oracle Identity Manager. If there are any user fields without values, then you must specify the values by performing the Update User provisioning operations.
You create a new user in Identity Self Service by using the Create User page. You provision or request for accounts on the Accounts tab of the User Details page.
See Also:
Creating a User in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Manager for details about the fields on the Create User pageUninstalling the concur connector deletes all the account related data associated with resource objects.
If you want to uninstall the connector for any reason, then run the Uninstall Connector utility. Before you run this utility, ensure that you set values for ObjectType
and ObjectValues
properties in the ConnectorUninstall.properties file. For example, if you want to delete resource objects, scheduled tasks, and scheduled jobs associated with the connector, then enter "ResourceObject", "ScheduleTask", "ScheduleJob" as the value of the ObjectType
property and a semicolon-separated list of object values corresponding to your connector as the value of the ObjectValues
property.
For example: Concur User
Note:
If you set values for theConnectorName
and Release
properties along with the ObjectType
and ObjectValue
properties, then the deletion of objects listed in the ObjectValues
property is performed by the utility and the Connector information is skipped.For more information, see Uninstalling Connectors in Oracle Fusion Middleware Administering Oracle Identity Governance.