Running the Large Messaging sample

You can run the Large Messaging sample to perform the following processing:

  1. Read a WebSphere MQ message with an XML payload containing a repeated structure within it.
  2. Split each of the repeats into a single WebSphere MQ message.
  3. Write a WebSphere MQ message that confirms that the input message was successfully split into multiple messages.

You might see warning messages such as Unresolvable message field reference in the Problems view of the Message Brokers Toolkit. The messages refer to the ESQL files in the sample's message flow project but can be safely ignored. The warnings do not affect the behaviour of the sample at run time.

To run the Large Messaging sample, in the Broker Application Development perspective:

  1. Ensure the sample message flows and message set have been deployed.
  2. Double click SampleInputMessage.enqueue in the message flow project into which the sample was imported.
  3. Review the values for Queue manager name and Queue name on the General tab.  When using the default queue manager and Message Broker configuration there is no need to change the values.
  4. Click Write to queue to place a WebSphere MQ message on the input queue of the Large Messaging message flow.
  5. Start an instance of the Dequeue application:
    1. On the workbench toolbar, click the arrow on the Get a message from a Queue icon Get a message from a Queue.
    2. On the drop-down menu, click Get Message to invoke the Dequeue Message window.
    3. Enter the names for the queue manager and queue that you want. Use values of WBRK6_DEFAULT_QUEUE_MANAGER for the queue manager name, 2414 for the port number, and LARGE_MESSAGING_SLICING_COMPLETE for the queue name to work with the Default Configuration.
    4. Click Read From Queue to read a message from the queue.
    5. After closing the window, the next time that you click the arrow on the Get a message from a Queue icon Get a message from a Queue, you see the dequeue configuration that you created above listed on the drop-down menu. Click this file on the menu (or if it is number 1 on the menu, just click the icon itself) to get a message from the queue.
    6. Optional: While the Dequeue Message window is open, you can save a read message into a file in your message flow project to keep it for later. Click the Save As button, and in the Save Message As window, select the flow project and enter a name for the file.
  6. Examine the retrieved message.  This should indicate that there were 10 messages declared in the SaleListCount element of the input message and that 10 records were processed.

When you have observed that the value of the declared and actual message counts is the same you have successfully run the large messaging sample.

Main Page icon   Back to sample home