By the term "INI application file" it is meant the INI
file located in the application folder with the same name as the PRA
file. For example, if the application file is named "BoilerPlant.pra"
, then the PROMOTIC system creates the "BoilerPlant.ini"
The application INI file can be edited as a plain text file. It can also beopened and edited directly in the PROMOTIC system in the menu " > Edit application ini file".
Basic settings are being stored in the INI application files that are necessary for the development environment or runtime environment. The basic useful parameter settings description can be found below.
Description of keys in the [Promotic] section
Global parameter settings of the application are located in this section.
runtime is not running, =1
runtime is running. It is used for setting the pEvent.Reset
parameter in the PmaRoot.onAppStartBegin
event. User modification of this parameter is not allowed, it can only be set by the PROMOTIC system.
(default: 0). Time delay in seconds of the PROMOTIC application launch. This setting is used if the runtime PROMOTIC application is depending on other programs (databases, communication server, etc.). It prevents the PROMOTIC application to be launched before necessary software is running thus avoiding errors.
For another option of launch delay: see RunLater program.
In case an error occurs in the application, the error description is always registered in the INFO system
in the Errors
item. By this setting it is possible to achieve that the error (repeated error too) is recorded into the Debug item of the INFO system
=0 (default) - the error is not recorded
- the error is recorded into the "Debug1
- the error is recorded into the "Debug2
(default: 0), Enable/disable the possibility of running one application more than once simultaneously. It means that the PRA
file is released after the application is loaded (option available while running the runtime key only).
System names verification (names of objects and names of variables in data objects):
=1 (default) verification
=0 no verification. Can be set only exceptionally for existing applications where non-system names are already present.
(default: 10) Specifies the maximum waiting time for finishing communication with the Web server in seconds. The system waits until the IP address is obtained from domain name, then waits for the established connection with the Web server and than waits for the reply from Web server.
Description of keys in the [Licence] section
In this section, there are the parameters of license carrier settings, see PROMOTIC licence carrier types
: This key contains the list of license carriers. The data is separated by "comma" character (,
). The license is searched in the license carrier list from left to right. The first license found is used. If the key is not specified, then the default setting Medium=hwkey
is used, in order to read the possible license from Hardware (USB) licence key
- The license carrier is Hardware (USB) licence key
or License file SWK extending the content of license key
. It is also possible to specify the license type (development/runtime), or even refer to an individual license (by license number). This way you can first search for development license (or specific individual license) and after that load the runtime license or network runtime license (or another defined sequence) etc. This way you can solve the situation when the application uses the runtime license by default (from any carrier), but if you connect the development HW Key the application will use the development license preferentially.
=hwkey - Key with development or runtime license (not further specified).
=hwkey:dev - Key with development license.
=hwkey:rt - Key with runtime license.
=hwkey:k-XXXX - Key with license number other than XXXX.
- Key with license number XXXX. This is the only functional option for reading hardware key via local PmLicServer
. This option is preferred especially for solving the RDP problem. It can also be used for direct reading of the licence. This is recommended option for applications with runtime licence in hardware key.
- The license carrier is Network licence key
. For example: netkey:http://192.168.1.2:5656/Pm1234.swk
Several examples of sequential available license search:
This key defines whether the licence carrier hwkey
will be read directly
or via the local PmLicServer
will be read directly
Description of keys in the [InfoSystem] section
It can be set the method of saving the state of the INFO system
in this section. If the StoreType
key value is set to 2 or 3 (i.e. saving enabled), then the new keys with the state values of the window are created in this section when closing the INFO system window. The position and the size of the window, the refresh rate of the INFO system
and the last viewed page including column widths are being saved.
The [InfoSystem] section with the key StoreType=0 is created automatically when opening the INFO system for the first time (if this key has not been included there previously).
: Specifies whether additional keys can be read and saved in this section:
=0 reading and saving is disabled
=1 only reading the settings from the INI file is enabled
=2 only saving into the INI file is enabled
=3 reading and saving is enabled
Other keys of this section are reserved for storing the system state values; these are created automatically and will not be described here.
Description of keys in the [Log] section
It can be set the parameters for application "logging"
in this section. It means that the application logging mode can be activated, causing that certain operations will always be written to disk into the Application.log
text file" (for example if there is the "BoilerPlant.pra"
project, then the logs go into the "BoilerPlant.log"
file). It is recommended to activate this mode while developing the application, in order to have an overview of the development progress and more detailed information about the software crashes, etc. It is recommended to switch the logging mode of the application to default values (i.e. one key: EnableBase=2
) for common continuous operation.
The PROMOTIC system only reads the key values in this section, not setting any. In order to enable the logging options the section must be created and the keys set by the designer manually.
: Size of the log
text file in kB (default 1000). If the size of the log
file reaches this value, then the original file "Application.log
" is renamed to "Application.log.old
" and new empty file "Application.log"
is created while the application is being launched. This is a simple security procedure preventing the unlimited growth of the log
=0 the log file is not closed after writing a record
=1 the file is not closed after writing, but a flush is done (i.e. data is stored from the memory buffer to disk)
=2 (default) the file is closed after each writing
This is a simple way of data writing optimization because some settings may allow writing of large record volumes.
=0 All logging disabled
=1 Logging enabled (i.e. log according to setting EnableGlobErr, EnableDebug, EnableObject)
=0 Global error logging disabled
=1 (default) Logging only new errors (i.e. only errors appearing for the first time)
=2 Log all global errors (not recommended for continuous operation because the records may grow continually resulting in unlimited size of log files)
It is also possible to set error loging into the Debug item of the INFO system simultaneously. See ErrRedir key in Description of keys in the [Promotic] section for more details.
" page logging
" page logging
=0 disabled (default), otherwise sum of values:
=1 when object is created (i.e. when object is read from a pra file and created in PC memory)
=2 when object closes (i.e. when object is removed from PC memory)
when object is started in the runtime mode - when the onStart
when object is stopped in the runtime mode - when the onStop
=0 SQL query logging forbidden (default), otherwise the value 1 or a sum of 2, 4 or 8:
=1 log SQL queries of all components
Description of keys in the [Info] section
In this section the most important information about the application and the PROMOTIC version can be found. The most important info listed in this section is the PROMOTIC version used for running the application for the last time. When looking into the application backup file you can see the PROMOTIC version used for creating this backup. It is handy also for the remote connection to existing application (e.g. by means of the VPN
) or if multiple applications are running simultaneously on one PC in different PROMOTIC versions See: How to find PROMOTIC version
The information in this section are to be considered only as general information, generated each time the application is launched. Possible modification of this info does not affect the application.
AppLastRunVer: The PROMOTIC version used last time for launching the application.
AppLastEditVer: The PROMOTIC version the application was last edited with.
AppLastEditTime: Date and time, when the application was last edited.
AppCreatedVer: The PROMOTIC version used for creating the application (this value is permanent in each application).
The sections [MainFrame]
, etc. contain parameters setting for the development environment (size of adjustable windows, etc.), runtime environment, fonts, etc.
Changing these keys is not recommended and therefore not described here.