The following fields are displayed on Connector Xpress dialogs when you select the Show extended set of metadata properties on the Connector Xpress Preferences dialog.
Connector Xpress displays the fields on the following dialogs:
Note: Not all fields are displayed on all dialogs.
Targets any indirect association property. Alternate key used to name the parent class of the target property that is, not the referenced class.
Defines a relationship from an obj type to a referenced obj type, where a direct association through an attribute and an indirect association through a table external to both object types are supported.
Targets any direct association property, names attribute in the referenced class (that is, not the parent of target property) which contains association information in the reverse direction.
Targets any indirect association property, names table which stores association links.
Targets any indirect association property, specifies column in table named in ${MD_ASSOC_TABLE} which contains references to class which is parent of target property.
Targets any indirect association property, specifies column in table named in ${MD_ASSOC_TABLE} which contains references to referenced class (that is, not the parent class of target property).
When true specifies that target attribute specifies an association between a parent object and its compound value child objects.
Specifies how to handle attempts to override generated attribute values in LDAP ADD requests.
Generator name (or literal expression passed to the endpoint if surrounded in \"s) which specifies the value assigned to the property
Example: \'my_sequence\' or \'\"NEXT VALUE FOR my_sequence\"\' for JDBC.
Specifies which name to map an object class (including the connector itself) or attribute to in connector-speak. For a dynamic connector, this attribute specifies the name of the native system item to map the attribute to. For example, a JDBC-based connector would probably map an object class to the name of a database table, and each property within it to the name of one of its columns.
Specifies which name to map an objectclass (including the connector itself) or attribute to in connector-speak. For example, where MD_CONN_MAP_TO is mapped to a complicated expression and therefore does not act as a useful reference name in the connector's code.
Specifies the rare cases where a single LDAP attribute ambiguously maps to more the one connector objectclass or attribute. The order of the choices is important, as the first choice is the default when no explicit choice is made and a new object is created.
Specifies that an attribute with ambiguous mappings can optionally name another LDAP attribute which is used to pass in an explicit choice when new instances of the objectclass are add()ed
Identifies all auxiliary classes by name to which mappings are present.
Identifies all structural classes by name to which mappings are present with any classes that each of them derives from.
Specifies that MD_CONN_MAP_TO mappings are lax. The Boolean can appear on any objectclass which has MD_CONN_MAP_TO specified.
Specifies multiple connector-speak classes or attributes. Used when you need to split a single LDAP class or attribute into multiple connector-speak attributes, or compose it from the values of multiple connector-speak attributes.
Specifies that all properties defined for this attribute will use their LDAP names literally as their connector-speak names. This attribute appears on an object class which does not have MD_CONN_MAP_TO specified. Object classes without either MD_CONN_MAP_TO or this attribute are skipped.
Causes the framework to augment objectclass filters to include an explicit check for the existence of a particular connector-speak naming attribute. This is used in cases where the naming attribute is potentially ambiguous, but you have chosen to map only one choice.
Contains dynamic version of connector.xml configuration used for all connectors on this namespace.
Identifies all structural classes by name to which mappings are present with any classes that each of them derives from.
(Optional) Specifies the default value for the attribute.
Note: Only clients use this value (for example, user interfaces). If the client does not supply a value, the Provisioning Server does not use it by default.
Defines the name of connector implementation targeted by the connector type.
If selected, specifies that that the target class exists to define the format of values accepted by a compound or structured attribute.
Distinguishes connection-related attributes on the connector.
Specifies that the value for property is generated implicitly by the endpoint (For example, true for IDENTITY column in JDBC).
Specifies that the attribute is marked as interesting to CA Role and Compliance Manager. For example, an attribute of an account object marked as interesting to compliance is available to CA Role and Compliance Manager as a resource for analysis. Typically these attributes signify the assignment of a permission or entitlement on the endpoint system.
Specifies that the value for the property is not displayed in GUIs.
Specifies whether the attribute is the LDAP naming attribute.
Specifies whether the target property is operational (that is, calculated by the native endpoint rather then persisted).
Specifies whether the property is read-only on the endpoint system.
(DB2 IBM i only) Controls whether transactions are used when performing operations (for example, Add, Delete, Modify) on a JDBC endpoint. Applicable where transactions cannot be used for DB2 for IBM i database tables that are not journaled.
Specifies whether this property is recognized as a member of the common set.
(Read only) Defines the value for the name of the object within the metadata XML. For classes and attributes, this is usually the LDAP provisioning name.
Flags the target property as computed rather than persisted.
|
Copyright © 2013 CA.
All rights reserved.
|
|