Running the debugger

Ops Center Automator Service Builder User Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99AUT002-18

After successfully building a service template, you can run the built-in debugger by accessing the Perform Debugging dialog box and then clicking OK. Before accessing the debug interface, you must specify the details for the debug service and tasks in the Perform Debugging dialog box. You can also verify and edit the service properties or make changes from the Create Service or Create Request windows.

You can use the built-in debugger to make sure the plug-ins and flow of a service template are working as intended. During a debugging session, you can:

  • Control when to run steps in the flow of a service template to isolate and correct any problems.
  • Run and manage debug tasks while verifying the flow transitions at all hierarchical levels.
  • Confirm that property mapping is set correctly and that the conditions for running subsequent steps flow as intended.
  • Modify input and output properties for currently running tasks.
  • Set breakpoints to enable the processing to start from or end before a specified step in the flow.
  • Skip the processing of specified plug-ins (script/command, repeat, wait for user response) so that it appears to the next step as though the process of the plug-in has run, which allows the flow to continue according to the condition of the next step.
  • Display the results of a repeated-execution flow (for each execution time).
  • Consult a running log of running tasks.
  • Edit entries in the Create/Edit Service and Submit Service Request windows to simulate service template processing.
  • If you detect an problem with a plug-in, you can assign an arbitrary property value or return value to the plug-in and run the plug-in again. This allows you to see how the plug-in processing and flow transitions are effected when you change a specific property value or return values.

You can debug a service template multiple times.

When you debug a service template, Ops Center Automator creates a debug service and debug task.

Debug service

A debug service is a service that is generated and run when you debug a service template. One debug service is created per service template. When you debug a service template that has already been through a debug process, Ops Center Automator deletes the existing debug service and creates a new one. The debug services appear in the Service column in the Tasks - Debug view, but do not appear in the Services window.

Debug task

A debug task is a task generated for a debug service when debugging a service template. When you debug a service template that has already been through a debug process, Ops Center Automator deletes the existing debug task and creates a new one. Debug tasks appear in the service template Debugging view and Tasks - Debug view. Only users assigned the Admin or Develop role can view and work with debug tasks. Debug tasks do not appear in the task summary.

Note: You cannot edit service template or plug-in definitions from the debugger view. Instead, when you detect a defect during debugging, you must stop debugging and return to the Service Builder Edit window to make the required correction.

Limitations on concurrent debugging procedures and associated tasks

A maximum of one debug service and one debug task can be generated for the same service template, and the same service template cannot be debugged by multiple users at the same time. The same service template cannot be edited by multiple users at the same time (because the last save action for the template takes precedence, which means that multiple problems cannot be fixed at the same time).

If a debug service and a debug task already exist for a service template that is being debugged, when you run the build or release process, the debug service and debug task are deleted automatically, and a new debug service and debug task are created when debugging re-starts.

After the debug task finishes, if you start debugging again without first closing the Debugger view, the created debug service and the finished debug task are deleted automatically and a new debug service and debug task are generated.

A Developing version of the service template to debug must have successfully completed the build process.

Follow these steps to start a debugging session:

  1. Enter the details from the Perform Debugging dialog box.
  2. For the Service Name field, accept the original name appended with [DEBUG] or specify another name of your choosing.
  3. Verify and, if necessary, modify the details for the other service and task related fields
  4. For the Task Log Level, specify the level of details to store in the task log file.
  5. If necessary, you can supply the values that are normally specified by the user who is configuring and submitting the service by accessing the Edit menu and selecting either From Create Service window or From Create Request window.
  6. Click OK to access the debugger user interface.
The debug interface opens where you can begin the debugging process.