Configuring connected output terminals

You can configure additional properties for any output terminals that you connect to nodes when you want to override the default behavior.

You must configure the message domain. The domain that you use determines which message template properties, message set, message type, and message format, you need to configure. See Supported message domains. Configure the message template properties for the output terminals through the Outputs tab in the Properties view.

You must configure the Encoding and Coded Char Set ID properties. These properties must match the byte order (endianness) and character set of the output data from the map. Configure these properties for the output terminals through the Outputs tab in the Properties view. The values you need to use follow IBM Integration Bus conventions, described in the help topic about converting data with message flows in the IBM Integration Bus documentation.

If you do not configure these properties for an output terminal, IBM Transformation Extender for IBM Integration Bus uses the corresponding properties from the input tree. As an example, if the input belongs to the XMLNSC message domain, and you do not configure the message template properties for the output terminal, TX Map node creates the output message using the XMLNSC domain. If the message flow uses a Collector node, TX Map node creates the output message using the domain to which the tree on the first input message belongs.

When the Outputs tab initially opens, there are no entries in the Properties table. Add the properties for each of the connected output terminals. After you configure additional properties for a connected output terminal, the Properties table displays the card's number in the following format:

card-number

Examples are:

1 
2