Skip to main content
Skip table of contents

Examples

Understanding the translation process

The transformation is as follows:

  1. Core Flow: Core flow consists of four flows, out of which 2 would be used.

  2. MTToMXTranslator:2.0: MT to MX translator2:0 accepts the MT message from the file interface which, in turn, invokes the corresponding MT to MX translation. In case of an error, the file is moved to the Error directory.

  3. MXToMTTranslator:2.0: MX to MT translator2:0 accepts the MX message from the file interface which, in turn, invokes the corresponding MX to MT translation. In case of an error, the file is moved to the Error directory.

Other than the File interface, the exchange of MT/MX messages can be performed using interfaces like REST, WebService, FTP, etc too by replacing the FileReader microservice with the respective microservice.

  1. MT_To_MX: The MT messages are translated via flows saved under the MT_To_MX category. Various pre-built flows can be used to translate an MT message to an MX message.

  2. MX_To_MT: The MX messages are translated via flows saved under the MX_To_MT category. Various pre-built flows can be used to translate an MX message to an MT message.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.