IBM Transformation Extender map failures

As a result of running a map, if the audit log map settings are set to ON, IBM Transformation Extender writes information about the map run, including the map return codes and messages, to the log file. For the list of all the return codes and messages, see the topic about error and warning messages that is in the IBM Transformation Extender Map Designer documentation.

If the trace map settings are set to ON, IBM Transformation Extender writes the map run steps to the trace file. For information about the trace file, see the specific topics in the IBM Transformation Extender Map Designer documentation.

All log and trace entries include time stamps.

By default, IBM Transformation Extender generates unique log and trace file names at run time, equivalent to when you use the Unique setting for the log and trace file names. You can also select the Custom setting to specify a custom file name and location.

If you specified Use external map in the TX Map node, IBM Transformation Extender creates the log and trace files with the same names and in the same directory locations as specified in the external map.

If you specified Use map from project in the TX Map node, and selected Default for the audit log or trace file name map setting, IBM Transformation Extender creates the log file as map_name.log, and the trace file as map_name.mtr, where map_name is the name of the executable map. If you selected Default for Directory, which specifies the audit log or trace file location, IBM Transformation Extender creates the files in the IBM Integration Bus's deployment directory.

Use the information that is in the IBM Transformation Extender log and trace files to help you troubleshoot the problem.

For information about the log and trace files, and troubleshooting maps, see the IBM Transformation Extender Map Designer documentation.