Mapping SWIFT MT and SWIFT MX Messages

The MT_MX_Mapping project shows how to use MT and MX activities to convert SWIFT MT messages to SWIFT MX messages, and to convert SWIFT MX messages to SWIFT MT messages.

This project contains the following processes:

MT_To_MX_Mapping_Process

You can use the MT_To_MX_Mapping_Process to convert an MT message to an MX message.

The following figure describes the MT_To_MX_Mapping_Process:

The MT_To_MX_Mapping_Process performs the following operations:
  1. The ReadFile activity reads an MT message, and passes it to the Parse_MT502 activity.
  2. The Parse_MT502 activity parses and validates the MT message, and passes it to the Render_MX_setr.010.001.04 activity.
  3. The Render_MX_setr.010.001.04 activity validates the message, generates an MX message, and passes it to the WriteFile activity.
  4. The WriteFile activity writes the MX message to the setr.010.001.04_output.xml file in the $Root/out directory.

MX_To_MT_Mapping_Process

You can use the MX_To_MT_Mapping_Process to convert an MX message to an MT message.

The following figure describes the MX_To_MT_Mapping_Process:

The MX_To_MT_Mapping_Process performs the following operations:

  1. The ReadFile activity reads an MX message, and passes it to the Parse_MX_setr.010.001.04 activity.
  2. The Parse_MX_setr.010.001.04 activity parses and validates the MX message, and passes it to the Render_MT502 activity.
  3. The Render_MT502 activity validates the message, generates an MT message, and passes it to the WriteFile activity.
  4. The WriteFile activity writes the MT message to the MT502_output.fin file in the $Root/out directory.