MX validation framework map
The individual MX validation maps are controlled by this single executable map. The map source file is mx_validation_framework. The executable map name is swiftval.
The map has the following five inputs and three outputs:
| Input or Output | Description |
|---|---|
| Input 1 (mx) | The MX data file. This file can be of any message type that is supported by the pack, or can be of a type that you add. |
| Input 2 (mxconfig) | The MX map configuration data. See“ MX configuration file. |
| Input 3 (bicDirectory) | The BIC information file. |
| Input 4 (ccyCtryCodeList) | The Currency Code, Country Code, and Decimal Places information file. |
| Input 5 (errorMsgList) | The source file for all of the error messages. |
| Output 1 (Framework) | This card performs the main processing in the map, and it creates an audit log of the results. It determines the schema name from the input MX instance in input 1 (mx). If this is unsuccessful, it then tries to obtain the schema name from the mxconfig.xml file in input 2 (mxconfig). Having obtained the schema name, it then performs a RUN command to invoke the relevant validation map for this schema. If the map is unable to obtain the schema name from either of these two methods, the map will not perform any validation. |
| Output 2 (GatherResults) | This card analyzes the results of the RUN command. If the RUN command completed successfully, this card stores the result of the RUN command of the validation map. If the RUN command did not complete successfully, this card performs a LOOKUP on file errcodes.txt in input 5 (errorMsgList), to obtain the relevant error message. |
| Output 3 (FinalOutput) | This card determines whether Trace is turned on in mxconfig in input 2 (mxconfig). If Trace is turned on, this card returns a concatenation of Output 1 (Framework) plus Output 2 (GatherResults). If Trace is not turned on, it returns Output 2 (GatherResults). |
Prior to running the MX validation framework, build the maps for Windows using the build_deploy_mx_validation.bat file. The build_deploy_mx_validation.bat file creates the deployment_mx_validation directory under the mx/maps directory.
Prior to running the MX validation frame, build the maps as described in Building multiple maps using Deploy.
To run the MX Validation Framework, execute the swiftval map, overriding the first input with the MX data to validate.
Input Card 2 may be overridden with different mxconfig files in order to use different levels of validation for different message types (See How to use different levels of validation in the MX validation framework).
For most cases the other inputs should remain static for optimal performance.