Configuration

The inbound maps access static configuration information that is passed to it on the Config card. The data for the card is built from information in the Channel and the Value tables of FTM. The data looks similar to this example:

<?xml version="1.0" encoding="UTF-8"?>
<cfg:inboundCfg xmlns:cfg="http://www.ibm.com/xmlns/prod/ftm/MapConfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <msgTypeCfg>
      <class>OC_101</class>
      <subType>BC_101</subType>
      <bat>
         <class>OC_101</class>
         <subType>ST_101</subType>
      </bat>
      <pt>
         <class>OC_101</class>
         <subType>ST_101</subType>
      </pt>
      <type>FIN101</type>
   </msgTypeCfg>
   <msgTypeCfg>
      <class>OC_202</class>
      <subType>BC_202</subType>
      <pt>
         <class>OC_202</class>
         <subType>ST_202</subType>
      </pt>
      <type>FIN202</type>
   </msgTypeCfg>
   <msgTypeCfg>
      <class>OC_910</class>
      <subType>BC_910</subType>
      <type>FIN910</type>
   </msgTypeCfg>
   <defaultMsgTypeCfg>
      <class>OC_XXX</class>
      <subType>BC_XXX</subType>
      <bat>
         <class>OC_DEFAULT</class>
         <subType>ST_DEFAULT</subType>
      </bat>
      <pt>
         <class>OC_DEFAULT</class>
         <subType>ST_DEFAULT</subType>
      </pt>
   </defaultMsgTypeCfg>
   <extendedCfg>
      <name>MapExtPoints</name>
      <extendedCfg>
         <name>PreBodyMap</name>
         <value>MyPreMap</value>
      </extendedCfg>
      <extendedCfg>
         <name>PostBodyMap</name>
         <value>MyPostMap</value>
      </extendedCfg>
   </extendedCfg>
   <validationLevel>0</validationLevel>
   <mapFileExt>mmc</mapFileExt>
   <targetDomain>XMLNSC</targetDomain>
   <mappingContext>
      <newLevel>0</newLevel>
      <completeLevel>0</completeLevel>
   </mappingContext>
</cfg:inboundCfg>

The maps determine the MsgTypeCfg element to use by looking for the one whose type is equal to "FIN" concatenated with the message type of the SWIFT message being processed. If that can not be found, the defaultMsgTypeCfg element is used.

The following is a table of fields from the Config card that are used by the inbound mappers

Table 1. Config card fields used by inbound mappers
Config element	How used
subType	Assigned to business concept also assigned as the subtype for the transmission, batches and transactions.
class	Assigned as the obj_class for the transmission, batches, and transactions.
validationLevel	If the value is greater than two, the message is processed by the JVC.
mapFileExt	The file extensions that are appended to the maps when called. Normally the extensions should be aix, mmc, or mvs.
targetDomain	The output domain requested from the ISF message.

If there is a need to have different subType and obj_class for the transactions, batches, and transmissions, msgTypeCfg can be expanded to define one for each as shown:

<defaultMsgTypeCfg>
   <class>OC_XXX</class>
   <subType>BC_XXX</subType>
   <bat>
      <class>OC_DEFAULT</class>
      <subType>ST_DEFAULT</subType>
   </bat>
   <pt>
      <class>OC_DEFAULT</class>
      <subType>ST_DEFAULT</subType>
   </pt>
</defaultMsgTypeCfg>