How OpenEdge creates or reuses a configuration

Although you can explicitly select an existing launch configuration to run or debug a program, in many cases, the easiest approach is simply to click Run or Debug with focus on the desired startup item. (In most cases, clicking the button produces the same result as opening the menu and selecting Run As or Debug As.)

When you choose one of these options, OpenEdge determines whether a suitable configuration already exists, and if so, runs that configuration. If a suitable configuration does not exist, OpenEdge creates and runs a new configuration. The basis for identifying a suitable configuration depends on whether the selected item is an ABL source file or an AppServer or WebSpeed instance.

For an ABL program

To determine whether to use an existing configuration to run or debug an ABL program, OpenEdge performs the following tests in sequence:

If multiple existing configurations satisfy a test, you are prompted to choose one of those configurations.

If both tests fail, OpenEdge creates and runs a new configuration with default settings. You can edit this configuration as appropriate.

For AppServer and WebSpeed instances

To determine whether to use an existing configuration to run or debug an AppServer or WebSpeed instance, OpenEdge looks for a configuration specifying that server. If such a configuration exists, OpenEdge uses it to start the AppServer or WebSpeed server. (OpenEdge automatically creates a default launch configuration when each AppServer or WebSpeed instance is defined, so a server has at least one launch configuration unless you delete it.)

If multiple configurations specify the same server, the one that was defined first is used.

If no configuration exists for the specified server, Progress Developer Studio for OpenEdge creates and runs a new configuration with a name matching the server name.