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 MT202 message or CBPR+ pacs.004.001.09 output from a MT202 RETN message or CBPR+ pacs.002.001.10 output from a MT202 REJT message.

Before you begin

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 the latest version.

For the non Docker environments,

Copy jars to <TX_install_dir>/extjar.

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

Copy the following into the directory defined in config.yaml server.persistence.libs, by default, this is set to /opt/txlibs:

jvcwrap.jar
jvalccyy.jar

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.

Note: For RHEL, Docker is not supported, Podman can be used as a substitute since it provides a command line interface similar to Docker. Below is an example of using podman:

podman cp jnodes0.jar <brand>-server:/opt/<company>/<brand>/libs/.
Restart the design server, i.e., podman restart <brand>-server.

About this task

This example may generate failure in the audit.log.json log file to report the translation failure due to the pre-conversion checks:

Field 72, Line[1] starts with "/RETN/", Line 2 must start with a pattern "/2!c2!n/"
Line 3 must start with "/MREF/" followed by textual information (Error code: T20314)

Field 72, Line[1] starts with "/REJT/", Line 2 must start with a pattern "/2!c2!n/"
Line 3 must start with "/MREF/" followed by textual information (Error code: T20315)

Field 72, Line[1] starts with "/RETN/" or "/REJT/", if length of OrgInstructionId i.e.
text after "/MREF/" at line 3 is greater than 0 then OrgInstructionID must not start 
or end with "/" or contains "//" within the string. (Error code: T20316)

If Field 72, Line[1] starts with  "/RETN/", <Tag121><EndToEndTxnRef> should not be absent.

Procedure

Import the cbpr_translation.zip project into the Design Server.
Open the cbpr_translation project in Design Server and view the flow cbpr_mt202_pacs00n.
1. The Flow Description points to all the maps to be executed during the flow process, which will be called from within some of the map nodes in the flow. The following is a list of maps invoked using RUN built-in function during the flow process:
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt202_pacs009_adv/cbpr2814_mt202_pacs009_adv
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt20n_pacs009_cov/cbpr2815_mt202_pacs009_cov
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt20nRTN_pacs004/cbpr2824_mt202RTN_pacs004
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt20n_pacs009/cbpr2813_mt202_pacs009
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt_setvarlog/cbpr1502_mtmx_setvarlog
  - @packagemap=cbpr_plus/translation/mt-mx/maps/cbpr_t9n_mt20nRJT_pacs002/cbpr2842_mt202RJT_pacs002
2. It utilizes the following nodes:
  1. Source Node
    - mt_202
      This node identifies the input data to be translated in the flow. It uses the INPUT_FILE variable to set the location of the data.
  2. Map Node
    - mt_translate
      Runs map cbpr2810_mt202_framework which set flow variables, checks pre-translation conditions and translates the input file (mt) into required output (XML).
  3. Target Node
    - pacs.00n
      This node contains the resulting translation in XML format and creates the pacs.004 or pacs.009 output as defined by variable OUTPUT_DOC_RESULT_XML.
  4. Log Node
    - audit_log
      This node creates a log file specified by the flow variable AUDIT_LOG.
3. It uses the following flow variables:
  - INPUT_FILE
    Default value for the flow variable INPUT_FILE is ../cbpr_plus/translation/mt-mx/data/MT202_COR.inp. This is the data file to be used for translation and can be customized. It is used in the Source node mt_202.
  - OUTPUT_DOC_RESULT_XML
    Default value for the flow variable OUTPUT_DOC_RESULT_XML is pacs.00n.xml. This is the location of the output file in mt format. It is used in the Target node pacs.00n. It can be customized.
  - AUDIT_LOG
    Default value for the flow variable AUDIT_LOG is audit.log.json. This is the location of the audit log. It is used in the Log node audit_log. It can be customized.
  - CONFIG_FILE
    Default value for the flow variable CONFIG_FILE is ../cbpr_plus/translation/mt-mx/data/trx_config.xml. This is the location of the file containing the configuration settings. It can be customized.
Open the flow cbpr_mt202_pacs00n in the Design Server. It utilizes one source node, one map node, one log node, and one target node.
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.