Configuration

The outbound 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:outboundCfg 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>
		<mapName>My101Map</mapName>
		<type>FIN101</type>
	</msgTypeCfg>
	<msgTypeCfg>
		<class>OC_202</class>
		<subType>BC_202</subType>
		<mapName>My202Map</mapName>
		<type>FIN202</type>
	</msgTypeCfg>
	<msgTypeCfg>
		<class>OC_910</class>
		<subType>BC_910</subType>
		<mapName>My910Map</mapName>
		<type>FIN910</type>
	</msgTypeCfg>
	<extendedCfg>
		<name>MapExtPoints</name>
		<extendedCfg>
			<name>PreBodyMap</name>
			<value>MyPreMap</value>
		</extendedCfg>
		<extendedCfg>
			<name>PostBodyMap</name>
			<value>MyPostMap</value>
		</extendedCfg>
	</extendedCfg>
	<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>
			<name>TXN_ROOT</name>
			<value>xpath like expression or equivalent</value>
		</extendedCfg>
	</extendedCfg>
	<validationLevel>0</validationLevel>
	<mapFileExt>mmc</mapFileExt>
	<targetDomain>XMLNSC</targetDomain>
</cfg:outboundCfg>

The outbound integration flow determines the correct map to call and passes the configuration data to the mapper. The following is a table of fields from the Config card that are used by the outbound mappers

Table 1. Config card fields used by outbound mappers
Config Element	How Used
SENDER entry from the extendedCfg	The value to assign as the sender of the message if one can not be determined from the ISF record
RECEIVER entry from the extendedCfg	The value to assign as the receiver of the message if one can not be determined from the ISF record
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