Debugging the MX validation framework

The MX framework map is designed to record the steps it performs in parsing the data to determine the correct RUN map to use.

It captures the metadata information obtained from the configuration input and the message data. The map can, optionally, output all of this information for debugging purposes. To enable this feature see the MX configuration file.

Error messages alert you that something went wrong in the process:

E09005 - Input validation failure from map ct052102_camt_052_001_02

The E09005 message alerts you that the RUN map being called was unsuccessful in parsing the data and so did not produce any output. In order to determine what is wrong in this case, run the data directly through the map ct052102_camt_052_001_02 with the Transformation Extender Trace setting enabled.

E09003 The WTX map failed due to invalid input card

The E09003 message usually occurs if the schema for the message data is not in the correct location, or if the message data is missing. Ensure that the schemas are deployed to the correct location. The default location the maps use is ../schemas.

E09006 The XML schema name: badname.001.001.01 used as input to the map in the configuration file was not able to be identified.

The map as shipped supports a set of messages and specific versions. If data is passed to the framework, and this data is missing the schema name, or if the validation map name cannot be determined, then this message will be triggered. Ensure that the data being checked has the schema name, and that the schema is in place for the data to use. If the schema is not included, it can be added. See Adding maps to the MX validation framework.