Using remote debugging

You use remote debugging to debug an AppServer application independently of the client application. With remote debugging, the Debugger does not have access to the client application that calls remote procedures in the AppServer session. When viewing the procedure call stack associated with a debugging session initiated in this mode, you never see procedure call stack entries for any ABL client application that might be driving the AppServer.

Because the Debugger is an ABL debugger only, you must use remote debugging to debug AppServer procedures that are driven by .NET and Java Open Client applications or that are invoked as OpenEdge Web services.

You must also use remote debugging if you want to step through code in any of the AppServer configuration procedures that you specify in the AppServer properties file (ubroker.properties). These include the:

The Debugger does not have access to these procedures with distributed debugging.

You can initiate a remote debugging session in one of two ways:

This section describes the basic tasks required to initiate remote debugging. For more information on detailed debugging tasks, such as using the Debugger window to step through code and exiting the Debugger process, see OpenEdge Development: Debugging and Troubleshooting.

For information about using the Progress Developer Studio for OpenEdge Debug perspective for remote debugging, see the Progress Developer Studio for OpenEdge online help.