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
Attaching the flow debugger to an execution group for debugging
Before you can debug your message flow, you must attach the flow debugger to the execution group where your flow is deployed, then start a debugging session.
Before you start:
- If authorization permissions are required, see: Authorizing users for administration
- Create a message flow. See: Developing message flows
- f
- Deploy your message flow to a broker execution group. See: Deploying resources
- Start the broker. See: Starting and stopping a broker
From a single WebSphere® Message Broker Toolkit, you can attach the flow debugger to multiple execution groups that are running on the same or on different host computers, and debug their flows (and therefore multiple messages) simultaneously.
An execution group can be debugged by only one user at a time. 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.
To attach the debugger to an execution group:
Next:
Continue with one of the following tasks:
- Optional: Debug: putting a test message on an input queue and Debug: getting a test message from an output queue. These tasks involve putting messages to, and taking messages from, WebSphere MQ queues and are therefore useful only if your message flow includes MQInput and MQOutput nodes.
- Working with breakpoints in the flow debugger.