Running the SWIFT sample

This topic explains how to put the test messages through the SWIFT message flow.

The input messages

The SWIFT sample contains the following four test messages.

• 103_0001.mbtest
• 103_0002.mbtest
• 103_0003.mbtest
• 103_missing_SW20.mbtest

All four input messages are MT103 Single Customer Credit Transfer messages. The first three input messages are valid. The fourth input message is not valid: the SW20 field is missing from the message.

Running the sample

To run the sample, you must put messages on the input queues, and get messages from the output queues. Follow the instructions below:

1. Put one of the input messages on the SWIFT_TO_XML_IN queue:
   1. In the Message Brokers Toolkit, switch to the Broker Application Development perspective.
   2. In the SWIFT Message Flows project, double-click one of the .mbtest files to open it in the Test Client.
   3. In the Test Client click Enqueue
   4. Click Send Message. The message in the .mbtest file is written to the queue.

   When you put a message on the SWIFT_TO_XML_IN queue, the SWIFT_TO_XML_IN MQInput node in the first message flow (called VALIDATINGSWIFT2XML.msgflow) parses the message and validates it against the message set:

   • If the message is a valid SWIFT message, it is passed to the Compute node which converts the SWIFT message to an XML message. The Compute node then passes the message to the SWIFT_TO_XML_OUT MQOutput node which puts the message on the SWIFT_TO_XML_OUT queue.
   • If the message is not a valid SWIFT message, the message is passed to the SWIFT_FAIL node, which puts the message on the SWIFT_FAIL queue.
     
2. Get the transformed message from the SWIFT_TO_XML_OUT queue using Dequeue:
   1. In the Test Client, click Dequeue.
   2. Click Get Message to read a message from the SWIFT_TO_XML_OUT queue.
   3. Right click on the contents of the message and Select All, and then Copy to take a copy of the message.
3. Put your copied message from step 2 on the XML_TO_SWIFT_IN queue using the Test Client.
   1. In the Test Client, click on Enqueue
   2. In the Source pane, right click on the Source message and click Select All and then right click and select Paste to replace the existing source message.
   3. In the Queue name field, type XML_TO_SWIFT_IN.
   4. Click Send Message to put the copied message onto the queue.
   
   When you put the message on the XML_TO_SWIFT_IN queue, the XML_TO_SWIFT_IN MQInput node in the second message flow (called VALIDATINGXML2SWIFT.msgflow) parses the message and validates it against the message set:
   • If the message is a valid XML message, it is passed to the Compute node which converts the XML message to a SWIFT message. The Compute node then passes the message to the XML_TO_SWIFT_OUT MQOutput node which puts the message on the XML_TO_SWIFT_OUT queue.
   • If the message is not a valid XML message, the message is passed to the SWIFT_FAIL node, which puts the message on the SWIFT_FAIL queue.
4. In the Test Client, click Dequeue.
5. In the Queue name field, type XML_TO_SWIFT_OUT.
6. Click Get Message to get the message from the XML_TO_SWIFT_OUT queue. The message is now a SWIFT message.

If there is no message on the SWIFT_TO XML_OUT or XML_TO_SWIFT_OUT queues, see Diagnosing problems. The message might still be on the input queue, or it might be on the SWIFT_FAIL queue, or on one of the system queues.

The 103_missing_SW20.mbtest message

When you put the 103_missing_SW20.mbtest message through the first message flow, the validation on the SWIFT_TO_XML_IN MQInput node fails because the SW20 field is missing from the message. The SWIFT_TO_XML_IN MQInput node puts the message on the SWIFT_FAIL queue.

Industry standard formats

Back to sample home