Running the Browsing WebSphere MQ Queues sample

When you import the sample you might receive warnings in the Toolkit about the mandatory filter pattern, and the staff schema element. These warnings are message set related and do not affect the running of the sample.

Running the Browsing WebSphere MQ Queues sample consists of putting each of the messages through the message flow. You can run the sample to learn what happens in the following situations:

For more information, see About the Browsing WebSphere MQ Queues sample.

If you encounter any problems when you run the sample, see Resolving problems when running samples in the IBM Integration Bus documentation.

Running the sample with a message that contains a staff number which is not equal to 2

To run the sample with the message that contains a staff number which is not equal to 2:

  1. In the Application Development view, expand the Browsing Websphere MQ Queues Message Flows project and double-click staffmsg1.mbtest. The staffmsg1.mbtest file opens in the Test Client.
  2. In the Test Client, click Enqueue.
  3. Click Send Message. A message that contains a staff number equal to 1 is put on the MQBROWSE_IN queue.
  4. View the MQBROWSE_IN queue using the WebSphere MQ Explorer. The message has been read but still remains on the input queue. Notice that the MQInput node does not attempt to process the message more than once, even though the message remains on the queue.

Running the sample with a message that contains a staff number equal to 2

To run the sample with the message that contains a staff number equal to 2:

  1. In the Application Development view, expand the Browsing Websphere MQ Queues Message Flows project and open staffmsg2.mbtest in the Test Client and click Enqueue.
  2. Click Send Message.
  3. View the MQBROWSE_IN queue using the WebSphere MQ Explorer. The message is no longer on this queue. If you put this test message after using staffmsg1.mbtest, notice that the message with a staff number equal to 1 still remains on the queue. This is because the MQGet node gets the message by matching the message ID, and not by removing the first message on the queue.
  4. In the Test Client click Dequeue.
  5. Click Get Message to get the message from the MQBROWSE_OUT queue.

Back to sample home