Administration Guide › CA Role & Compliance Manager Integration › How to Configure Integration with CA RCM › How to Configure a Connection in CA RCM › Configure Field Mapping

Configure Field Mapping

Use the following procedure to define how the connector maps data fields between Identity Manager and CA RCM data structures.

To configure field mapping

1. On the system that hosts the CA RCM Client Tools, browse to the following directory:

   RCM_install\Client Tools\Software\Converters\CA\conf
   

   Note: RCM_install is the CA RCM installation directory.

2. Open the defaultMapping.xml file for editing.

   Note: The defaultMapping.xml file contains typical default settings. Copy and rename the defaultMapping.xml file to use these defaults as the basis for your customized file, or open a customized file, if you created one earlier.

   This file maps fields in CA RCM User, Role, and Resource data records to Identity Manager fields. The following elements and attributes are used in the file:

   KEYn

   Indicates a mandatory field of the CA RCM data record. Map a Identity Manager field to this field.

   FIELDn

   Indicates an optional field of the CA RCM data record. You may not have to map this field in some situations. For example, if there is no parallel Identity Manager field that is common to all the endpoints in the scope of the connector, you do not have to map a field.

   host

   Defines a field in the CA RCM universe configuration that the connector works with.

   guest

   Defines a field in the Identity Manager operating environment.

3. Edit the default mapping, as follows:
   • To change the mapping of a field, enter a new value for the guest attribute of a KEY or FIELD element.
   • To add a new field mapping, create a FIELD element, number it, and assign host and guest attributes.
   • To remove a field mapping, delete the corresponding FIELD element.

   Note: If you have a custom field mapped to an RCM date field in the Role section of the mapping file, the date format must be: dd/MM/yyyy HH:mm, for example, 31/12/2010 01:20.

4. Save changes to the file.