As when attaching to any ABL session, to attach the Debugger to an AppServer session, you must first make the AppServer agent debug-ready in one of the following ways:
Use the -debugReady startup parameter for starting the agent
From the command line, run the proDebugConfig tool
From a Debugger session, use the Make-ready and attach option in the Attach to Process dialog box
For any method other than using the -debugReady startup parameter, you must identify the AppServer agent you want to debug by its process ID. For many debugging situations, you can configure the AppServer to run only one agent at a time, and there by eliminate any need to choose among them.
Attaching to an AppServer agent presents the same Debugger user interface as when you connect to a client process. The one difference is that there are times when an AppServer is not executing any code. In this case, the Debugger indicates that it is waiting for an AppServer request before it takes control on the first executable line of ABL code.
For more information on remote debugging by attaching the Debugger to an AppServer session, see OpenEdge Development: Debugging and Troubleshooting.
For information on remote debugging by attaching the Progress Developer Studio for OpenEdge Debugger to an AppServer session, see the Progress Developer Studio for OpenEdge online help.
Use the -debugReady startup parameter for starting the agent