The distributed debugging allows you to debug several associated ABL sessions within a distributed application environment. That is, one debugger session, running in one session within the distributed environment, controls the debugging process for all sessions associated with it. The procedure call stack reflects all procedures in all sessions involved, enabling the root client application to be aware of the AppServer sessions that it is debugging. The root client application is the client application that initiates the Debugger using distributed debugging.
You can use distributed debugging on AppServers running in all operating modes except the state-free operating mode.
You can run the Debugger using distributed debugging to debug local procedures, remote procedures, and remote procedures executed by other remote procedures. An AppServer agent that is once, twice, or further removed from the initial debugger session can be debugged in this manner. More information on this debugging mode follows in later sections.
