8.3.4 Example of debugging service templates

When debugging a service template, users need to adjust various settings according to the aspects of the service template they want to check.

The following shows an example of the operations a user performs when debugging a service template.

This example describes the procedure for debugging a service template in the following scenario:

Problems with service template being debugged

Problem 1:: There is a problem with mapping settings between a service property and input property of Step A.

User objectives

Objective 1:: Check the execution results of other steps before amending the service template.
Objective 2:: If a problem is found in the property mapping, prevent processing of the plug-in in the step.
Objective 3:: Change the step property of Step B, and then check the results of processing of Plug-in B.
Objective 4:: Check the results of processing of Plug-in C.

Figure 8‒4: Example of debugging a service template

The debug task starts, and then Step A is automatically interrupted before processing of Plug-in A is performed. When Step A is interrupted, in the Debug area, check the value of step property Input A. Make sure that the value of service property Input 1 has been mapped correctly in the Service Properties tab.

This process allows you to identify the problem with the mapping settings of step property Input A (Problem 1).
A problem is found in the property mapping. Therefore, according to Objectives 1 and 2, you must skip the processing of Plug-in A to proceed with the debug task. In the Debug area, from the Debug Modes pull-down menu, select Run plugin in dry-run mode.
To change the step property value and perform processing of Plug-in B as described in Objective 3, click the Step Over button () to advance the debug task up to the point before the processing of Plug-in B.

Processing of Plug-in A is skipped and execution of Step A ends. Then, Step B is interrupted before the processing of Plug-in B is performed.
In the Debug area, from the Debug Modes pull-down menu, select Run plugin in execution mode.
Change the value of the input property of Step B.
In the Debug area, click the Resume button ().

After processing of Plug-in B is performed, Step C is executed according to the subsequent-step execution condition, and then the debug task terminates.
To meet Objectives 3 and 4, check the execution results of Steps B and C in the Debug area, flow area, and Task Log tab.
In the Service Builder Debug window, click Back to Editor.

The Service Builder Debug window closes.
In the Flow tab of the Service Builder Edit window, amend the property mapping settings for Step A.
Save the service template, and then debug the service template again.