Schema Mapping Policy


What does the Schema Mapping Policy do?[1][2]#

The Schema Mapping Policy applies to both the Subscriber channel and to the Publisher channel. The purpose of the Schema Mapping Policy is to map schema names (particularly attribute names and class names) between the Identity Vault namespace and the Application namespace. The default policy syntax is defined by the documentation for <attr-name-map>.

The Schema Mapping Policy uses the Policy Interval of 0.

The Schema Mapping Policy is applied to the XML documents sent to and returned from SubscriptionShim.execute, XmlQueryProcessor.query, and XmlCommandProcessor().execute(). The Schema Mapping Policy is also applied to XML sent to (but not to XML returned from) SubscriptionShim.init and PublicationShim().init().

The Schema Mapping Policy is applied before the Output Transformation Policy when Identity Manager submits or returns a document to the shim and before the Input Transformation Policy when the driver submits or returns a document to Identity Manager.

The Identity Vault schema is read from eDirectory. The Identity Manager driver for the connected system supplies the connected application’s schema. After the two schemas have been identified, a simple mapping is created between the Identity Vault and the target application.

After a Schema Mapping Policy is defined in the Identity Manager driver configuration, the corresponding data can be mapped.

It is important to note the following:

  • The same policies are applied in both directions.
  • All documents that are passed in either direction on either channel between the Metadirectory engine and the application shim are passed through the Schema Mapping policies.

Some of the concepts and even wording was taken from one or more of the following:

More Information#

There might be more information for this subject on one of the following: