This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: af52120_
Writer: John Morris-Smith

Task topic

This build: July 31, 2007 21:29:28

Testing a message flow

You can test sending messages when you are developing message flows before you deploy them using the Test Client.

First you need to:
To test a message flow:
  1. Select a Message flow from the Broker Application Development Navigator.
  2. Invoke the Events page from the message flow by performing one of the following actions: Right click and select the Test Message Flow option, or select either an MQInput node or an HTTPInput node depending on which one is the message source, right click and select Test.
  3. Fill in the message content in the available panel on the Events page.
  4. Select Send Message button on the Events page.
  5. Select required server from the Deployment Location dialog and ensure the Mode is set to Run.
  6. Select Finish to initiate testing.

The testing starts when a message-flow event is invoked and ceases with a Stop event.

One execution can be performed at the same time in the Test Client.

A test can be stopped manually or automatically depending on the situation. Stopping the test has no effect on the runttime, and will only disconnect the monitors that are running.

A synchronous test, as would be the case when the message flow invoked from an HTTPInput node, is stopped automatically when a reply message is received.

An asynchronous test, as would be the case when the message flow is invoked from an MQInput node, can be stopped manually depending on the monitor setting in the configuration panel.

All execution events are stopped when the Test Client is closed and any test monitors are removed.

Related tasks
Preparing to test a message flow
Related reference
Test Client Events page
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:28

af52120_ This topic's URL is: