Debugging a message flow

Use the tasks described in this section of the documentation to manage and work with the flow debugger.

Before you start

If you are new to debugging, see: Flow debugger overview.

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. See: Deploying a message flow application.

To debug a message flow, perform the following tasks. You might want to vary the tasks you perfom and repeat certain tasks, depending on your particular debugging requirements.

  1. Start the flow debugger.

    Set required preferences and then start debugging by attaching the flow debugger to an execution group. You can then send test messages along the flow. See: Starting the flow debugger.

  2. Work with breakpoints.

    Add and manipulate breakpoints in your message flow. See: Working with breakpoints in the flow debugger.

  3. Follow the progress of a test message.

    Use breakpoints to pause the progress of a test message so that you can observe its behavior. See: Stepping through message flow instances in the debugger.

  4. View message data.

    View (and change) data in messages, ESQL code, Java code or mappings as debugging progresses. See: Debugging data.

  5. Manage message flows.

    During a debugging session, there are various administrative tasks you might need to do. When you have finished debugging, detach the debugger from the execution group. See: Managing flows and flow instances during debugging.

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
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:54

ag11080_