CA Identity Manager Connector Guides › Connector Xpress Guide › Connector Xpress Utilities › Edit Metadata

Edit Metadata

You can edit the metadata for a project.

Important! Use the metadata editor at your own risk. Removing or altering important objects in the metadata can render it inoperable.

Follow these steps:

1. Open an existing project.
2. In the Provisioning Servers tree, right-click the endpoint type you want to edit the metadata for, then click Edit Metadata.

   The Edit Metadata for Endpoint Type dialog appears and displays the metadata in an XML tree.

3. Edit the metadata as required, then click Save.

   Connector Xpress redeploys the metadata.

Example: How an Administrator Modifies Metadata Manually

In this example, an administrator wants to change the display name mapping from last name to first name by manually modifying the metadata without using the mapping tree. The administrator:

1. Opens the dyn_jdbc_namespace.con project file.
2. Right-clicks the dyn_jdbc_namespace.con endpoint, then selects Edit Metadata.
3. Expands the dyn_jdbc_namespace node, and navigates to Classes, eTDYNAccount, Properties, eTDYN-str-01 in the Metadata Editor.
4. Modifies the displayName attribute from Last name to First name.
5. Modifies the beanPropertyName attribute from lastName to firstName.
6. Redeploys the modified metadata.
7. hecks that the changes have been made successfully by validating them in the Provisioning Manager.

More information:

Projects

Edit Metadata for Endpoint Type Dialog

Enumerated Values

For static enumerations, defining a new type involves:

• Creating a new unique type name
• Constructing a list of known values, each consisting of an internal value, and an optional display value

Note: Naming your new enum type int or integer does not cause any problems, however it can make maintenance of the metadata more difficult.

For query-based enumerations, define:

• A mapping to an unmanaged class
• The attributes the objects of that class have available for querying
• An association between a managed class and unmanaged class, through an appropriately chosen attribute in the former class

Metadata and Operations Bindings Editors Considerations

Important! You can use the Metadata editor to verify that the mappings you have made, however we recommend that you use the Metadata editor at your own risk. Removing or altering important objects in the metadata can render it inoperable.

Redeploy Metadata

When a connector project is open and metadata is available, you can push the metadata to the endpoint type on the Provisioning Server. You can only deploy metadata to dynamic endpoint types.

Note: If the endpoint type already has metadata, the new metadata cannot alter fundamental aspects of the data model such as adding attribute names or types.

Follow these steps:

1. Open an existing project.
2. In the Provisioning Servers tree, right-click the endpoint type you want to deploy data to, then click Deploy Metadata.

   The Deploy Metadata dialog appears.

3. Confirm that you want to deploy the metadata.

   Connector Xpress deploys the metadata to the selected endpoint type and overwrites any existing metadata.

More information:

Projects

DYN Schema Extensions

The DYN Schema has been extended for the following attributes:

• Container objects (eTDYNContainerXXX) are extended to 10.
• Generic objects (eTDYNObjectXXX) are extended to 35.
• All capability attributes (for example, eTDYN-str-multi-ic-, eTDYN-str-ic-, eTDYN-str-c-, eTDYN-bool-c-, eTDYN-int-multi-c-, eTDYN-int-c-) are extended to 99, with the exception of the multivalued case-sensitive attributes (eTDYN-str-multi-c-), which are extended to 500.
• The noncapability multivalued case-sensitive or case-insensitive attributes (for example, eTDYN-str-multi-, eTDYN-str-multi-i-) are extended to 500.
• The generic cached (that is, data location equals BOTH) multivalued case-sensitive attributes (eTDYN-str-multi-ca-) are extended to 99. These attributes are included in every DYN object.

  Cached attributes have their values stored on the provisioning server and are therefore accessible without contacting the endpoint system. Where their values are provided by the endpoint system, an explore operation is needed to update the values stored for them to match that on the endpoint system.

• Ninety-nine connection-specific cached multivalued case-sensitive attributes (eTDYN-str-multi-ca-sec-) are added for DYN Directory only. These attributes are added in the "encryptwith" line of the DYN password attribute, which can be used to obfuscate sensitive settings.

Metadata Descriptions

For more information about the metadata used in all layers of the architecture including Connector Xpress, JIAM, and CA IAM Connector Server, see the JavaDocs in the CA Identity Manager Bookshelf.

Using Connector Xpress as a Generic Metadata Editor

You can use Connector Xpress as a generic editor for non-JNDI or JDBC endpoint types. Using Connector Xpress as a generic editor lets you edit generic metadata that is not intended for a particular implementation bundle. For example, to edit metadata for the Scripting connector, create classes and attributes from the ground-up that are not mapped to a particular schema.

You can create and edit generic metadata in the following ways:

• Create new attributes, rather than selecting discovered attributes in the attribute mapping table.
• Load a set of predefined custom operational attributes from a predefined dictionary file.
• Load selected operational attributes from a predefined dictionary file.
• Load an extended set of metadata properties from a data file.

Create New Attributes

You can use Connector Xpress as an editor for generic metadata, and create new attributes, rather than selecting discovered attributes in the attribute mapping table. You can use this procedure to define compound type attributes or any other connector-specific attribute that is not mapped to an endpoint attribute.

Follow these steps:

1. Create a project, and when prompted to select a Data Source, select No source.

   The Endpoint Type Details dialog appears.

2. Complete the fields on the Endpoint Type Details dialog.
3. Expand the Classes node, then click the Attributes node of the class you want to map.

   The Map Attributes dialog appears.

4. In the Maps To field, type the name of the attribute you want to add.

   Connector Xpress adds the new attribute to the mapping tree.

5. Expand the Attributes node in the mapping tree, then click the new node for the attribute.

   The Attribute Details dialog appears.

6. Complete the fields on the Attribute Details dialog.

Display Extended Set of Metadata Properties

You can display an extended set of metadata properties on various dialogs.

To display extended set of metadata properties

1. Create a project, or open an existing project.
2. Click Tools, Preferences.

   The Connector Xpress Preferences dialog appears.

3. Select the Show Extended Metadata check box.

   Connector Xpress displays the extended metadata properties and contains all additional metadata that is relevant to this data model item.

   Note: For information about the fields displayed, see Extended Metadata Properties.

How you Load Operational Attributes

Connector Xpress does not automatically load operational attributes, however for JNDI endpoint types, you can load operational attributes using either of the following methods:

• Load a dictionary of custom operational attributes from a dictionary

  Each dictionary is based on a particular vendor or standard. You can select the following dictionaries:

  • CA Directory
  • RFC 2252
  • X.500
• Load a selected operational attribute to the list of all attributes of the selected structural native class.

Load Operational Attributes from a Dictionary

For JNDI endpoints, you can load a set of predefined custom operational attributes from a dictionary.

You can map operational attributes like other attributes.

Follow these steps:

1. Create a project, or open an existing project.
2. Click Project, Settings.

   The Edit Project Settings dialog appears.

3. Select the dictionary you want to load the operational attributes from, then click OK.
4. Click the Attributes node of the class you are mapping.

   The Map Attributes dialog appears.

5. Click the Edit icon to the right of the Maps to field.

   Connector Xpress displays the operational attributes in the Maps To list.

6. Map the operational attributes as required.

   Note: To load only some of the operational attributes, select the dictionary attribute you want to load from the list, then click the attribute you created in the mapping tree. Complete the fields on the Attribute Details dialog.