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:

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. You can use the Dequeue section of the Test Client to retrieve the messages from the output queues. If the message is not on the output queue you expect, change the name of the output queue to the name of the failure queue. Follow the instructions below to run the sample:

  1. Put one of the input messages on the EDIFACT_TO_XML_IN queue:
    1. In the Broker Development view, expand the EDIFACT 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:

  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. Ensure that Source is selected under Detailed Properties. Right-click the contents of the message in the Source pane, and click Select All.
    4. To take a copy of the message, right-click the contents of the message in the Source pane and click Copy.
  3. Put your copied message from step 2 onto the XML_TO_EDIFACT_IN queue by using the Test Client.
    1. In the Test Client, click Enqueue.
    2. In the Source pane, right-click the Source message and click Select All. 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 onto 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:
  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 Resolving problems when running samples in the WebSphere Message Broker documentation. The message might still be on the input queue, 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 onto the EDIFACT_FAIL queue.

Back to sample home