Before you can debug your message flow, you must attach the flow
debugger to the integration server where your flow is deployed, then
start a debugging session.
About this task
From the IBM Integration Toolkit, you
can attach the flow debugger to multiple integration servers that
are running on the same or on different host computers, and debug
their flows (and therefore multiple messages) simultaneously.
An integration server can be debugged
by only one user at a time. If you attach your debugger to an integration
server, another user cannot attach a debugger to that same integration
server until you have ended your debugging session.
To
attach the debugger to an integration server:
Procedure
- Set a Flow Debug port number.
To configure the
integration node JVM with a debug port number, use one of the following
methods:
The Java JIT (just-in-time)
compiler is disabled if the jvmDebugPort parameter is set to an integer
greater than zero. If you are not debugging a message flow, reset
the jvmDebugPort parameter to zero to maximize performance.
Warning: When the jvmDebugPort is enabled, a remote
user can connect to the integration node's JVM and inspect its behavior
and data, including potentially sensitive information. A remote user
can also exert control over the integration node's behavior. It is
therefore recommended that the jvmDebugPort is disabled on production
systems.
- If you used the mqsichangeproperties command to
configure the Flow Debug Port, you must use the Integration Nodes view in the IBM Integration Toolkit to attach the flow debugger
to the integration server. Right-click the integration server
with which you want to work, and click Launch Debugger,
and click OK to attach the debugger to
the selected integration server.
- Open the message flow that you want to debug in the Message
Flow editor by double-clicking its name in the Application Development view.
- Add a breakpoint to a connection that leads out of the
input node to ensure that the message flow does
not run to completion before you can begin to debug it.
- Switch to the Debug perspective.
- Right-click
the IBM Integration Bus Launch Configuration
in the Debug view, and click Edit
Source Lookup.
You can use Edit
Source Lookup Path to tell the debugger where to look for
your source files for message flows, and related resources such as
ESQL, message maps and Java during
debugging.
- Click Add, and select the type of
source to add to the lookup path.
The lookup path can be
an Eclipse project name, an external folder, or a compressed (.zip)
file. You can specify multiple locations, but the debugger always
looks first in the message flow project that you specify in the Edit
Source Lookup Path dialog.
- Select the resources to include in the lookup path, and
click OK.
- Click Add to include more resources
in the lookup path, click Up, or Down to
modify the order of the resources.
- Click OK to exit the Edit
Source Lookup Path dialog, and save your changes.
- When the next message comes into your flow and arrives
at breakpoint you added after the input node, the flow pauses, the
breakpoint icon is highlighted: , and you can start debugging.
- In the Debug view, double-click the message flow that you want to debug. The message flow opens in the Message Flow
editor. You can now add more breakpoints, start stepping over the
flow, and so on.
What to do next
Continue with one of the following tasks: