5.3.4 Procedure for starting the debug process

When JP1/AO has successfully built the service template, you can begin the debug process. This involves selecting the break setting for debug service execution and setting the definition information for the debug service and debug task.

Note that schedule information is ignored during debug operations. All plug-ins are executed immediately.

To start the debug process:

1. From the Interruption Settings list box in the Perform Debugging dialog box, select the execution method for the debug task.

   To pause after each step as you execute the debug task, select Interrupt After Each Step. To execute the debug task without pausing between steps, select Do Not Break.

2. Set the definition information for the debug service. For details about the parameters you can set in the Perform Debugging dialog box, see 5.3.5 Settings used when beginning the debug process.

3. Click the Run button.

   The Debug view and the service template debugging view appear in the Editor window, and the debug task is executed.

4. If you select Interrupt After Each Step as the break setting, execution of the debug task pauses after each step. You can resume execution of the task by clicking Rerun in the Debug view.

Important note

• The break setting governs whether execution of the debug task pauses between steps. If you want to check the execution results of each step as you go, or the task contains plug-ins you do not want to execute at that time, select Interrupt After Each Step as the break setting.

• The Perform Debugging dialog box shows the service template as it was configured when last built by the current 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.

  • The user logs out of JP1/AO.

• Closing your Web browser during the debug process does not stop the debug task. If you close your Web browser, processing of the debug task continues until reaching a point where it would normally stop. If you have configured JP1/AO to break between each step of the debug task, processing of the debug task remains paused indefinitely at the current or succeeding step. If this occurs, the user needs to log in again and stop the debug task from the Debug-Tasks view of the Tasks window. The Debug view and the service template debugging view do not re-appear. To execute the debug task again, you need to rebuild the service template and restart the debug process.

• If another user builds the same service template in the period of time after you build the service template but before you begin the debug process, an error occurs after you click Run 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 at one time and what happens when the number exceeds this limit, see Maximum number of plug-ins contained in a task that can be executed concurrently in the Job Management Partner 1/Automatic Operation Administration Guide.

• The status of debug tasks is subject to JP1 event reporting and email notification.

Related topics

• 5.3.2 Functions used during debug operations

• 1.1.3 Main windows used to develop service templates

• 5.2.1 Procedure for building a service template

• 5.3.1 Flow of service template debugging

• 5.3.7 Flow of debug process without pausing between steps

• 5.3.8 Flow of debug process when pausing between steps

To Page Top