Before you can debug your message flow, you must attach the flow debugger to the execution group where your flow is deployed, and then start a debugging session.
Before you start:
From a single workbench, 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. 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.
The flow debugger can debug runtime brokers from previous versions. Select the version of the broker that you want to debug by checking the corresponding option on the Engine Selection panel in the Debug wizard, as described previously.
For details of which version of Rational Agent Controller (RAC) you must install on each of the broker operating systems, see Installing Rational Agent Controller.
You cannot debug flows that you have deployed to a 64-bit execution group; only 32-bit execution groups are supported by the flow debugger.
To attach the debugger to an execution group:
Next:
Continue with one of the following tasks: