Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
The ability to save a modified system configuration through the UI makes use of the INDEX file. When
the UI is used to make modifications to the system configuration, Ignite-UX produces a "delta" configura-
tion file that represents the changes. When this delta configuration file is appended to the list of default
configuration files, it overrides the defaults with the values you specified. When a system configuration is
saved with a new name, a new INDEX configuration clause is created that contains the original configura-
tion files with the addition of the new delta configuration file.
Any information stored in the first 8KB of the *INSTALLFS file, as well as the client-specific configura-
tion file, is always appended to the list of configuration files, although is not explicitly listed in the INDEX
file set.
INDEX File Content and Syntax
The INDEX and CINDEX files contain configuration clauses, and may also contain a list of scripts that are
available for scheduling in the "Advanced" tab of the UI.
The INDEX file syntax is of the form:
cfg "tag_string_1"{
description "description_text"
"config_file_path_1"
"config_file_path_2..."
}
cfg "tag_string_2"{
description "description_text"
"config_file_path_1"
"config_file_path_2..."
} = true | false
scripts {
"script_file_path_1"
"script_file_path_2"
}
In the above example syntax, the cfg keyword is used to specify a group of configuration files. The
tag_string is displayed in the UI selection list, and must be 80 characters or less. The description keyword
supplies additional information the UI may display to further describe a selection. After the closing brace,
the cfg clause may be selected or unselected using the = true|false syntax. A setting of = true is
used to select a particular configuration as the default.
Only one cfg clause may be selected as the default. The last clause that is selected will cause all other
clauses to be automatically unselected. See the EXAMPLES sections on how to set up a cfg clause to be
conditionally selected.
The scripts keyword is used to specify a list of file paths to scripts that may be selected and scheduled
to run at the end of the client install. (See the description of the post_config_script keyword for
more details.)
General Configuration File Structure
The configuration file is a free-structured file in which white space is optional but may be used to improve
readability. The # character is used to designate a comment line that extends from the # character to the
end of the line.
Some keywords require string arguments. Most keywords that take a string argument may also take a com-
plex string which is a concatenation of strings, variables and system attributes. See the following descrip-
tions for details.
All keywords in the configuration file may be either all lowercase or all uppercase, but not a combination.
Variable and use-model identifiers are case sensitive.
Most keywords, and all variables, that use the = assignment operator will also accept the += operator,
which appends the given value to any value that the keyword/variable currently holds. The += operator
has the same effect as = when it is the first assignment. Using the += operator on an integer variable
2