Programming Guides › Programming Guide for Java Connector Server › The Object Model › Metadata Definition › DYN Class Name Selection

DYN Class Name Selection

When manually assigning class names for a DYN endpoint type (rather than using Connector Xpress), consider the following:

• Use eTDYNDirectory for the top-level representation of the connector. Cached attributes (which have –ca- in their names), should typically be chosen to store values which are to connect to the endpoint system, so that the Provisioning Server stores them.
• Use eTDYNAccount for the representation of accounts on the endpoint system.
• Use eTDYNPolicy for the representation of the account templates used to create and manage accounts on the endpoint system. There is usually a strong correlation between the attributes in this class and those defined for eTDYNAccount, with the same attribute names doing double duty in both classes.
• Use eTDYNObjectXXX classes for native objects which are not accounts or containers. This includes live enumerations which are native objects which are not themselves managed (That is, they cannot be created or deleted) but are mapped so that clients can search for all instances. For example, the names of all native permissions configured on the endpoint system.
• eTDYNGroup can still be used instead of one of the eTDYNObjectXXX classes if you prefer.
• Use eTDYNContainerXXX for container native objects, which have the same attributes available for mapping as the eTDYNObjectXXX classes, but in addition can act as containers for them (and other containers). The list of classes permitted within a container is specified using the childTypes metadata setting.
• Configure eTDYNContainer, eTDYNAccountContainer, and eTDYNGroupContainer the same way as the eTDYNContainerXXX classes. You can use these classes if you prefer.