Double click Create User to edit as illustrated in

Developing Identity Connectors 17-31 Following is the procedure to create a Provisioning Attribute Mapping Lookup. 1. Log in to the Oracle Identity Manager Design Console. 2. Click Lookup Definition under the Administration tab. 3. Create a new lookup and name it Lookup.FF.UM.ProvAttrMap. The name of this lookup is referred from the object type configuration lookup. See Section 17.2.2.3.2, Creating Object Type Configuration Lookup. 4. Add the form Field Labels as the code keys and identity connector bundle attributes as the decode. ■ Return ID : __UID__ ■ Account ID: AccountId ■ Change Number: ChangeNumber ■ First Name: FirstName ■ Last Name: LastName ■ Email ID: MailId

17.2.3.4.1 Field Flags Used in the Provisioning Attributes Map

For provisioning attributes mapping, the following field flags can be appended to the code key: ■ LOOKUP: This must be specified for all fields whose values are obtained by running a lookup reconciliation job. The values obtained from lookup reconciliation job have IT Resource NameKey appended to it. Specifying this flag helps ICF integration to remove the appended value just before passing them onto the bundle. For example, the code key for a field with label Database whose value is obtained by running a lookup reconciliation job looks similar to Database[LOOKUP]. ■ IGNORE: This must be specified for all fields whose values are to be ignored and not sent to bundle. For example, the code key for a field with label Database whose value need not be sent to bundle looks similar to Database[IGNORE]. ■ WRITEBACK: This must be specified for all fields whose values need to be written back into the process form right after the create or update operation. Adding this flag makes the ICF integration layer call ICF Get API to get values of attributes marked with the WRITEBACK flag. For example, the code key for a field with label Database whose value needs to be written back to the process form right after createupdate looks similar to Database[WRITEBACK]. For this to work, the connector must implement the GetApiOp interface and provide an implementation for the ConnectorObject getObjectObjectClass objClass,Uid uid,OperationOptions options API. This API searches the target for the account whose Uid is equal to the passed in Uid, and builds a connector object containing all the attributes and their values that are to be written back to process form. Note: The LOOKUP flag can be specified for both Provisioning and Reconciliation Attribute Map. For provisioning, IT Resource NameIT Resource Key prefix must be removed. For reconciliation, IT Resource NameIT Resource Key prefix must be added. 17-32 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager ■ DATE: This must be specified for fields whose type need to be considered as Date, without which the values are considered as normal strings. For example, the code key for a field with label Today whose value needs to be displayed in the date format looks similar to Today[DATE]. ■ PROVIDEONPSWDCHANGE: This must be specified for all fields that need to be provided to the bundletarget when a password update happens. Some targets expect additional attributes to be specified on every password change. Specifying the PROVIDEONPSWDCHANGE flag, tells ICF integration to send all the extra fields or attributes whenever a password change is requested. For example, the code key for a field with label Extra Attribute Needed for Password Change whose value needs to be provided to bundletarget while password update looks similar to Extra Attribute Needed for Password Change[PROVIDEONPSWDCHANGE].

17.2.4 Creating Reconciliation Metadata

This section contains the procedures to configure the reconciliation of records from the flat file. We will use the target reconciliation as an example; trusted reconciliation can also be configured in a similar fashion. Do the procedures in the listed order.

1. Creating a Reconciliation Schedule Task

2. Creating a Reconciliation Profile

3. Setting a Reconciliation Action Rule

4. Creating Reconciliation Mapping

5. Defining a Reconciliation Matching Rule

17.2.4.1 Creating a Reconciliation Schedule Task

By default, reconciliation uses a Search operation on the connector bundle. This operation is invoked with a schedule task configured using Oracle Identity Manager. This procedure is comprised of the following sub procedures. 1. Defining the Schedule Task 2. Creating a Scheduled Task

17.2.4.1.1 Defining the Schedule Task To define the scheduled task:

1. Create a Deployment Manager XML file containing the scheduled task details as shown in Example 17–9 . Make sure to update database value to your database. Example 17–9 Deployment Manager XML with Scheduled Task Details ?xml version = 1.0 encoding = UTF-8? xl-ddm-data version=2.0.1.0 user=XELSYSADM database=jdbc:oracle:thin:localhost:5524estView.regress.rdbms.dev.us.oracle.com exported-date=1307546406635 description=FF scheduledTask repo-type=MDS name=Flat File Connector User Reconciliation mds-path=db mds-file=Flat File Connector User Reconciliation.xml completeXml scheduledTasks xmlns=http:xmlns.oracle.comoimscheduler task Note: If the connector does not implement the GetApiOp interface, then the WRITEBACK flag does not work and an error is generated.