WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Using the Test Client in trace and debug mode
You can run the Test Client in trace and debug mode to trace the path of a test message through a message flow.
Before you start:
Before you can test your message flow, you must have configured a broker. The broker must be running. You must also have created an execution group to which to deploy your message flows.
You can use the trace and debug mode to complete the following
actions:
- Stop the test message at breakpoints in the message flow by using the flow debugger.
- Trace the message nodes and terminals that the test message passes through.
- See the test message change as it passes through the message flow.
- View a message node, where an exception occurs, and the associated exception message and trace details.
Note: If the message flow does not contain an MQOutput, HTTPReply, JMSOutput, or SOAPReply node, the Test
Client stops the test after
the test message is sent to the broker. Therefore, you might not
see trace events when the flow is run.
All output from the trace and debug mode is written to the "Message flow test events" section on the Message flow Test Events tab.
To use the Test Client in trace and debug mode, complete the following steps:
Next:
You can modify
the deployment location settings from run mode to trace and debug
mode by using the Deployment Location wizard:
- Click Configuration in the Test Client.
- Click Deployment to display the deployment settings.
- Click Change to open the Deployment Location wizard.