Programming Guides › Connector Programming Guide › The Object Model › Metadata Definition › Container Definition › Metadata Settings for a Real Container Class Example

Metadata Settings for a Real Container Class Example

The following is an example of important metadata settings for a real, that is, not virtual, container class. This example is from the metadata for the SDKFS sample, sdkfs_metadata.xml:

<class name="eTDYNContainer001">

	<metadata name="childTypes">
		<value>
		<setValue>
			<baseType>
				<strValue/>
						</baseType>
						<val>
							<strValue>eTDYNContainer001</strValue>
						</val>
						<val>
							<strValue>eTDYNAccount</strValue>
						</val>
						<val>
							<strValue>eTDYNObject001</strValue>
						</val>
					</setValue>
				</value>
			</metadata>
			<metadata name="connectorMapTo">
				<value>
					<strValue>folder</strValue>
				</value>
			</metadata>
			<property name="eTDYNContainer001Name">
				<value>
					<strValue>Container Name</strValue>
				</value>
				<metadata name="isNaming">
					<value>
						<boolValue>true</boolValue>
					</value>
				</metadata>
				<metadata name="isRequired">
					<value>
						<boolValue>true</boolValue>
					</value>
				</metadata>
				<metadata name="displayName">
					<value>
						<strValue>folder name</strValue>
					</value>
				</metadata>
				<metadata name="connectorMapTo">
					<value>
						<strValue>dirname</strValue>
					</value>
				</metadata>
			</property>
… arbitrary other properties can be mapped for the class…

</class>

The following settings in the above example are important to consider:

groupMappings / groupContents / displayName

These settings are required by the CA IdentityMinder and CA IdentityMinder Provisioning Manager user interfaces.

Value: As shown in the code example above.

isVirtual

Distinguishes virtual containers from real ones.

Value: true

childTypes

Specifies all classes in the datamodel that can be contained under this class (the class on which childTypes appears).

This setting is used the same way as for real containers. You can specify more than one class name, but each class can only appear in the childTypes setting for a single container. The values here also affect the searches done across the containers. Searches are optimized where possible to take only the classes that can exist under the container into account.

connectorMapToSame

Specifies that connectorMapTo values do not have to be provided for the class and its naming attribute (that is, their LDAP names are used). Note that these values are not important in a connector's implementation because the container is virtual and therefore does not exist on the endpoint.

Value: true

eTDYNContainer001Name

Specifies the container's name used by UI clients.

Value: SDK Groups

Note: For more information on real container examples involving ambiguous mappings, review some mappings generated for a JNDI endpoint by Connector Xpress.