Build mappers in IBM App Connect Enterprise

Depending on the version of FTM for High Value Payments, some additional mappers might be necessary to convert existing formats to and from ISF.

If these mappers are not available in IBM® App Connect Enterprise, new mapper subflows need to be built to meet the requirements for the High Value Payments project. For more information about mapper subflows and mapper containers, see Mappers.

Use the wrapper mapper flows to call any newly created mappers. Existing mappers that are provided with High Value Payments can be used as a template. For more information about wrapper mapper flows, see ISO message router mapper.

When the mappers are created, VALUE table entries that contain the following data need to be created.
  • The CATEGORY set equal to the channel param CONFIG.
  • The KEY that contains the msgTypeCfg keyword.
  • The configuration value with the XML that specifies the following elements.
    • <type>
    • <subType>
    • <class>
    • <extendedCfg> properties
    • <mapName>
These entries allow for greater flexibility for setting the subtype, class, and transaction properties in the database, based on the type of message.

The following figure shows an example of VALUE table entries that are created for existing mappers that are provided with High Value Payments.

Figure 1. FTM for High Value Payments mapper VALUE table config
This image shows configuration values. (fxtenvintimwmbbldmappersconfigib.png)