IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

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.

Deploy your message flow to an integration server in a broker and make sure that the broker is running. See: Deploying resources.

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.

Start the flow debugger.
Set the required preferences, then start debugging by attaching the flow debugger to an integration server. You can then send test messages along the flow. See: Starting the flow debugger.
Work with breakpoints.
Add and manipulate breakpoints in your message flow. See: Working with breakpoints in the flow debugger.
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.
View message data.
View (and change) data in messages, ESQL code, or Java™ code as debugging progresses. See: Debugging data.
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 integration server. See: Managing flows and flow instances during debugging.

ag11080_.htm |

Last updated Friday, 21 July 2017