Debugging WebSphere Message Broker flows in MB6

Step 1:- Assign debug port to execution group and enable debugging

You need to assign a debug port to the execution group you want the debugger to attach to and enable debugging. Please remember that this can constitute a security vulnerability since the debug port should be accessible from outside.

Step 2:- Next you should enable debugging;

Step 3:- Go to tthe command console and shoot;

mqsichangeproperties <broker-name> -e <execution-group-name> -o ComIbmJVMManager -n jvmDebugPort -v <port-number>

Step 4:- Restart the broker

Step 5:- Restart the broker toolkit

Step 6:- Create debug configuration

Create a new debug configuration by going to Debug… / Message Broker Debug / Add…

In the new configuration first click the “Select Execution Group…” which will result in the broker toolkit to query execution groups previously configured to discover the ones which have debugging enabled. Choose the execution group you have configured. Enter the debug port you have picked and add the Source folder to the debug configuration.

Step 7 :- Add breakpoints to you flow and use the debug configuration you have created to debug your flows.