Administration Guide › CA Role & Compliance Manager Integration › How to Configure Integration with CA RCM › How to Configure a Connection in CA RCM › Select Endpoints and Resources

Select Endpoints and Resources

Identity Manager interacts with numerous endpoints in the enterprise environment. You define which endpoints you want to include in the scope of the connector, and the relevant user, role, and resource information for each endpoint.

The endpoint selection is stored in an XML file under the installation root directory of the connector.

To select endpoints and resources

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. Edit the endpointTypeMapping.xml file. Do one of the following:
   • Define endpoints using the customizable connector, as follows:
     1. Delete the XML comment signifiers <!-- and --> to activate the endpointtype element corresponding to the endpoint you want to include.

     Note: To create an entirely new endpointtype element, duplicate an existing

     element.

     1. Edit the XML attributes and child elements to reflect the endpoint type, endpoints, and resources you want to include in the connector.
     2. Repeat the previous process for each endpoint type you want to include in the connector.
   • Use predefined legacy endpoints by deleting the XML comment signifiers <!-- and --> to activate the endpointtype element corresponding to the type of endpoint you want to include.
3. Save changes to the file.

Example: Two Types of Endpoint Handlers

The following code in the default endpointTypeMapping.xml file shows the two types of endpointtype elements:

• Customizable connector template—this endpointtype element is configurable. You define the endpoints and resources included in the connector by editing the XML element, and assigning attribute values from the target Identity Manager data tree.

  <endpointtype name="Windows NT"
  

  handler="com.eurekify.connectors.ca.subconnectors.cst.CustomizableNsHandler"
  abbreviation="N16" default-policy-name="N16DefaultPolicy"
  policy-class="eTN16Policy" policy-name-attribute="eTN16PolicyName"
  policy-container-name-attribute="eTN16PolicyContainerName"
  policy-container-name="Windows NT Policies"
  >
  <endpoint name="*" fetch-policy="TRYFETCH"
  

  directory-class="eTN16Directory"
  directory-name-attribute="eTN16DirectoryName"
  account-class="eTN16Account"
  account-name-attribute="eTN16AccountName"
  default-policy-name="N16DefaultPolicy"
  ignore-problematic-policies="true"
  ignore-problematic-accounts="true"
  ignore-problematic-resource-types="true"
  >
  <resource description="NT Group"
  resource-class="eTN16Group"
  resource-name-attribute="eTN16GroupName"
  resource-referenced-attribute="eTN16GroupName"
  resource-appears-in-attribute="eTN16GroupMembers"
  ignore-problematic-resources="true">
  </resource>
  

  </endpoint>
  

  </endpointtype>
  

• Predefined endpoint handler—this endpointtype element references a hard-coded, Java-based endpoint handler. You cannot change the endpoints and resources that are included in the connector. This XML element is shorter than the customizable element.

  <endpointtype name="Windows NT"
  

  handler="com.eurekify.connectors.ca.subconnectors.n16.NtNsHandler">
  <endpoint name="*" fetch-policy="TRYFETCH"/>
  

  </endpointtype>