How to use different levels of validation in the MX validation framework

You can perform different levels of validation for different messages types.

For example, you might not want to perform BIC validation for the camt messages, but you do want to perform this for the pacs messages. In this situation, you would use two separate mxconfig.xml files:

mxconfig_camt.xml	BIC validation=F
mxconfig_pacs.xml	BIC validation=T

How you use these files depends on whether you are using the framework map, or are running the individual MX validation maps independently of the framework. The examples here use the Command Server as the ITX map execution platform.

This example shows how to use the files when you use the framework map:

dtxcmdsv swiftval -IF1 camt.053.001.04.xml IF2 mxconfig_camt.xml dtxcmdsv swiftval -IF1 pacs.008.001.04.xml IF2 mxconfig_pacs.xml

This example shows how to use the files when you use the individual MX validation maps:

dtxcmdsv ct053104_camt_053_001_04 -IF1 camt.053.001.04.xml IF2 mxconfig_camt.xml

dtxcmdsv ps008104_pacs_008_001_04 -IF1 pacs.008.001.04.xml IF2 mxconfig_pacs.xml