Template-Based Configuration Files - Toshiba SG20 - Magnia - Web Server Customization Manual

Customization

Template-based configuration files

Many of the configuration files in the Magnia SG20 are managed using templates. With
this methodology, a set of templates for each configuration file is maintained. Then, when
a change is made to the configuration file by the Magnia SG20 user interface or other
mechanism, the configuration file is regenerated using these templates.
The Perl-based middleware and CGI code interfaces may need to modify the system
configuration files (for example when a user is added or a configuration changed). When
a change has been made, a trigger is invoked, which regenerates the corresponding
system configuration file using the configuration file templates.
Because these template-based configuration files are regenerated periodically, changes
to the files must be made in the templates, not in the file itself. Changing the
configuration file directly does not work.
Templates are stored in /sa2/templates. Each file's templates are located under this
directory based on the file's location in the system. For example, the /etc/passwd
template files are located in /sa2/templates/etc/passwd. The contents of this
directory are shown in the following table:
05system
10static
The configuration file may be broken up into several templates. Each template
represents one part of the configuration file, and the order in which they are used is
determined by the alphabetical sorting order of the template file name. This is why a two-
digit number, which determines its placement within the final configuration file when it is
regenerated, precedes each template file name.
15ftp 15postgress
15mysql 20dynamic
Template-based configuration files
footer
header
19