Framework map

The framework map works by attempting to identify the message type from the input data, by looking for the schema name in the schema name space.

For example:

This information is used to determine the correct validation map name, and when it is identified, the relevant map is then run. An error report is produced if a validation failure is detected, and is also produced if it is not possible to identify the message type from the input data. See Error reporting in the MX validation framework.

Configuration file, mxconfig.xml, is used to control the level of validation that is performed by each of the individual MX validation maps. See MX configuration file.

If the message type cannot be identified from the input data, then, it is possible to provide the message type in the mxconfig file so that the framework map can identify the correct map to run. See MX configuration file.

You can customize the framework to add your own validation maps, if required. But the relationship between schema name and map name must be maintained in order for the framework map to identify the correct validation map to run. See Adding maps to the MX validation framework.

You can use different levels of validation for different message types, if required, by using separate configuration files for different message types. See How to use different levels of validation in the MX validation framework.

The framework map can be run in debug mode to help with problem diagnosis. See Debugging the MX validation framework. The framework map is called swiftval, and can be found in validation_framework . See Framework map.