Running the EDIFACT sample

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

The input messages

The EDIFACT sample contains the following five test messages.

• D.96A_INVOICE_1.mbtest
• D.96A_INVOICE_2.mbtest
• D.96A_INVOICE_3.mbtest
• D.96A_INVOICE_4.mbtest
• D.96A_INVOICE_missing_BGM.mbtest

All five input messages are INVOICE messages. The first four input messages are valid. The fifth input message is not valid: the BGM 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 EDIFACT_TO_XML_IN queue:
   1. In the EDFACT Message Flows project, double-click one of the .mbtest files to open it in the Test Client.
   2. In the Test Client, click Send Message. The message in the .mbtest file is written to the queue.

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

   • If the message is a valid EDIFACT message, it is passed to the Compute node which converts the EDIFACT message to an XML message. The Compute node then passes the message to the EDIFACT_TO_XML_OUT MQOutput node which puts the message on the EDIFACT_TO_XML_OUT queue.
   • If the message is not a valid EDIFACT message, the message is passed to the EDIFACT_FAIL node, which puts the message on the EDIFACT_FAIL queue.
     
2. Get the transformed message from the EDIFACT_TO_XML_OUT queue using Dequeue:
   1. In the Test Client, click Dequeue.
   2. Click Get Message to read a message from the EDIFACT_TO_XML_OUT queue. The transformed message is now in XML format.
   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_EDIFACT_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_EDIFACT_IN.
   4. Click Send Message to put the copied message onto the XML_TO_EDIFACT_IN queue.
   
   When you put the message on the XML_TO_EDIFACT_IN queue, the XML_TO_EDIFACT_IN MQInput node in the second message flow (called VALIDATINGXML2EDIFACT.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 an EDIFACT message. The Compute node then passes the message to the XML_TO_EDIFACT_OUT MQOutput node which puts the message on the XML_TO_EDIFACT_OUT queue.
   • If the message is not a valid XML message, the message is passed to the EDIFACT_FAIL node, which puts the message on the EDIFACT_FAIL queue.
4. In the Test Client, click Dequeue.
5. In the Queue name field, type XML_TO_EDIFACT_OUT.
6. Click Get Message to get the message from the XML_TO_EDIFACT_OUT queue. The message is now an EDIFACT message.

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

The D.96A_INVOICE_missing_BGM.mbtest message

When you put the D.96A_INVOICE_missing_BGM.mbtest message through the first message flow, the validation on the EDIFACT_TO_XML_IN MQInput node fails because the BGM field is missing from the message. The EDIFACT_TO_XML_IN MQInput node puts the message on the EDIFACT_FAIL queue.

Back to sample home