Overview#

The Translation Processor is a part of the DirXML Engine that is responsible for converting information from the Identity Vault namespace (data format and schema structure/name) to the Connected Application, and vice versa.

Translation Processor

Translation Processor is independent of the Publisher Channel of Subscriber Channel.

Translation Processor part of the DirXML Engine and is the first and last processor before the Connected Application's shim.The DirXML Engine assumes that anything issued from within a driver channel is in XDS Document (ie Identity Vault namespace) format. For the Connected Application to understand what is being requested the event will need to be converted to the Connected Application format.

Conversely, any results from the Connected Application will need to be converted back to a XDS Document before it can be processed in the DirXML Engine

Everything (like Queries, DirXML commands, DirXML events) that goes to or comes from the Connected Application passes through Translation Processor.

All Items, other than those that originate in the Translation Processor, that go to the Connected Application will pass through:

• the Outbound Association Reference Processor
• the Schema Mapping Policy
• the Output Transformation Policy Set

All Items other than those that originate in the Translation Processor that come from the Connected Application will pass through:

• the Input Transformation Policy Set
• the Schema Mapping Policy
• the Inbound Association Reference Processor! DirXML Out-of-Band Requests

Generally, DirXML Out-of-Band Requests skip the Schema Mapping Policy

More Information#

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

• DirXML Engine
• Event Transformation Policy Set
• IDM Queries
• Notify and Reset Subscriber Filter
• Publisher Flow
• Subscriber Flow
• Translation Processor