Environment variables can be set in several ways:
- By adding options to the command line of the application executable
files.
- By editing the initialization file in use (enovia.ini on Windows).
- By editing the UNIX startup scripts that contain the variable settings
for locating the database and setting up the environment.
- By adding personal properties to a person object.
- By creating a program object called MatrixIniDefaults, which is designed
to set optional settings not set elsewhere.
- By creating a program object called MatrixSystemDefaults, which is
designed to set those variables that must be set consistently between
all users.
When 3DSpace needs to read the value for a variable
(with the exception of the variables needed before a connection to the
database is made), it checks if the variable is allowed to be set locally
(see Overriding Settings). If it can be, it looks until it finds the setting in the following
places:
- First for properties on the current context person object, if it can
be stored there (see Setting Personal Preferences).
If the person has a property of the same name as the desired environment
variable, its value is set.
- Next for the variable in the appropriate .ini file (enovia.ini) or
shell script. If found, its value is set.
- Next for a program in the database named MatrixIniDefaults. If it
exists and sets a value for the desired environment variable, its value
is set.
- In the case of a site preference, for the site on the group object.
If it cannot be locally set, its value is looked for in the Matrix System Defaults Program.
If not found there, it uses the default value.
Wherever they are set, variables must be spelled correctly and set
to appropriate values or they are ignored.