TX Map node exceptions

When IBM® App Connect Enterprise runs your message flow that uses the TX Map node, and it fails, there are tools that you can use to troubleshoot the problem.

If any of the data that the TX Map node receives from an input message is missing or malformed, the node raises an exception.

If a Map Node failure terminal is connected to the message flow, IBM Sterling Transformation Extender for IBM App Connect Enterprise propagates the following information through the failure terminal when the Map node fails:
  • A message that contains NodeErrorInfo
  • The exception list
In addition, IBM App Connect Enterprise sends the original input message through the failure terminal as a separate message.

If the terminal is not connected, the exception is thrown back up the message flow, according to standard IBM App Connect Enterprise failure behavior.

If the TX Map node fails, IBM App Connect Enterprise logs the failure exception, including the standard error message, in the broker's event log and, optionally, trace files. For details about the standard error message, see the topic about problem determination.

Use the information that is in the IBM App Connect Enterprise log and trace files to help you troubleshoot the problem.

For information about IBM App Connect Enterprise logging and tracing mechanisms, see the IBM App Connect Enterprise product documentation.