Previous Topic: How you Create a Connector Xpress ProjectNext Topic: Template Locations

Connector Guides › Connector Xpress Guide › Creating Connectors › Projects › Templates

Templates

You can use a template as a starting point for mapping common endpoint schemas. For example, starting a project with a template is useful for LDAP, where standards such as RFCs define widely used schemas, and purely custom schemas are less common. Templates also include information that CA IdentityMinder uses to render account management screens.

The following table highlights some of the more commonly used templates. For a full list of all templates, select Project, Create New from Template in Connector Xpress, then click on each template for a brief description.

Important! To help ensure correct performance, we recommend that you use the vendor-specific template supplied with Connector Xpress as a starting point when you create a mapping for a specific vendor.

Project Name Setting

Endpoint type

Description

Metadata File Name

JNDI NIS NetGroup

JNDI

For use with LDAP endpoints supporting NIS Netgroup Schema. This template demonstrates advanced association handling.

jndi_assoc_nisnetgroup_metadata

JNDI inetOrgPerson (Common)

JNDI

LDAP inetOrgPerson. This template should be used when no vendor-specific template is required.

jndi_inetorgperson_common_metadata

Lotus Notes Domino

JNDI

Lotus Notes Domino Server. This template allows easy mapping of eTLNDCustomAttribute* and eTLNDCustomCapabilityAttribute* attributes (the latter set are relevant for account template synchronization).

lnd_metadata

SDK DYN Compound

Any

Like SDKDYN but demonstrates use of Compound Values. This template uses compound values which allow complex data to be represented as a single string in JSON syntax, for instance '{"attr1": 42, "attr2": [ "a", "b" ], attr3: { "objName" : "jack" } }' represents a top level object with three attributes, the first is an integer (42), the next is an array of strings and the last a nested object.

sdkcompound_metadata

SDK DYN

Any

Software Development Kit demo connector. This template is a flat (i.e. non-hierarchical) case-sensitive connector that uses the recommended eTDYN* schema to save provisioning information to local files on the CA IAM CS host computer. Because it is flat, its containers are Virtual Containers not actually stored on the endpoint.

sdkdyn_metadata

SDK DYN Script

Any

Like SDKDYN but implemented in Java Script. This template demonstrates how to implement an entire connector (all operation bindings) in JavaScript, as well as configuration information usually found in a connector.xml file, using the connectorXML metadata setting on the top-level namespace.

sdkscript_metadata

SDK DYN UPO Script

Any

Like SDK DYN Script but sends emails rather than writing to local files. This connector has similar functionality to the deprecated C++ UPO connector except that it sends emails rather than writing information to local files.

sdkuposcript_metadata