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.

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 <brand>-server:/opt/<company>/<brand>/libs/.
  • Restart the design server, i.e., docker restart <brand>-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 generates MT199 or MT299 based on the <OrgnlMsgNmId> which could be pacs.008 or MT103 (will generate MT199) or pacs.009 or MT202 or MT205 (will generate MT299).

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

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

Procedure

  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_pacs002_mtn99.
    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/mx-mt/maps/cbpr_t9n_mx_pacs002_translate/cbpr2502_pacs002_translate
      • @packagemap=cbpr_plus/translation/mx-mt/maps/cbpr_t9n_mx_pacs002_mtn99/cbpr2503_pacs_002_mtn99
      • @packagemap=cbpr_plus/translation/mx-mt/maps/cbpr_t9n_mx_setvarlog/cbpr2501_mxmt_setvarlog
    2. It utilizes the following nodes:
      1. Source Node
        • pacs_002

          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
        • mx_translate

          Runs framework map cbpr2500_pacs002_framework, checks pre-translation conditions and translates the input file (mx or xml) into required output (mt).

      3. Target Node
        • mtn99

          This node contains the resulting translation in MT format (mt199.out or mt299.out) and creates the output as defined by the variable OUTPUT_RESULT_MT.

      4. Log Node
        • audit_log

          This node creates a log file specified by the flow variable AUDIT_LOG.

    3. It utilizes the following flow variables:
      • INPUT_FILE

        Default value for the flow variable INPUT_FILE is ../cbpr_plus/translation/mx-mt/data/env_pacs_002_199.xml. This is the data file to be used for translation and can be customized. It is used in the Source node pacs_002

      • OUTPUT_RESULT_MT

        Default value for the flow variable OUTPUT_RESULT_MT is mtn99.out. This is the location of the output file in mt format. It is used in the Target nodes mt199 or mt299 . 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/mx-mt/data/trx_config.xml. This is the location of the file containing the configuration settings. It can be customized.

  3. Open the flow cbpr_pacs002_mtn99 in the Design Server. It utilizes one source node, one map node, one log node, and one target node.
  4. 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.