Compartir a través de


Define Object Types

For this procedure, in Management Agent Designer, on the Define Object Types page, you can define the object types included in the template input file. You can also define an anchor attribute for each object type and specify which attributes are required for the object type. To complete this procedure, you must be logged on as a member of the FIMSyncAdmins security group.

To define object types

  1. In Management Agent Designer, on the Define Object Types page, in Object types, click an available object type, and then in Attributes, confirm the available attributes for the selected object. Verify that at least one attribute, selected as the anchor attribute, is marked as Yes in the Must Have column.

  2. To configure additional object type properties, in Object types, click an available object type, click Edit, and then do any of the following:

    • If there is more than one object type and you want to configure an anchor attribute for each object type, select the Define anchor attribute for this object type check box, and then, in Select anchor attribute, click an anchor attribute for the object type. If the template input file contains a hierarchical distinguished name attribute, select the Use distinguished name as anchor attribute check box.

    • To require that an attribute be present in all synchronizations of the selected object, in Select mandatory attributes, in Available attributes, click the attribute that you want to require, and then click the Add button to the left of Must have attributes. To remove an attribute from Must have attributes, click Remove.

    • To include an attribute that can be present in all synchronizations of the selected object, in Select mandatory attributes, in Available attributes, click the attribute you want to require, and then click the Add button to the left of May have attributes. To remove an attribute from May have attributes, click Remove.

Note

The Must have attribute property is not enforced, however this property is required when validating an object against the schema, for example, validating an object for export.

See Also

Concepts

Connected Data Sources and Management Agents
Map Object Types
Using Management Agents