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

Flow debugger overview

Use the flow debugger in the WebSphere® Message Broker Toolkit to track messages through your message flows.

Use the Debug perspective in the WebSphere Message Broker Toolkit to use the flow debugger. For an introduction to the Debug perspective and the views it presents, see Debug perspective.

You can set breakpoints in a message flow, then step through the flow. While you are stepping through, you can examine and change the message variables and the variables used by ESQL code and Java™ code. You can debug a wide variety of error conditions in flows, including the following:

From a single WebSphere Message Broker Toolkit, you can attach the debugger to one or more execution groups, and debug multiple flows in different execution groups (and therefore multiple messages) at the same time. However, an execution group can be debugged by only one user at a time. Therefore, if you attach your debugger to an execution group, another user cannot attach a debugger to that same execution group until you have ended your debugging session.

When you debug message flows, use a broker that is not being used in a production environment. Debugging might degrade the performance of all message flows in the same execution group and those in other execution groups that share the same broker because they might be affected by potential resource contention.

Debugging code in message flow nodes

You can use the flow debugger to examine the behavior of code in message flow nodes.

After you have deployed a message flow, you can set a breakpoint just before one of the nodes listed in this section so that, when the flow pauses at the breakpoint, you can step through the code line by line. This allows you to examine the logic, and check the actions taken and their results. You can set additional breakpoints and you can also examine and change variables.

The following nodes can contain ESQL code modules:
  • Compute node
  • Filter node
  • Database node
The following nodes can contain Java code modules:
  • User-defined nodes
  • JavaCompute node

Restrictions

The following restrictions apply when you debug a message flow:
  • You must use the same version of the broker and the WebSphere Message Broker Toolkit; for example, you cannot use the WebSphere Message Broker Toolkit Version 6.1 to debug a message flow that you have deployed to a broker at an earlier version.
  • You should not debug message flows over the Internet, because there might be security issues.
  • You can debug a message flow that contains a Mapping node, but you cannot step into the graphical data mapping to view or set breakpoints on the transforms. However, you can use the user trace facility to find information that might help you to diagnose and debug mapping problems. For more information about user trace, see Debugging with user trace.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:03


Concept topicConcept topic | Version 8.0.0.7 | ag11050_