WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Attaching the flow debugger to an execution group for debugging

Before you can debug your message flow, you must attach the flow debugger to the execution group where your flow is deployed, then start a debugging session.

Before you start:

From a single WebSphere® Message Broker Toolkit, you can attach the flow debugger to multiple execution groups that are running on the same or on different host computers, and debug their flows (and therefore multiple messages) simultaneously.

An execution group can be debugged by only one user at a time. If you attach your debugger to an execution group, another user cannot attach a debugger to that same execution group until you have ended your debugging session.

To attach the debugger to an execution group:

  1. Set a Flow Debug port number. To configure the broker JVM with a debug port number, use one of the following methods:
    • In the Brokers view in the WebSphere Message Broker Toolkit, right-click the execution group with which you want to work, and click Launch Debugger. Click Configure, and enter a port number. Click OK to enable debugging on the selected port, and attach the debugger to the selected execution group.
    • In the WebSphere Message Broker Explorer, right-click the execution group with which you want to work, and click Properties. Enter a port number in the Flow Debug Port field on the Extended page, and click OK to modify the Flow Debug port number. You must right-click the execution group and click Flow Debug Port > Enable to enable debugging on the selected port.
    • Set the Java™ debug port by running the mqsichangeproperties command (all on one line) in the Command Console:
      mqsichangeproperties broker_name -e execution_group_name 
      -o ComIbmJVMManager -n jvmDebugPort -v port_number
      For example:
      mqsichangeproperties TEST -e default 
      -o ComIbmJVMManager -n jvmDebugPort -v 3920
      When this command completes, restart the broker. See: Starting and stopping a broker.
    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 broker's JVM and inspect its behavior and data, including potentially sensitive information. A remote user can also exert control over the broker's behavior. It is therefore recommended that the jvmDebugPort is disabled on production systems.
  2. If you used the mqsichangeproperties command or the WebSphere Message Broker Explorer to configure the Flow Debug Port, you must use the Brokers view in the WebSphere Message Broker Toolkit to attach the flow debugger to the execution group. Right-click the execution group with which you want to work, and click Launch Debugger, and click OK to attach the debugger to the selected execution group.
  3. Open the message flow that you want to debug in the Message Flow editor by double-clicking its name in the Broker Development view.
  4. 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.

    The breakpoint appears as Enabled breakpoint. For information about adding a breakpoint, see Working with breakpoints in the flow debugger.

  5. Switch to the Debug perspective.
  6. Right-click the Message Broker 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.
  7. 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.
  8. Select the resources to include in the lookup path, and click OK.
  9. Click Add to include more resources in the lookup path, click Up, or Down to modify the order of the resources.
  10. Click OK to exit the Edit Source Lookup Path dialog, and save your changes.
  11. 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: Enabled paused breakpoint, and you can start debugging.
  12. 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.

Next:

Continue with one of the following tasks:

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:03


Task topicTask topic | Version 8.0.0.7 | ag11186_