8.3.3 Functions used during debug operations

Setting up debug tasks

You can specify the definition information of the debug service and debug task, the task log output level, and information about debug service properties.

8.3.5 Procedure for starting debugging

Setting up step execution

You can execute a debug task without pausing between steps (like execution of normal tasks), or by interrupting a step before and after processing of the plug-in. A combination of the following methods can be used for steps in a debug task.

• Do not stop after each step

  Like execution of a normal task, processing of the debug task proceeds without pausing between steps. You can check the execution results of the debug task and identify steps where problems occur.

• Stop after each step

  Execution of the debug task pauses before or after plug-in processing for a selected step. This allows you to check the property values and return values.

8.3.9 Operations for interrupting step executions during debugging

Skipping plug-in processing

You can skip plug-in processing and continue processing as if execution of the step has been completed.

8.3.11 Procedure for skipping plug-in processing during debugging

Checking property mapping settings

You can display the values of step properties in the Debug area. By viewing this information together with the service property values displayed on the Service Properties tab, you can check whether property mapping is configured correctly.

8.3.13 Procedure for checking property mapping settings during debugging

Changing information in a step

You can change a property value and return value of a step to any value.

• You can interrupt a step before the plug-in processing for that step is performed, and then change the values of input properties.

• After plug-in processing is skipped or executed, you can interrupt a step and then change the values of output properties or a return value.

8.3.14  Procedure for changing step property values or return value during debugging

Retrying tasks

You can use the following ways to retry a failed debug task:

• Resubmit

  You can execute the debug task as a new one without rebuilding it.

• Retry From Failed Step

  You can resume task execution from the failed step.

• Retry From Next To Failed Step

  You can resume task execution from the next step, as if the failed step had finished normally.

8.3.19 Procedure for debugging a service template again without rebuilding, 8.3.20 Procedure for retrying a task from a failed step during debugging, and 8.3.21 Procedure for retrying a task from the step after the failed step during debugging

Displaying flow information

You can use the following ways to display the flow of a debug task:

• Flow view

  In the Service Builder Debug window and Tasks window, you can view the status of steps and the flow transitions at each hierarchical level.

• Flow Tree view

  In the Service Builder Debug window, you can view flow hierarchies in tree format.

  You can also identify interrupted steps in each flow hierarchy.

8.3.22 Displaying debug task flow, 8.3.23 Displaying the flow tree of a debug task, 8.4  Managing debug tasks

Displaying task logs

The contents of the task log can always be displayed on the Task Log in the Service Builder Debug window. You can configure JP1/AO to automatically refresh and download the contents of the task log.

8.4.3 Procedure for checking task log entries for debug tasks

Managing debug tasks

You can do the following for debug tasks:

• Check the progress

• Check detailed information

• Stop execution

• Forcibly stop

• Delete

8.4  Managing debug tasks