Connector Guides › Connector Xpress Guide › Creating Connectors › Managing Accounts and Groups › Account Class Mapping Example

Account Class Mapping Example

This example shows you the procedure you would follow if you were an administrator that wanted to map an account class for a JNDI data source. This example shows you how an administrator maps an endpoint's account class to the provisioning account class. This example assumes that the administrator has set up setup a JNDI data source.

To map an account class

1. On the Project menu, click New.

   Connector Xpress automatically creates a user account provisioning class node in the Mapping tree when you create a project.

   The Select Data Source for new project dialog appears.

2. Select the data source you want to use for the project.

   The Endpoint Types dialog appears.

3. On the Endpoint Type Details dialog, specify a name, description, and version for your connector.

   Note: These fields are for descriptive purposes only.

4. In the Mapping Tree, click the User Account node.

   The Mapped Class and Attributes dialog appears.

5. Select the endpoints type's object class that you want to map from the Add structural class list. For example, inetOrgPerson.
6. Map the endpoints mandatory attributes to the provisioning attributes in the Map Object Class Attribute mapping table. For example, cn and sn to Account ID and Last Name.

   Note: If the table list fails to populate when mapping tables, verify that your database does not have outstanding transactions or locks on the schema metadata.

7. Map any other required attributes, for example, the user password, street, and title.
8. Click the Classes node in the mapping tree.

   The Mapped Classes dialog displays a summary of the classes you have mapped. You can use this dialog to revise the native class to provisioning mappings you have made.

9. In the Mapping Tree, click the Account Id node under the Attribute node.

   The Attribute Details dialog appears.

   The dialog displays the LDAP attribute assigned to each field, its datatype, the JavaBean property name that JIAM uses, and whether the field is required (allows null values) and any length constraints.

10. Click the Last Name node under the Attributes node.

    The Attribute Details dialog appears with the default policy value set.

    Note: When you map a required attribute to a well-known provisioning attribute, Connector Xpress sets a default account template value by default.

11. Save the project.