EndMapper

Figure 1. EndMapper subflow for input mappers
EndInputMapperSubflow.jpg
The EndMapper subflow shown in the previous figure has the following main responsibilities:
  • Database persistence of all transactions and batches that have been successfully mapped into ISF.
  • Database persistence of all errors reported during mapping into ISF.
  • Raise mapper events. There are a number of events that the mapper will raise to:
    • indicate the objects that were successfully mapped
    • indicate where the mapping failed or was aborted for any reason
  • Return control to the main physical transmission flow to complete processing of the incoming physical transmission.
The EndMapper subflow has the following input terminals:
Table 1. EndMapper input terminals
Terminal Description
Input Legacy input terminal for original EndMapper (v1) implementation. ISF is propagated as OutputRoot. Other column persistence information passed on IBM® App Connect Enterprise Environment. Deprecated for single transaction mappings.
xmlnsc XMLNSC domain input for EndMapper (v2) implementation. ISF is propagated as part of an EndMapper document that includes all column persistence information, including ISF. Should be used where the mapping technology is providing a IBM App Connect Enterprise tree by default (for example, an ESQL map).
blob BLOB domain input for EndMapper (v2) implementation. ISF is propagated as part of an EndMapper document that includes all column persistence information including ISF. Should be used where the mapping technology is not providing a IBM App Connect Enterprise tree by default (for example, an XSLT or ITX map).
As shown in the previous table, the input terminal is the original, legacy input to EndMapper and is being deprecated for the following reasons:
  • Requires use of the IBM App Connect Enterprise Environment for data persistence API
  • Does not support nested batches
  • Does not easily support database extensibility
An alternative to the original EndMapper implementation is offered by the other two terminals. Both of these terminals provide the same functional support as each other, the difference is that a BLOB arriving from a blob mapper will be converted to XMLNSC domain using opaque parsing for ISF data elements for maximum efficiency. The main difference between EndMapper (v1) and EndMapper (v2) is that Mappers using EndMapper do not use the IBM App Connect Enterprise Environment to propagate persistence data but instead produce an EndMapper document. EndMapper (v2) is the strategic direction for inbound mappers and should be used for all new mappings.