How to run the example

This mt-mx translation will use the sample files to demonstrate the generation of CBPR+ pacs.008.001.08 XML message output from a MT103 SWIFTGo 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.

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

If input file is SWIFT message other than MT103 or not a SWIFT message or Field 72, Line 1 starts with "/REJT/" OR "/RETN/"

Import the cbpr_translation.zip project into the Design Server.
Open the cbpr_translation project in Design Server and view the flow cbpr_mt103sgo_pacs008. It utilizes the following nodes:
1. Map Nodes:
  - serialize data
    Runs map cbpr2803_mt103_serializ which set flow variables, check pre-translation conditions and create infoset.json of required input.
  - set pacs008
    Runs map cbpr2804_mt103_pacs008_jexit, invokes JEXIT call to java class located in jnodes0.jar and returns with flow variables.
  - build MX
    Runs map cbpr2805_mt103_pacs008_sgo which set all the output pacs.008.001.08 SWIFTGo message fields based on the values set in flow variables.
  - trx_log
    Runs map cbpr1502_mtmx_setvarlog, process the flow variables by extracting audit log.
2. Decision Nodes:
  - pre-conv chk
    Decide if further translation is not required.
3. Log Nodes:
  - FAILURE
    Archive for any failure during translation.
  - pacs.008
    Archive the pacs.008.001.08 SWIFTGo message generated from translation.
  - audit_log
    It creates the audit.log.json output file.
4. Fail Nodes:
  - STOP
    It generates error message setup in the node in case of no translation.
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.