Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Debugging with Mulesoft Anypoint Studio

Debugging with Mulesoft Anypoint Studio

Debugging with Mulesoft Anypoint Studio

Jitendra Bafna

May 27, 2017
Tweet

More Decks by Jitendra Bafna

Other Decks in Technology

Transcript

  1. Debugging With Anypoint Studio Anypoint Studio comes with Studio Visual

    Debugger which allows you to run the application in debug mode and stopping the execution to check the contents of previous building blocks. Debugging the Mule Application with Anypoint Studio is very easy. For running the application in debug mode first you need to set up breakpoint on building block. When application runs in debug mode, it stops immediately after executing the building block with breakpoint.
  2. Debugging With Anypoint Studio When debugging application on your local

    machine, Studio Visual Debugger listens for incoming connection on port 6666 and ensure that firewall is not blocking port. Set debug point on building blocks in your application by right clicking on studio component as shown below
  3. Debugging With Anypoint Studio In package explorer pane right click

    on your application, then select Debug As < Mule Application. Studio will start application in debug mode and displays the Confirm Perspective Switch window. Click Yes to confirm.
  4. Debugging With Anypoint Studio After enabling the application in debug

    mode, when message is sent to application and it will stop at first building block where breakpoint is set.
  5. Debugging With Anypoint Studio On the Left pane of Mule

    Debugger, you can see message payload and various other properties. Right pane displays various metadata associated with message like Inbound, Variables, Outbound, Session and Record. To go to next step of debugging, then click on Run to processor icon as highlighted in below snapshot.
  6. Debugging With Anypoint Studio To resume execution, click the Resume

    icon (see below) or press F8. Your application runs until the message reaches the next breakpoint, if any. For more details, Please go to MuleSoft Debugging Documentation.