webMethods Integration Cloud and Cloud Deployment Documentation 6.0.0 | webMethods Integration Cloud | Integrations | Debug Integrations
 
Debug Integrations
You can debug an orchestrated Integration and can inspect the data flow during the debugging session. You can debug an orchestrated Integration only in the Development stage and after the Integration has been saved.
You can do the following in debug mode:
*Start an Integration in debug mode, specify the input values, and inspect the results.
*Examine and edit the pipeline data before and after executing the individual blocks.
*Monitor the execution path, execute the blocks one at a time, or specify breakpoints where you want to halt the execution.
To start the Debug mode, click the Debug Integration icon .
The following table describes the options available in the Debug panel:
Icons
Applicable for...
Action/Description
Inserting Breakpoints
A breakpoint is a point in an Integration where you want processing to halt when you debug that Integration. Breakpoints can help you isolate a section of code or examine data values at a particular point in the execution path. For example, you might want to set a pair of breakpoints before and after a particular block so that you can examine the pipeline before and after that block executes.
Breakpoints are recognized only when you execute an Integration in debug session. To insert a breakpoint, in debug mode, click the top-left corner of the block. To remove a breakpoint, click on the inserted breakpoint.
When you execute an Integration that contains a breakpoint, the Integration is executed up to, but not including the designated breakpoint. At this point, processing stops and the debug session suspends. To resume processing, select Resume. After you resume the debug session, the Integration flow stops at the next breakpoint.
Ignore All Breakpoints
Ignores all breakpoints inserted in the Integration blocks. You cannot insert breakpoints for variables in the Expressions category.
Stepover
Executes the current block. Integration Cloud suspends the debug session immediately before executing the next block in the Integration.
Resume
The debug session resumes but suspends at the next breakpoint.
Stop
Terminates the debug session.
A debug session may also stop by itself for the following reasons:
*The Integration that you are debugging executes to completion (error or success).
*You select Stepover for the last step in the Integration.
*You Exit the Integration.
Clear All Breakpoints
Removes all breakpoints inserted in the Integration.
Modifying the current pipeline data while debugging
During debugging, you can modify the contents of the pipeline. The changed values will be applied when you perform a Stepover or Resume.
While modifying the pipeline, keep the following points in mind:
*You can modify the pipeline data only during an active debug session.
*When you modify values in the pipeline, the changes apply only to the current debugging session. The Integration is not permanently changed.
*You can only modify existing variables. You cannot add new variables to the pipeline.
Copyright © 2014- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.