What the example contains

Files and directories included in this example are as follows:

• Maps:

  The maps directory contains the following map sources to use when running under Design Studio:

  • swift_uc_mx_trck_validation_enh.mms

    Utility maps called by main map for all the trck SWIFT UC xml message MX validation.

  • swift_uc_mx_validation_frmwrk_map_enh.mms

    The main map used to apply MX validation to SWIFT UC xml messages.

  Note: When running under Design Server, the main framework map is swift_uc_mx_validation_frmwrk_map_flw_enh.mms.
• Schemas:

  The schemas directory contains the following files:

  • bic.xsd

    Metadata that represents the bic.xml repository file structure.

  • ccy.xsd

    Metadata that represents the currencycodedecimals.xml repository file structure.

  • mxconfig.xsd

    Metadata that represents the mxconfig.xml configuration file structure.

  • trck.001.001.02_uc.xsd
  • head.001.001.02_trck_001_uc.xsd
  Note: XML schemas were downloaded from SWIFT MyStandards Readiness SWIFT UC Portal.
• Trees:

  The trees directory contains the following files:

  • mxvalErrorReport.mtt

    Metadata that represents the xml based structure of the validation report.

  • swiftroute_funds.mtt

    Metadata that is used as an internal element placeholder.

• Data:

  The data directory contains the following file:

  • bic.xml

    Repository file listing all BICs which are used during validation.

  • currencycodedecimals.xml

    Repository file listing country codes, currency codes and corresponding maximum fractionally digits, used as reference for validation.

  • mxconfig.xml

    Holds the MX configuration information on how to process the message.

  Sample SWIFT UC valid files with header envelope for test purposes:

  • bah_trck_001_001_02_uc_valid.xml