How to run the example

This mt-mx translation will use the sample files to demonstrate the generation of SWIFT CBPR+ pacs.009.001.08 output from a MT205 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 tx-server:/opt/ibm/wsdtx/libs/.
  • Restart the design server, i.e., docker restart tx-server.

The stopTranslation.json file will report the translation failure due to the pre-conversion checks:

Translation MT205 REJT, MT205 RETN are not covered in this translation set.
  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_mt205_pacs009. It utilizes the following nodes:
    1. Map Nodes:
      • serialize data

        Runs map cbpr2817_mt20n_serialize which set flow variable mxMsgId to pacs.009.001.08 based on input and the flow variable stopTranslation if required.

      • set pacs009

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

      • trx_log

        Runs map cbpr1502_mtmx_setvarlog, process the flow variables.

      • build pacs009

        Runs map cbpr2819_mt205_pacs009 which set all the output pacs.009.001.08 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 the further translation is not required.

    3. Log Nodes:
      • FAILURE

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

      • pacs.009

        Archive the pacs.009.xml message generated from translation.

      • audit_log

        It creates the audit.log.json output file.

  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.