5 Using the Concur Connector
You can use the Concur connector for performing reconciliation and provisioning operations after configuring it to meet your requirements.
5.1 Configuring Reconciliation
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:
5.1.1 Performing Full Reconciliation
Full reconciliation involves reconciling all existing user records from the target system into Oracle Identity Governance.
After you deploy the connector, you must first perform full reconciliation. To perform a full reconciliation run, ensure that a value is not specified for the Filter attribute of the Concur Target Resource User Reconciliation job for reconciling users. See Reconciliation Jobs for information about this reconciliation job.
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. See Reconciling Large Number of Records.
5.1.2 Performing Limited Reconciliation
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, primaryEmail=xyx@demo.com) while configuring the Concur Target Resource User Reconciliation job. See Reconciliation Jobs for information about this reconciliation 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 on Concur filters, see information on user resources related to API Explorer on the Concur Developer Center page at https://developer.concur.com/.
5.1.3 Reconciling Large Number of Records
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.
5.2 Configuring Reconciliation Jobs
Configure reconciliation jobs to perform reconciliation runs that check for new information on your target system periodically and replicates the data in Oracle Identity Governance.
You can apply this procedure to configure the reconciliation jobs for users and entitlements.
5.3 Configuring Provisioning
Learn about performing provisioning operations in Oracle Identity Governance and the guidelines that you must apply while performing these operations.
5.3.1 Guidelines on Performing Provisioning Operations
These are the guidelines that you must apply while performing provisioning operations.
-
Ensure that you provision only one Concur account for an Oracle Identity Governance 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 Governance through a reconciliation run, ensure that values are populated for all the mandatory user fields in Oracle Identity Governance. If there are any user fields without values, then you must specify the values by performing the Update User provisioning operations.
5.3.2 Performing 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.
To perform provisioning operations in Oracle Identity Governance:
- Log in to Identity Self Service.
- Create a user as follows:
- In Identity Self Service, click Manage. The Home tab displays the different Manage option. Click Users. The Manage Users page is displayed.
- From the Actions menu, select Create. Alternatively, you can click Create on the toolbar. The Create User page is displayed with input fields for user profile attributes.
- Enter details of the user in the Create User page.
- On the Account tab, click Request Accounts.
- In the Catalog page, search for and add to cart the application instance for the connector that you configured earlier, and then click Checkout.
- Specify value for fields in the application form and then click Ready to Submit.
- Click Submit.
See Also:
Creating a User in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance for details about the fields on the Create User page5.4 Uninstalling the Connector
Uninstalling 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.