How to run the example

This SWIFT UC MX Validation will use the sample files to demonstrate the generation of validation report as output from a SWIFT UC XML message.

If input file is other than any of the supported SWIFT UC messages as per schema list indicated above.

1. Import the swift_uc.zip project into the Design Server.
2. Open the swift_uc project in Design Server and view the flow swift_uc_validation_flow.
   1. The Flow Description points to all the maps to be executed during the flow process, which will be called from within some of the map nodes in the flow. The following is a list of maps:
      • @packagemap=swift_uc/validation/mx_extended/maps/swift_uc_mx_trck_validation_enh/swuc1051_head112_trck001_uc
      • @packagemap=swift_uc/validation/mx_extended/maps/swift_uc_mx_trck_validation_enh/swuc1001_trck_001_001_02_uc
      • @packagemap=swift_uc/validation/schema_only/maps/swift_uc_mx_schema_validation_xsd/swuc1551_head112_trck001_uc
      • @packagemap=swift_uc/validation/schema_only/maps/swift_uc_mx_schema_validation_xsd/swuc1501_trck_001_001_02_uc
   2. It utilizes the following nodes:
      1. Map Nodes:
         • MX pre-check

           Runs map mxut1007_business_svc_swuc.mms which set flow variables, check pre-validation conditions and create infoset.json for validation.

         • MX de envelope

           Runs map swuc1900_deenvelope which separates header and document portions for messages.

         • BAH EXT-VAL

           Runs map swuc1991_bah_val which calls the appropriate map to performs extended validation on the header of a SWIFT UC message.

         • BAH XSD-VAL

           Runs map wuc1996_bah_val which calls the appropriate map to performs schema validation on the header of a SWIFT UC message.

         • DOC EXT-VAL

           Runs map swuc1992_doc_val which calls the appropriate map to performs extended validation on the body of a SWIFT UC message.

         • DOC XSD-VAL

           Runs map swuc1997_doc_val which calls the appropriate map to performs schema validation on the body of a SWIFT UC message.

           Note: The maps swuc1991_bah_val, swuc1992_doc_val, swuc1996_bah_val, and swuc1997_doc_va internally call all the other maps identified in the above Flow Description step.
      2. Decision Nodes:
         • pre-valid chk

           This node checks the flow variable stopTranslation to decide if further processing is not required.

      3. Route Nodes:
         • BAH-VAL

           This routing node identifies the type of validation to be performed for the business application header. The options are extended or schema. The default as per the flow settings is extended.

         • DOC-VAL

           This routing node identifies the type of validation to be performed for the business document. The options are extended or schema. The default as per the flow settings is extended.

      4. Log Nodes:
         • FAILURE

           It creates stopMXvalidation.json log file in case of no validation due to pre-condition check failures.

         • bah_ext

           It creates bah_validation_results.xml output file for results of message header extended validation.

         • bah_xsd

           It creates bah_validation_results.xml output file for results of message header schema validation.

         • doc_ext

           It creates doc_validation_results.xml output file for results of message body extended validation.

         • doc_xsd

           It creates doc_validation_results.xml output file for results of message body schema validation.

      5. Fail Node:
         • STOP

           It generates error message setup in the node in case of no validation performed.

3. In Design Server, create a package swift_uc_mx_validation that contains the input files and one flow swift_uc_validation_flow. The maps will automatically be included during deployment of the package onto the runtime server.
   Note: Not required for running flows on Design Server user interface directly.