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 AttributeTypes and ObjectClass Types) 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 XDS Documents sent to and returned from SubscriptionShim.execute, XmlQueryProcessor.query, and XmlCommandProcessor().execute(). The Schema Mapping Policy is also applied to XDS Documents sent to (but not to XML returned from) SubscriptionShim.init and PublicationShim().init().
The Schema Mapping Policy is applied before the Output Transformation Policy Set when DirXML Engine submits or returns a document to the DirXML Shim and before the Output Transformation Policy Set when the driver submits or returns a document to DirXML Engine.
The Identity Vault schema is read from eDirectory. The DirXML Shim for the Connected Application 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 Schema Mapping Policy are applied in both directions.
- All documents that are passed in either direction on either channel between the DirXML Engine and the Connected Application DirXML Shim are passed through the Schema Mapping Policy.
More Information#There might be more information for this subject on one of the following:
- DirXML Engine
- DirXML PolicySets
- Event Transformation Policy Set
- IDM Queries
- Input Transformation Policy Set
- Input-Output Transforms and Schema Mapping Policy
- Output Transformation Policy Set
- Policy Set Interval Values
- Translation Processor