Runtime configurations
Introduction to runtime configurations
menu Maintenance > Runtime configurations
The Runtime configurations screen provides an overview of your personal runtime configurations for the selected project version.
Runtime configurations can have different databases, extended properties, and file storage locations than the default configuration. Settings that deviate from the default configuration are shown in bold.
A runtime configuration provides the environment in which an application is started, defined by the database server and database of the application. By specifying multiple runtime configurations, the same application can be started on multiple environments, for example for development and testing purposes. The runtime configuration to be used is specified in the configuration file.
Runtime configuration overview
Active runtime configurations per user
The user interfaces provide the option to switch between active runtime configurations using the application selector. When a runtime configuration is active, its project and version are available in the project version selector in the ribbon under My projects.
menu Maintenance > Users > tab Runtime configurations
In this screen, the Active checkbox indicates whether or not the runtime configuration is activated for the current user.
- Universal GUI Indicium - Runtime configurations need to be activated or de-activated per user. When running applications in development directly in the Software Factory, only the active runtime configurations are loaded for the logged-in user.
- Windows GUI Web GUI - These GUIs will load all active runtime configurations when no project, project version and runtime configuration are specified in the INI file.
- Windows GUI To automatically load a runtime configuration when starting the Windows GUI on the Software Factory without a project version, you must select the Active checkbox.
Active runtime configurations per user
The order in which active runtime configurations are shown can be modified here as well.
Runtime configurations for other users
menu Maintenance > Runtime configurations > tab Other users
Runtime configurations contain personal settings. The Active checkbox does not affect the other users' settings.
In the Other users tab, you can enable or disable a runtime configuration for other users. You cannot add new users in this tab. This can be done in Maintenance > Users > tab Runtime configurations.
The Runtime configurations detail tab shows the active and inactive runtime configurations for the selected user. Note that the RDBMS user name equals the IAM user name.
To display the users currently not involved in the development process, de-select the Active users 
prefilter.
Application ID and Alias
The Mobile user interface only loads one runtime configuration. To connect to the Indicium application tier, the Mobile user interface needs to provide the Application ID or Application Alias of the runtime configuration:
menu Maintenance > Runtime configurations
Setting the runtime configurations' application ID or alias
Role simulation
menu Maintenance > Runtime configurations
Developers can choose to simulate a role. This can be set in the Runtime configurations screen at Personal settings or at the overview of runtime configurations per user. When the application is started or the model is refreshed, the rights of this role will be applied.
While this setting is configurable in the Runtime configurations screen, this setting will affect all runtime configurations of this user for a project version.
File storage location type for a runtime configuration
For each runtime configuration, you can configure the base file storage location type:
menu Maintenance > Runtime configurations > tab File storage locations
- Execute task Switch file storage locations type
to select another location type.
Override OAuth servers
For OAuth process actions, an OAuth server is configurated in menu Projects > Project overview > tab Project versions > tab OAuth servers. To override these settings for development or testing:
menu Maintenance > Runtime configuration -> tab OAuth servers
