Building Distributed
Applications
Using the Progress AppServer


Using Remote Debugging

You use remote debugging to debug an AppServer application independently of the client application or to debug any AppServer application running in stateless operating mode. 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 4GL client application that might be driving the AppServer.

Because the Debugger is a 4GL debugger only, you must use remote debugging to debug AppServer procedures driven by Java or ActiveX Controller client applications.

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.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095