How to run the example

This mx-mt translation will use the sample files to demonstrate the generation of SWIFT MT112 message output from a CBPR camt.109.001.01 XML message.

The cbprJnodesConfigIBM.tar.gz file is available either in IBM_financialpaymentsplus_vn.n.n.n.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.
Note: Recommend using latest version.
For the non Docker environments,
  • Copy jars to <TX_install_dir>/extjar.

For TX V11.0.0 and up, native based Design Server installation,

Copy jars into the directory pointed to the config.yaml server.persisitence.files, by default, this is set to /opt/txlibs, then restart the running application ./ITX stop and then ./ITX start

For the Docker environments,
  • Docker cp jnodes0.jar <brand>-server:/opt/<company>/<brand>/libs/.
  • Restart the design server, i.e., docker restart <brand>-server.

This example may generate stopTranslation.json log file to report the translation failure, if input message is not camt.109.001.01

.
  1. Import the cbpr_translation.zip project into the Design Server.
  2. Open the cbpr_translation project in Design Server and view the flow cbpr_camt109_mt112. It utilizes the following nodes:
    1. Map Nodes:
      • MX deenvelope

        Runs map cbpr2724_deenvelope which sets the flow variable mxMsgId to 'camt.109.001.01' based on the input. Also, distribute the input data into two: Application header and document.

      • set BAH

        Runs map cbpr2643_bah_camt109_set which set up the flow variables for the Application Header.

      • serialize data

        Runs map cbpr2645_camt109_serialize which set flow variable mtMsgId to '112' based on input and the flow variable stopTranslation if required.

      • set mt112

        Runs map cbpr2644_camt109_mt112_jexit, invokes JEXIT call to java class located in jnodes0.jar and returns with flow variables.

      • trx_log

        Runs map cbpr2501_mxmt_setvarlog, process the flow variables by extracting log as key.

      • build mt112

        Runs map cbpr2642_camt109_mt112 which builds the output MT112 message fields based on the values set in flow variables.

    2. Decision Nodes:
      • pre-conv chk

        This check the flow variable stopTranslation to decide if further translation is not required.

    3. Log Nodes:
      • FAILURE

        It creates stopTranslation.json log file in case of failure during translation.

      • MT 112

        Archive the mt112.out message generated from translation.

      • audit_log

        It creates the audit.log.json output file in case of success translation to MT112.

  3. In Design Server, create a package that contains the input files and one flow. The maps will automatically be included during deployment of the package onto the runtime server.