Tutorial: Working with Run Environments


The Developer allows the user to quickly test run the application in different environments. Running an application from the Developer has several advantages:

  • Quickly run the application in standalone or thin client mode
  • Define multiple run / debug environments that are immediately accessible from the toolbar
  • Create Control Center pages as a menu to application functionality
  • Run the application in normal or debug mode
  • Trace and debug dump files are conveniently placed in locally and remotely accessible areas.

Running the Application in Normal or Debug Mode

To run the application select pulldown Application / Run or the corresponding toolbar icon. Selecting the pulldown item or pressing the icon will run the application in the "Default" environment. The toolbar also provides a dropdown selection of alternate run / debug environments.

To run a specific application logic component, select pulldown Logic / Run or the corresponding toolbar icon in the Logic Editor.

Running Applications from the Control Center

You can also run applications or logic components from a page displayed in the Control Center. This allows the developer to setup menu pages of applications to test specific functionality not normally accessible from the application's user interface.

Use the following URLs: to launch applications:

  • bp://xdev?action=run&environment=Default&debug=False
  • bp://xdev?action=runlogic&environment=Default&debug=False&componenttype=Function&componentname=test

For more information see Using the Control Center.

Setting up Run Environments

The Developer is supplied with "Default" and "Alternate" run environment settings. It is easy to change or add new environment settings. The run environments are defined in the local developer profile (buildpro/bin/xdevprofile_user.xml). Edit this file to add additional run environments.

There are two run options; Application / Run and Application / Client to differentiate between standalone and thin client sessions.

  • Application / Run. Specify the parameters required to run the a BuildProfessional or other executable.
  • Application / Client. Specify details need to create a local .bpc file on the fly or specify an existing .bpc on your local system. If you specify a local .bpc file, then you can skip all other options.

Some options allow the use of keywords that will be parsed by the Developer:

  • %application%. The current application being developed.
  • %user%. The current user name.
  • %serverid%. The current Application Server (*SERVERID).
  • %riserver%. The current Developer Server.

NOTE. It is possible to configure programs other than BuildProfessional and launch them from the Developer.


To add another run environment, copy the complete settings of the Default environment (Common/Run/Application) and rename the @Environment attribute. Different run environments are used to test applications on different servers, using live or test datasets, running base or a selection of versions etc.

To use different DataPath settings, use alternate configuration files:

Run / Application / Arguments = "-uguest -a%application% -clivedata.ini"

To run a specific version, hard code the application:

Run / Application / Arguments = "-uguest -abphrx_infx"