MT Launcher Validation framework
This sample validation framework uses the Transformation Extender Launcher and the JVC to perform trigger-based MT validation.
The Transformation Extender Launcher Edition is required to run this example.
The framework for this sample is triggered by placing a file containing a single MT message into a folder, which causes the framework to be invoked to validate the message. Depending on the results of the validation, the framework either creates an error report file, or passes the message through unchanged. After being processed, the file is deleted from the input folder. Using this method it is possible to validate numerous separate files by placing them into the input folder. The framework, therefore, consists of a folder structure for processing the data, a map source file for performing the validation, and a Launcher System Definition file for deploying to the Launcher. The framework is installed into this directory location: install_dir/packs/financial_payments_vn.n.n.n/swift/mt/examples/validation
Where install_dir is the installed location of the Transformation Extender base product and n.n.n.n is the version number of the pack.
- data/input
- Placeholder for files to be validated
- data/output/error/
- Placeholder for error reports.
- data/output/passed/
- Placeholder for files that pass validation.
- maps/execution/
- Executable maps are deployed here.
- maps/source/validate_mt
- Where validate_mt is the source map file for deployment.
- msds/validate_mt.msd
- Where validate_mt.msd is the system definition file for deployment.
The following instructions are for deploying and running the framework on a Windows platform. Refer to the Transformation Extender documentation for instructions on running the Launcher on other platforms.