How to run the example

This MT validation will use the sample file to demonstrate the validation of SWIFT MT messages.

1. Import the cbpr_translation.zip project into the Design Server.
2. Open the cbpr_translation project in Design Server and view the flow mt_validation. It utilizes the following nodes:
   1. It utilizes the following nodes:
      1. Source Node
         • mt_input

           This node identifies the input data to be translated in the flow. It uses the INPUT_FILE variable to set the location of the data.

      2. Map Node
         • validate_messages_enh

           Runs framework map validate_messages_enhwhich validates the input SWIFT MT message and produces validation results.

      3. Decision Nodes
         • RESULT_FORMAT

           This checks the flow variable REPORT_FORMAT to decide 'xml' or 'json'.

      4. Passthrough Node
         • XML_CONVERT

           This node receives an extended validation report in XML format and does not modify the content, thus passing it as is to the appropriate target node.

      5. Format Converter Node
         • JSON_CONVERT

           This node receives an extended validation report in XML format and converts it to JSON before passing it to the appropriate target node.

      6. Target Node
         • rslt_xml

           This node contains the resulting translation in XML format and creates the output as defined by the variable OUTPUT_RESULT_MT.

         • rslt_json

           This node contains the resulting translation in JSON format and creates the output as defined by the variable OUTPUT_RESULT_MT.

   2. It uses the following flow variables:
      • JVC_VALIDATION_LEVEL

        Flow variable JVC_VALIDATION_LEVEL is set without any default value.

      • INPUT_FILE

        Default value for the flow variable INPUT_FILE is ../tools/mt_validation/data/mtxxx.inp. This is the data file to be used for translation and can be customized. It is used in the Source node mt_input.

      • OUTPUT_RESULT_JSON

        Default value for the flow variable OUTPUT_RESULT_JSON is mt_validation_result.json. This is the location of the output file in json format. It can be customized.

      • OUTPUT_RESULT_XML

        Default value for the flow variable OUTPUT_RESULT_XML is mt_validation_result.xml. This is the location of the output file in xml format. It can be customized.

      • REPORT_FORMAT

        Default value for the flow variable REPORT_FORMAT is xml. It can be customized.

3. In Design Server, create a package that contains the input files and one flow mt_validation. The maps will automatically be included during deployment of the package onto the runtime server.
   Note: Check for the jvalccyy.prop file. It should be present with the latest FinPay installation (<finpay_install_dir>/swift/mt/jvc/maps) or it will be available in the swiftMTjvcConfig.tar.gz.