Linking Orphan Accounts Linking Reconciliation Events

1-14 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

1.2.6.3.1 For an Event With Multiple Matches When several users are matched to the event

data by the reconciliation engine, you must select the right user by using ad hoc or manual linking. For information about ad hoc linking, see Ad Hoc Linking on page 1-13. For information about manual linking, see Manual Linking on page 1-13.

1.2.6.3.2 For an Event With No Matches When no matches are found for an event, you

can either trigger an entity creation, or select an Oracle Identity Manager entity to link to the event. For information about how to select and Oracle Identity Manager entity to link to an event, see Ad Hoc Linking on page 1-13.

1.3 Updating Reconciliation Profiles Manually

This section describes creating and updating reconciliation profiles manually in the following sections: ■ Creating New Reconciliation Profiles ■ Updating Reconciliation Profiles ■ Changing the Profile Mode

1.3.1 Creating New Reconciliation Profiles

You might want to create reconciliation profiles in the following scenarios: ■ Creating Additional Nondefault Profiles for Reconciliation Based on Resource Objects ■ Creating New Profiles for Trusted Source Reconciliation

1.3.1.1 Creating Additional Nondefault Profiles for Reconciliation Based on Resource Objects

For reconciliation based on resource objects, the default profile name is the same as that of the resource object. For example, if resource object name is testresource, then the default profile name is also testresource. The corresponding reconciliation horizontal table name is RA_TESTRESOURCEobj_key. If the resource has Multi-Language Support MLS data, then the MLS table name is RA_MLS_TESTRESOURCEobj_key. If the resource object has child tables, then for each child form name, which is UD_xxx, there is a corresponding RA_UD_xx. Each of the tables has a corresponding entity definition XML file, which is stored as per platform documentation on MDS storage. Therefore, RA_MLS_TESTRESOURCEobj_key has an entity definition MDS document called dbRA_TESTRESOURCEobj_key.xml, which is stored as per platform documentation on MDS storage. To create nondefault profiles for reconciliation based on resource objects: Note: If you change the name of a resource object, the reconciliation profile needs to be regenerated by clicking the Create Reconciliation Profile button in the Object Reconciliation tab in Oracle Identity Manager Design Console. Managing Reconciliation Events 1-15 1. Create a copy of the exported profile XML file with a different name. 2. Make changes to the file to reflect the new profile name, horizontal table names, and new reconciliation field names and mappings. 3. Import the new profile to MDS by using the MDS import tool. 4. Copy the entity definition XML files with new names based on the new profile name. If the reconciliation field names also change, then change the XML files to refer to the new reconciliation field names. 5. Import the entity definition XML files to MDS by using the MDS import tool. 6. Create new horizontal tables in the database based on the new profile name.

1.3.1.2 Creating New Profiles for Trusted Source Reconciliation

The procedure for creating new profiles for trusted source reconciliation is similar to the procedure in Creating Additional Nondefault Profiles for Reconciliation Based on Resource Objects on page 1-14. The only difference is that trusted source reconciliation may or may not be associated with a resource object, and therefore, you can use the XML files corresponding to the LDAPUser profile as samples.

1.3.2 Updating Reconciliation Profiles

To change a property in a reconciliation profile, for instance batch size: 1. Export the dbPROFILE_NAME profile document from MDS. 2. Make changes in the XML file, for example, change the batch size value. 3. Import the updated profile into MDS by using the MDS import tool.

1.3.3 Changing the Profile Mode

You can use one of the following methods to change the profile mode property from CHANGELOG to REGULAR: ■ Change the value of the mode attribute in the profile, for example: generalconfig mode=REGULAR createEntityUsingSPFlag=true dateFormat=yyyyMMdd hh:mm:ss z ownerMatchingRuleWhereClause= UGP.ugp_ldap_guid=RA_SAMPLE_HIERARCHY.RECON_ROLE_GUID entitytype=RoleRole version=1.0 trustedSrcFlag=false Note: You can export or import files to MDS by using the MDS exportimport utility, which is run by running the weblogicExportMetadata.sh and weblogicImportMetadata.sh scripts. For information about running these scripts, see MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager. See Also: Mode of Reconciliation in the Oracle Fusion Middleware Users Guide for Oracle Identity Manager for information about changelog and regular reconciliation modes