Hitachi

JP1 Version 11  JP1/Automatic Operation Service Template Developer's Guide 


8.1.3 Overview of debugging

Debugging is the process of using the Service Builder Debug window to check the operation of a service template you have built, and identify problems in its flow or plug-ins. When you debug a service template, a debug service and debug task are created. The debug process involves executing this debug task.

If debugging reveals a problem, stop debugging and then edit the affected service template or plug-in and then correct the problem.

Objective

Debugging is performed to make sure the flow and plug-ins of a service template are working as intended. For example, you can confirm that property mapping is configured correctly and that the flow branches as intended in the design based on the conditions for executing subsequent steps. In the Service Builder Debug window, you can:

Number of executions

You can debug a service template any number of times. If debugging reveals a problem with the service template, you must repeat the series of operations, from amending the development service template or development plug-in to building and debugging, until all problems are resolved.

Debug services

A debug service is generated and executed during debugging of a service template. One debug service is generated per service template. If you debug a service template that has already been debugged, JP1/AO deletes the previously generated debug service, and then creates a new one.

Note that debug services appear in the Service Name column in the Tasks window (Debug tab), but do not appear in the Services window.

Debug tasks

A debug task is generated for a debug service during debugging of a service template. If you debug a service template that has already been debugged, JP1/AO deletes the previously generated debug task, and then creates a new one.

Debug tasks appear in the Service Builder Debug window and Tasks window (Debug tab). Only users in the Admin or Develop role can view and work with debug tasks.

Note that debug tasks do not appear in the task summary.