How to run the example

This mx-mt translation will use the sample files to demonstrate the generation of SWIFT MT199 or MT299 message output from a CBPR+ pacs.002.001.10 XML message.

The cbprJnodesConfigIBM.tar.gz file is available either in IBM_financialpaymentsplus_10.2.0.0.zip or in UIProjectImports directory.

Extract from cbprJnodesConfigIBM.tar.gz file.
  • jnodes0.jar
The following jars needs to be copied from <TX_install_dir>/jars:
  • jackson-core-n.n.n.jar
  • jackson-annotations-n.n.n.jar
  • jackson-databind-n.n.n.jar

Or visit https://repo1.maven.org/maven2/com/fasterxml/jackson/core/ for download.

For the non Docker environments:
  • Copy jars to <TX_install_dir>/extjar.
For the Docker environments
  • Docker cp jnodes0.jar tx-server:/opt/ibm/wsdtx/libs/.
  • Restart the design server, i.e., docker restart tx-server.
  1. Import the cbpr_translation.zip project into the Design Server.
  2. Open the cbpr_translation project in Design Server and build the following maps:
    • cbpr2500_pacs002_framework
    • cbpr2501_mxmt_setvarlog
    • cbpr2502_pacs002_translate
    • cbpr2503_pacs002_mtn99
  3. Run the main map cbpr2500_pacs002_framework.
    The following output files will be generated:
    • mt_out.txt

      File contains the translated MT199 or MT299 SWIFT message from CBPR+ pacs.002 message based on the <OrgnlMsgNmId> which could be pacs.008 or MT103 (will generate MT199) or pacs.009 or MT202 or MT205 (will generate MT299).

    • audit_msg.json

      Reports translation logs, including failure due to the pre-conversion checks as:

      Either <OrgnlMsgNmId> is not one of these ("pacs.008", "MT103", "pacs.009", "MT202", "MT205") or 
    <TxSts> "transaction status" is not "RJCT".