Channel

Map configuration data is stored in the FTM database using a variation of the convention used by the existing Mapper Pack maps. A channel is related to a mapper. The channel may define a mapper configuration name. This configuration name refers to a category in the Value table (PARAM{CONFIG=name}), in which separate values can be grouped for the mapper. The example in the following figure is taken from the sample application for the LiquidityRequest channel. It shows the three distinct configuration parameters that are provided to the mapper when handling messages on this channel
Figure 1. Liquidity request channel
Liquidity request channel

For ITX integration, the static configuration data is stored in the VALUE table as fragments of XML.

The value table entries to XML schema mapping is based on key entries that start with names that match the XML elements (direct children of the root element). The following table shows examples from the previous XML samples.

Table 1. VALUE table config entries
KEY VALUE 
msgTypeCfg_<msg type>
 
<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>
 
defaultMsgTypeCfg
 
<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_1
 
<extendedCfg>
	<name>MapExtPoints</name>
	<extendedCfg>
		<name>PreMap</name>
		<value>MyPreMap</value>
	</extendedCfg>
	<extendedCfg>
		<name>PostMap</name>
		<value>MyPostMap</value>
	</extendedCfg>
</extendedCfg>
 
extendedCfg_2
 
<extendedCfg>
	<name>MapExtPoints</name>
	<extendedCfg>
		<name>PreMap</name>
		<value>MyPreMap </value>
	</extendedCfg>
	<extendedCfg>
		<name>PostMap</name>
		<value>MyPostMap </value>
	</extendedCfg>
</extendedCfg>
 
extendedCfg_SwiftEnv
 
<extendedCfg>
	<name>Swift</name>
	<extendedCfg>
		<name>SENDER</name>
		<value>BICXXXXXX</value>
	</extendedCfg>
	<extendedCfg>
		<name>RECEIVER</name>
		<value>BICXXXXXX</value>
	</extendedCfg>
	<extendedCfg>
		<name>PRIORITY</name>
		<value>S</value>
	</extendedCfg>
	<extendedCfg>
		<name>DEL_MON</name>
		<value>3</value>
	</extendedCfg>
	<extendedCfg>
		<name>OBS_PER</name>
		<value>nnn</value>
	</extendedCfg>
	<extendedCfg>
		<name>DIRECTION</name>
		<value>I</value>
	</extendedCfg>
</extendedCfg>

The integration flows will read all msgTypeCfg entries, the defaultTypeCfg entry, and the extendedCfg entries with a matching KEY and concatenates them together as one XML document to send to the ITX map. When integrating with a new ITX map using a new inbound or outbound message type, a new msgTypeCfg entry, extendedCfg entry, or both, is needed. The outbound map name is extracted from the msgTypeCfg for the message or, if not there, from the defaultTypeCfg. If the map name is missing from both, it defaults to the value specified in the VALUE table, where CATEGORY is the CHANNEL 'CONFIG' PARAM and the KEY is the batch or transaction type.