IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Testing a message flow

You can test your message flows using the Test Client.

Before you begin

You must have an integration node running, with an integration server configured. If you do not have an existing integration node and integration server, you can create them; see Creating an integration node and Creating an integration server.

Note: You cannot use the Test Client to send messages to an MQInput node in a flow in the following situations:
  • The MQInput node is configured with a policy.
  • The MQInput node has the MQ connection property set to Client Channel Definition Table (CCDT) file.
  • You deploy the message flow to a remote integration node, and the message flow receives messages on an MQInput node that is configured to use a local queue manager.

Instead, you can send messages to the flow by using Enqueue and Dequeue; see Enqueue and Dequeue.

About this task

To test a message flow, complete the following tasks:

Procedure

  1. Opening the Test Client editor
  2. Configuring the test settings
  3. Creating and editing a test message
  4. Selecting the deployment location for the message flow.

Results

The test message is put to the selected input node. The Test Client monitors the output nodes in the message flow and events are generated as the message passes through the message flow. You might need to stop the test manually, depending on the nodes in the message flow and the settings that you have configured in the Test Client.

What to do next

To test the message flow again, right-click Invoke Message Flow in the Message Flow Test Events pane and click Invoke to start a new test; or click Duplicate or Re-run to re-run the test using the same message.


af52240_.htm | Last updated 2015-03-27 19:26:44