MT2XML transforms SWIFT Message Type (MT) messages to XML conforming to the schemas issued by SWIFT in SWIFT Standards Developer Kit (SDK).

Configuration and Testing

Component Configuration

Figure 1: MT2XML configuration properties

Attributes

Error handling configuration

Please refer Error Handling section in Common Configurations page.

Standard Release MT Year

Year in which SWIFT released SDK schemas.
Standard Release Years supported by MT2XML component and available in this property are:

• 2012
• 2013
• 2018
• 2020

Message Schema File

Name of standard MT message schema present in Schema Repository, for example 'fin.202.2012.xsd. It is the Schema file according to which transformed XML conforms.

These schema files are present at the following location: 

The component supports MT-XML transformation of all MT messages.

Expert Properties

Enable the Expert Properties view to configure these properties.

Figure 2: Expert properties for MT2XML

Pre Processing XSL Configuration

Pre Processing XSL configuration can be used to transform request message before processing it. Click the ellipses button against the property to configure the properties.

Refer to the Pre/Post Processing XSL Configuration section under the Common Configurations page for details regarding Pre Processing XSL configuration and Post Processing XSL configuration (below).

Post Processing XSL Configuration 

Post Processing XSL configuration can be used to transform the response message before sending it to the output port.

Process Message Based on Property

The property helps components to skip certain messages from processing.

Refer to the Process Message Based On a Property section under the Common Configurations page.

Message Schema Directory

If this property is used, the file name mentioned in the Message Schema file will be located from Message Schema Directory.

Figure 3: Message Schema Directory

Threadpool Configuration

This property is used when there is a need to process messages in parallel within the component, still maintaining the sequence from the external perspective. 

Click the Threadpool Configuration ellipsis button to configure the Threadpool Configuration properties.

Figure 4: Threadpool Configuration

Enable Thread Pool

Enable this option to configure the properties that appear as below.

Pool Size

Number of requests to be processed in parallel within the component. Default value is '1'.

Batch Eviction Interval (in ms)

Time in milliseconds after which the threads are evicted in case of inactivity. New threads are created in place of evicted threads when new requests are received. Default value is '1000'.

Testing

Input and Output

Sample Input

A sample of message type MT102 – Request for Transfer:

Output

XML output of the component for the above sample input can be seen by expanding the below:

Functional Demonstration

Use Feeder and Display components to send sample input and check the response respectively.

Figure 5: Event process demonstrating scenarios

Scenario 1 - Using MT103 with MT Year 2020

This scenario demonstrates the transformation of a message in MT format to XML using MT103 message type.

Configure the MT2XML component with the MT year 2020 and provide the location for the schema.

Figure 6: MT2XML microservice configured with MT103 (2020) with the schema file path provided

Sample Input

After running the event process, click the Send button in the Feeder window to send the following input message to the MT2XML microservice.

Figure 7: Feeder window with the sample message

Output

Figure 8: Display window with the output message for Scenario 1 input

Scenario 2 - Using MT101 with MT Year 2018

This scenario demonstrates the transformation of a message in MT format to XML using MT101 message type.

Configure the MT2XML component with the MT year 2018 and provide the location for the schema.

Figure 9: MT2XML microservice configured with MT101 (2018) with the schema file path provided

Sample Input

After running the event process, click the Send button in the Feeder window to send the following input message to the MT2XML microservice.

Figure 10: Feeder window with the sample message

Output

Figure 11: Display window with the output message for Scenario 2 input

Scenario 3 - Using MT103 with MT Year 2018

This scenario demonstrates the transformation of a message in MT format to XML using MT103 message type.

Configure the MT2XML component with the MT year 2018 and provide the location for the schema.

Sample Input

Sample Output

Figure 12: Display window with the output message for Scenario 3 input