Previous Topic: Select Endpoints and Resources

Next Topic: endpointtype Element

The Customizable Connector Template

The customizable connector template uses an XML data structure to specify the endpoints you want to include in the scope of the connector, and the relevant user, role, and resource information for each endpoint. By editing this template with values from the target Identity Manager data tree, you can define which endpoints and resources the connector polls or updates.

Example: Define Included Endpoints

The following code in the endopintTypeMapping.xml file defines included resources for endpoints of type OS400. The endpoint mapping file typically contains several <endpointtype> declarations like this example, one for each endpoint type you want to include in the scope of the connector.

The <endpoint> child element lets you include specific endpoint instances of a certain type. Similarly, the <resource> child element lets you include only specific account and resource data from the parent endpoints.

<endpointtype 
name="OS400"
handler="com.eurekify.connectors.ca.subconnectors.cst.CustomizableNsHandler"
abbreviation="AS4" default-policy-name="OS400DefaultPolicy"
policy-class="eTAS4Policy" policy-name-attribute="eTAS4PolicyName"
policy-container-name-attribute="eTAS4PolicyContainerName"
policy-container-name="OS400 Policies"
>
<endpoint 
name="*" 
fetch-policy="TRYFETCH"
directory-class="eTAS4Directory"
directory-name-attribute="eTAS4DirectoryName"
account-class="eTAS4Account"
account-name-attribute="eTAS4UserProfileName"
default-policy-name="OS400DefaultPolicy"
ignore-problematic-policies="true"
ignore-problematic-accounts="true"
ignore-problematic-resource-types="true"
>
<resource 
 description="OS400 Group"
 resource-class="eTAS4Group"
 resource-name-attribute="eTAS4GroupName"
 resource-referenced-attribute="eTAS4AccountMembers"
 resource-appears-in-attribute="eTAS4GroupMembers"
 ignore-problematic-resources="true">
</resource>
</endpoint>
</endpointtype>