Back to Contents

The FGLPROFILE configuration file

Summary:

• Basics
• FGLPROFILE Entry Syntax
• Supported Entries

See also: Programs

Basics

The runtime system uses one or more configuration files in which you can define entries to change the behavior of the programs.

There is no specific naming convention for the configuration files, however, we recommend to use an extension such as prf.

There are three different ways to specify the configuration file, with the following order of precedence:

1. By default, the runtime system reads the configuration file provided in FGLDIR/etc/fglprofile. This file contains all supported entries, identifies the possible values for an entry, and documents default values.
2. If the FGLPROFILE environment variable is set, the runtime system reads entries from the file specified by this environment variable.
3. If the program-specific profile directory contains a file with the same name as the current program, the runtime system reads the entries from that file. By default, the program-specific profile directory is FGLDIR/defaults. This directory can be changed with the fglrun.defaults entry in one of the previously mentioned configuration files (FGLDIR/etc/fglprofile or the one defined by the FGLPROFILE environment variable).

FGLPROFILE Entry Syntax

Purpose:

An FGLPROFILE entry is a parameter that can be changed in the configuration file.

Syntax:

Notes:

1. entry identifies the name of the entry.
2. value is the value of the entry; it might be a numeric value, a string literal, or a Boolean value (true/false), depending on what is valid for the entry.

Warnings:

1. Entry names are converted to lower case when loaded by the runtime system. In order to avoid any confusion, it is recommended to write FGLPROFILE entry names in lower case.
2. If an entry is defined several times in the same file, the last entry found in the file is used. No error is raised.

Usage:

The entries are defined by a name composed of a list of words separated by a dot character.

By using names like domain.sub-domain.param, entries can be organized by domains and sub-domains.

The value can be a numeric literal, a string literal, or a Boolean (true/false).

Numeric values are composed by an optional sign, followed by digits, followed by an optional decimal point and digits:
[-|+]{digits}[.digits]

String values must be delimited by double quotes. The escape character is backslash:
"characters"

Boolean values must be either the true or false keyword:
{true|false}

If an entry is defined in different levels of configuration files (default/specific/program), the runtime system searches for the entry value in the following order:

1. Program (FGLDIR/default/progname)
2. Specific (file specified by the FGLPROFILE environment variable)
3. Default (FGLDIR/etc/fglprofile)

For more details about supported entries, see Supported Entries.

Example:

01 rtm.memory.cachelocals = true
02 rtm.default.logfile = "mytrace1.log"
03 rtm.installation.path = "C:\\progra~1\\fourjs\\fgl"
04 dbi.database.stores.prefetch.rows = 200

Supported Entries

The following table shows the a partial list of supported FGLPROFILE entries. You can find the complete usage for an entry in the corresponding documentation section referenced in the description of the entry.