When message flow processing has paused at a breakpoint
that you have set in source code within a node that contains Java™ code, you can examine and modify
the Java variables in the Flow
Debugger.
Procedure
- To open the Command Console, click .
- Start the integration node by running the mqsistart command in the Command
Console.
- Check that the Java debug
port is set by running the mqsireportproperties command
(all on one line) in the Command Console:
mqsireportproperties integrationNodeName -e integrationServerName -o ComIbmJVMManager -r
For example:
mqsireportproperties TEST -e default -o ComIbmJVMManager -r
- Set the Java debug
port by running the mqsichangeproperties command
(all on one line) in the Command Console:
mqsichangeproperties integrationNodeName -e integrationServerName
-o ComIbmJVMManager -n jvmDebugPort -v port_number
For example:
mqsichangeproperties TEST -e default
-o ComIbmJVMManager -n jvmDebugPort -v 3920
- Stop and restart the integration node by running the mqsistop and mqsistart commands.
- 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 where the Java method
is called, by following the instructions in Adding breakpoints in the flow debugger.
- To step directly into the Java code
during the debugging process, add a breakpoint in the Java code.
- Deploy the BAR file
that includes the JAR file that contains the Java code, by following the instructions in Deploying integration solutions to a production environment.
- Click to open the Debug wizard.
- Right-click Debug in the list of
elements on the left and click New.
- Set the Java Debug Port with the
same value that you specified for the -v parameter
on the mqsichangeproperties command,
and click Apply to save your changes.
- Click the Source tab, specify the
source file location, and click Apply to save
your changes.
- Click Debug to start the debug process.