Did this article resolve your question/issue?



How to use the debugger to step into code on PASOE?


TitleHow to use the debugger to step into code on PASOE?
URL Namehow-to-use-the-debugger-to-step-into-code-on-pasoe
Article Number000116254
EnvironmentProduct: OpenEdge
Version: 11.7
OS: All Supported Platforms
Question/Problem Description

Is it possible to step into a Progress AppServer (PAS for OE) using the OpenEdge Debugger?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
In OpenEdge 11.7 debugging support for PAS applications was introduced for PASOE development environments using the oedbg.war to debug application problems.

It is possible to debug code running on Progress AppServer for OpenEdge only when running from a development environment.  Unlike the classic AppServer which provides the ability to either instantiate an instance of the Standalone Debugger directly from the executing AVM or to attach the Standalone Debugger remotely to an executing AppServer process that is enabled for debugging.

To debug on PASOE you have to start the AppServer from Developer Studio (PDSOE) using a Debug Configuration, and all debugging is done from within the Debug Perspective of PDSOE.

Steps (Note that these instructions assume that debugging has already been enabled using proDebugEnable as a machine Administrator):
  • First shut down your Progress AppServer instance.  It must be started using the below steps in order for the debugger to be effective.
  • Open a program that you're trying to debug and set a breakpoint in it by double-clicking along the left-edge of the line you wish to begin debugging on.  This will show a little dot (.) to the left of the line if you've successfully set a breakpoint.  (See below)
User-added image
  • From the Developer Studio menu, select "Run >> Debug Configurations".
  • Expand the "Progress Application Server for OpenEdge" node in the left pane and select your OE PAS instance
  • Set the appropriate properties on the property sheet (Documented at: and click Debug to start the AppServer.
  • Once the AppServer is finished starting, send a request to the AppServer and Developer Studio will switch you to the Debug Perspective when the breakpoint is encountered.
Last Modified Date7/24/2018 7:13 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.