You can put a message on an input queue to test a message flow that you are debugging.
Before you start
Complete the steps described in: Attaching the flow debugger to an execution group for debugging.If your message flow includes MQInput and MQOutput nodes, you can test the flow by putting a message on the input queue of your first MQInput node.
You can use the command line interfaces or WebSphere® MQ Explorer (if you have WebSphere MQ Version 6 installed) or WebSphere MQ Services (if you have WebSphere MQ Version 5.3 installed) to put a message to a queue.
You can also use the Test Client as a repeatable alternative. To use the Test Client, complete the steps described in the following sections:
If the message is processed by the message flow and is put on an output queue, you can retrieve it from that queue. See: Debug: getting a test message from an output queue.
To configure an enqueue file so that you can use it to send a test message:
To find your enqueue file at a later time, switch to the Broker Application Development perspective and expand the navigation tree for your message flow project. Double-click your enqueue file to open it in a view.
If you want to add just a small amount of test data in your test message, type the data into the "Message data" window:
If you want your test message to contain a larger quantity of sample data (for example some structured XML), first create or import a file containing that data, then get the enqueue file to use it. Follow the optional steps to use either of these methods of creating and adding data.
To get the enqueue file to use a file that contains sample data:
To create a new file of sample data:
You can now select the file as described in the Optional: Using a file of sample data section. You can also double-click the file to open it in an appropriate editor.
If you already have a file on your computer containing sample data that you want to use in a test message, use these steps to import the data into the workbench. If the file contains XML, make sure that it has the extension .XML.
After you have imported the file as described here, a copy of your file is stored in the workbench data space along with all other workbench files for your configuration. Your original file is not used directly again.
The file appears in the Broker Development view in your chosen project, and you can select it as described in the Optional: Using a file of sample data section on this page. You can also double-click it to open it in an appropriate editor.