Connector for CA Identity Manager › Configure the Connector for CA Identity Manager › Select Endpoints and Resources › Example: Two Types of Endpoint Handlers

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 CA 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>