Programming Guides › Programming Guide for Java Connector Server › The Object Model › Metadata Definition › How You Define Metadata for a New Connector

How You Define Metadata for a New Connector

If you are creating a connector for which there is no pre-existing specialized schema, we recommend that you create a specialized data model mapping to and from the generic DYN schema. We recommend that you write metadata from scratch that annotates your LDAP schema with all the information required by the Java CS, the JIAM and CA Identity Management account management functionality.

The most critical metadata setting is connectorMapTo, which specifies the mappings for objectclasses and attributes to connectors. For example, in a JDBC-based connector, the account objectclass (defined using the class name=' XML syntax), is mapped to a database table and its properties are mapped to columns within its parent table.

Note: For more information, see the SDKDYN.

Some connectors can require the similar connectorMapToAmbiguous metadata property. For example, JNDI-based connectors can have an account which can have either of the naming attributes cn= or uid= on the endpoint.

Note: For an example of a hand-written metadata document, see the sample-home/conf/sdkdyn_metadata.xml file in the SDKDYN sample connector (ignoring metadata properties starting with pt.). For a list of supported metadata properties and values, see com.ca.commons.datamodel.MetaDataDefs in the Java CS Javadoc. com.ca.commons.datamodel.MetaDataDefs.