Debugging a message flow

This topic lists the tasks involved in debugging a message flow. If you are new to debugging, see Flow debugger overview for a conceptual overview.

  1. Deploying the message flow:
    • Make sure that the computer hosting the broker has Rational Agent Controller (RAC) installed and running (you can debug a flow in a broker hosted on this computer or a remote one). RAC authorizes user access to debug flows.
    • Deploy your message flow to an execution group in a broker and make sure that the broker is running. For further information, see Deploying.
  2. Starting the flow debugger:
    1. Setting flow debug preferences
    2. Attaching to the flow engine
    3. Putting a test message
    4. Getting a test message
  3. Working with breakpoints:
    1. Adding breakpoints
    2. Restricting breakpoints to specific flow instances
    3. Disabling breakpoints
    4. Enabling breakpoints
    5. Removing breakpoints
  4. Stepping through flow instances:
    1. Resuming flow instance execution
    2. Running to completion
    3. Stepping over nodes
    4. Stepping into subflows
    5. Stepping out of subflows
    6. Stepping into source code
    7. Stepping over source code
    8. Stepping out of source code
  5. Debugging data:
    1. Debugging messages
    2. Debugging ESQL
    3. Debugging Java
    4. Debugging mappings
  6. Managing flows and flow instances:
    1. Querying a broker for deployed flows
    2. Redeploying a flow
    3. Terminating a flow instance
    4. Detaching from the flow engine
Related concepts
Flow debugger overview
Message flows overview
Debug perspective
Related tasks
Installing Rational Agent Controller
Deploying
Related reference
Flow debugger shortcuts
Flow debugger icons and symbols