8.3.5 Procedure for starting debugging

If the build process of a service template is successful, you can start debugging. To do this, you must specify the definition information for the debug service and debug task, task log output level, and debug service property information.

Note that schedule type is set to immediate execution when debugging is performed.

To start debugging:

In the Perform Debugging dialog box, specify the definition information for the debug service and debug task, task log output level, and debug service property information.

To specify properties, from the Edit pull-down menu, select From Create Service Window or From Create Request Window, and then specify the properties in the window that appears. You can also read properties from the property file.

Figure 8‒5: Perform Debugging dialog box
Click OK.

Operation results

The Service Builder Debug window appears, and then execution of the debug task starts.

After the debug task starts, the first step is interrupted before processing of the plug-in for that step is performed. You can resume execution of the step by clicking Resume in the Debug area.

Important

The Perform Debugging dialog box shows the status of the service template when it was built the last time by the current debugging user. If another user edits and builds the same service template after the debugging user, the changes do not apply to the contents of the service template shown in the Perform Debugging dialog box.
A debug task is forcibly terminated in the following circumstances:

• The JP1/AO server stops.

• Failover to another node in a cluster system occurs.
If you close your Web browser during the debugging, the debug task is interrupted, and you will be unable to execute subsequent processing. In this case, you need to log in again and stop the debug task in the Debug area of the Tasks window. Note that the Service Builder Debug window you closed does not re-appear. To execute the debug task again, you need to rebuild the service template, and then restart debugging.
After you build the service template, if another user builds the same service template before you start the debugging, an error occurs when you click OK in the Perform Debugging dialog box.
A single JP1/AO system can execute a maximum of 10 plug-ins concurrently in a debug task. For details about the maximum number of plug-ins that can be executed concurrently and what happens when the number exceeds this limit, see Maximum number of concurrently executable plug-ins in a task in the JP1/Automatic Operation Administration Guide.
The status of debug tasks is subject to JP1 event reporting and email notification.