Contents

Debugging

Debugging allows you to monitor a handler as it runs and to stop it at locations or situations of your choosing. You can set a breakpoint on a particular step, for instance, and let your handler execute until it reaches that step. If you are interested in the values assigned to a variable, you can have the debugger pause execution ("break") whenever the handler changes the variable's value.

When you debug a handler, you are viewing the handler in read-only format. When the handler runs on the server, it pauses whenever it reaches a Notify Debugger step or any step that has been set as a breakpoint. Handlers that do not contain any Notify Debugger steps will pause at the initiator. You can then establish other breakpoints in the handler and let the handler execute until it reaches the next breakpoint.

In Debug mode, the debug toolbar and debug palette appear to allow you to manage the debugging session.

Interaction Designer's Debug mode is closely integrated with the Interaction Processor to support debugging over a network. This allows you to run Interaction Designer on a client workstation to debug a handler even though that handler is actually executing on the server.

Prerequisites for debugging:

You must be running a copy of Interaction Designer connected to the server running the handler you want to debug.
The handler or subroutine you want to debug must be published and running (activated ) on the server.