Construct an attribute. This action enables you to construct a virtual attribute that does not actually exist in the physical data source but is required by a client application. The action can also be used to alter an add or modify request to construct an attribute that is required by the physical data source.
To construct the attribute, use the add-attr transformation action.
Remove an attribute. This action enables you to delete an attribute from a client request if that attribute is not permitted by the schema on the physical data source. The action can also be used to remove an attribute from the response sent to a client application if the client application does not require that attribute.
To remove an attribute, use the remove-attr transformation action.
Construct an attribute value. This action enables you to create an attribute value from other attribute values.
To create an attribute value, use the add-attr-value transformation action.
Delete an attribute value. This action enables you to remove the value from an attribute. It is usually used to remove one or more values from a multi-valued attribute if either the client application or the data source schema does not permit multi-valued attributes.
To remove an attribute value, use the remove-attr-value transformation action.
Add a default value to an attribute. This action enables you to add a default value to an attribute, if no value exists.
To add a default value to an attribute, use the def-value transformation action.
Map one attribute value to another. This action enables you to have two different values for an attribute, depending on whether the attribute is being written to a data source or returned to a client application.
To map attribute values, use the attr-value-mapping transformation action, with the internal-value and view-value parameters.
Directory Proxy Server supports two ways of mapping attribute values — simple attribute mapping and mapping through a virtual transformation. In general, attribute mapping is simpler to configure and slightly better in terms of performance. For more information, see Renaming Attributes and DNs in Oracle Fusion Middleware Administration Guide for Oracle Directory Server Enterprise Edition.
The results of a transformation action depend on the transformation model.