Connector Guides › Connector Xpress Guide › Screens and Dialogs › Map Compound Class and Attributes Dialog (JDBC)

Map Compound Class and Attributes Dialog (JDBC)

The Map Compound Class and Attributes dialog (JDBC) lets you create a Compound type class that you can use to you provide multi-table support for JDBC connectors.

Every class mapping that you create must be associated with exactly one database table.

This dialog contains the following fields:

• Name

  Defines the name of the class you are mapping.

  Limits: Must begin with a letter.

• Description

  Describes the class you are mapping.

• Managed

  If unchecked, marks this class as mapped only for the purpose of establishing associations. As a result, Connector Xpress only maps its name and type. Instances of an unmanaged class can be listed and associated with other objects, but cannot be created, edited or deleted.

  For compound classes, Connector Xpress selects this field by default, and cannot be cleared.

• Schema (Mandatory)

  Specifies the schema (for example, tablespace or database) name for the tables displayed in the Table list.

• Table (Mandatory)

  Specifies the table that represents account/group information in the selected schema.

  You must associate every class mapping that you create with exactly one database table.

• Map Columns

  Displays an overview of the column mappings you have selected.

  Note: This table does not show the full set of mapping options. For more rarely used options, expand the class node to display individual attribute detail nodes.

• Native Name

  Displays the name of the native attribute.

  Bold entries indicate mandatory entries that you must map at least once per class.

  The naming attribute of the class in question is displayed in bold.

• Native Type

  Specifies the data-model type depending on the SQL type for the JDBC case.

• Native Size

  Displays the size of the Account/Group Table column in characters.

  Note: In some cases this value is a "best guess", such as for NVARCHARS or storage of time-related values in vendor-specific formats.

• Name

  Lists the provisioning attributes you can map to the native attribute.

  • Italic entries

    Indicate that the attribute has already been mapped. For JNDI, these attributes can be mapped again.

  • Bold entries

    Indicate mandatory entries that you must map at least once per class.

  • Custom attributes

    Indicate that the attribute is given a default name based on its native attribute name. You can modify this attribute in the Provisioning Attribute Details dialog.

  • Blank entry

    Lets you remove a mapping.

  Note: For account classes, this list also displays the list of well-known attributes.

• Type

  Specifies the data-model type depending on the SQL type for the JDBC case.

  • Binary Data

    Defines an attribute whose value is arbitrary binary data.

  • Boolean

    Specifies logically true or false in XML, but represented by the Provisioning Server and JIAM APIs as 1 or 0 in LDAP attribute values.

  • Date

    Specifies a date.

    Example: 1999-05-31

  Note: The Dynamic Namespace plug-in to Provisioning Manager supports the years from 1800 through 9999, but other components of the solution impose no such restrictions and can represent virtually any year in recorded history.

  • Date & Time

    Specifies a particular time on a particular day.

    Example: 1999-05-31T13:20:00

  Note: The Dynamic Namespace plug-in to Provisioning Manager supports the years from 1970 through 2036, so you must use Date to represent days falling outside of this range.

  Note: Vendor differences complicate how Connector Xpress handles time-related columns. For example, MSSQL "DATETIME" signifies a DateTime value whereas other vendors use the standard "TIMESTAMP", and MSSQL TIMESTAMPs are automatically generated binary values. Also, Oracle does not support a "TIME" type and its "DATE" type is also effectively a TIMESTAMP. Therefore, to remain vendor-neutral, Connector Xpress allows you to map to any of Date/DateTime/Time whenever it makes sense for you to do so.

  • Double-precision floating-point

    Specifies a double-precision 64-bit floating-point value.

  • Enumeration - enumeration type name

    Specifies an attribute with a fixed list of enumerated values.

  • Flexi-DN

    Specifies a distinguished name string format.

    For example, "cn=Bob,ou=Sales,o=ExampleCorp". The connector enforces this.

  • Flexi-Email

    Specifies an email address string format.

  • Flexi-Quoteless

    Specifies that quotes are removed from attribute values.

  • Floating Point

  Specifies a single-precision 32-bit floating-point number.

  • Integer

    Specifies a 32-bit value between -2147483648 and 2147483647.

  • Long Integer

    Specifies a 64-bit value from 9223372036854775808 through 9223372036854775807.

  • String

    Specifies an unrestricted field.

  • Time

    Specifies an offset of between 0 seconds and 23:59:59.

    Example: 13:20:00

• Multi-valued

  If selected, specifies that this attribute is multi-valued.

  Note: If the native attribute is multi-valued, Connector Xpress automatically selects this check box. If the native attribute is single-valued, this option is cleared and read-only.

• Extended Properties

  Displays an extended set of metadata properties. These fields are displayed when you select the select the Show extended set of metadata properties on the Connector Xpress Preferences dialog.

  Note: For more information, see Extended Properties.