Section 14 Editing LISTSERV Maestro INI Files

The following rules apply to the INI-files "lui.ini", "hub.ini" and "tracker.ini" which are the configuration files for the Maestro User Interface, Administration Hub and Maestro Tracker components respectively (the "my.ini" configuration file of the internal MySQL database follows different rules, as it is a third party product; see the MySQL documentation for details):

All INI-files are text files and assumed to be encoded in the default encoding for the platform being used. For most English/European installations that would be ISO-8859-1 [Latin 1 - Western European].

In the files, every parameter occupies one line. Each line must be terminated by a line terminator (LF, CR, or CRLF). All lines in the file are processed.

A line that contains only white space or whose first non-white space character is an ASCII "#" or "!" is regarded a comment, and its content is ignored.

Every line other than a blank line or a comment line describes one parameter (except if a line ends with a backslash "\", then the following line, if it exists, is treated as a continuation line, as described below).

A parameter always consists of a key and a value. Keys and values are separated by white space or "=" or ":". Any white space around the separation character is also ignored.

All remaining characters on the line become part of the associated value. Some characters which otherwise have special meanings, need to be escaped with a backslash. The ASCII escape sequences "\t"(TAB), "\n"(LF), "\r"(CR), "\\"(backslash), "\""(quotation mark), "\'"(apostrophe), "\ "(space), and "\uxxxx" (where "xxxx" is the Unicode-value of the required character, expressed in hexadecimal format) are recognized and converted to single characters.

In the case that the last character on a line is a "\", then the next line is treated as a continuation of the current line; the "\" and line terminator are simply discarded, and any leading white space characters on the continuation line are also discarded and are not part of the parameter value.

Examples:
Each of the following four lines specifies the key "Truth" and the associated value "Beauty":

Truth = Beauty Truth:Beauty Truth :Beauty Truth Beauty

The following three lines specify a single parameter:

fruits apple, banana, pear, \ cantaloupe, watermelon, \ kiwi, mango

The key is "fruits" and the associated value is:
"apple, banana, pear, cantaloupe, watermelon, kiwi, mango". Note that a space appears before each "\" so that a space will appear after each comma in the final result; the "\", the line terminator and leading white space on the continuation line are discarded and are not replaced by one or more other characters.

As a last example, the line:

cheeses

specifies that the key is "cheeses" and the associated value is the empty string.

14.1 Maestro User Interface INI-File Entries

The following table shows all possible entries of the "lui.ini" file for the Maestro User Interface component. For any entry that is missing in the INI-file, the corresponding default value is assumed.

Table 3 Maestro User Interface INI-File Entries

Entry Key	Description
`AllowISO-i-Mails`	Defines if in outgoing mail the special bi-directional charsets "ISO-8859-6-i" and "ISO-8859-8-i" are used instead of their "normal" ISO-8859 counterparts. Default: `true`
`AllowUTF-8-Mails`	Defines if "UTF-8" is allowed to be used as the charset of ourgoing mail, in the case that none of the ISO-8859 charsets is able to display all the characters used in the mail. Default: `true`
`ClickThroughURL`	Path-part of the click-through tracking URL used for URLs without passing of merged parameters. Default: `/trk/click`
`ClickThroughPPURL`	Path-part of the click-through tracking URL used for URLs with passing of merged parameters. Default: `/trk/clickp`
`CreatePersonalProfileTables`	Defines if full personal profiles should be stored in the internal database, when personal tracking is used. Default: `true`
`ExternalHostName`	Host name and HTTP-port of the Maestro User Interface server as seen by external clients, in the format "`host:port`" where "`:port`" can be left out if standard port "80". To be used if the external host name or HTTP-port of the server is different than the actual host name or port (for example behind a proxy). Default: none (normal host name and port 80 used)
`ExernalHubHostName`	Host name and HTTP-port of the Administration Hub server as seen by external clients, in the format "`host:port`" where "`:port`" can be left out if standard port "80". To be used if the external host name or HTTP-port of the server is different than the actual host name or port (for example behind a proxy). Default: none (normal host name and port 80 used)
`Home`	Home folder in which work-files are kept. Default: subfolder "`lui`" in installation folder
`HubContext`	Context-path part of the user interface access URLs for the Administration Hub component. Default: `hub`
`HubHTTPPort`	HTTP-Port of the Administration Hub server. Default: 80
`HubRMIPort`	Internal communication port (RMI-Port) of the Administration Hub server. Default: 1099
`MaintenanceMode`	Defines it the Maestro User Interface component shall run in maintenance mode or not. Default: `false`
`OpenUpURL`	Path-part of the open-up tracking URL. Default: `/trk/open`
`RegistryDomain`	The domain name with which the Maestro User Interface component stores its settings in the Administration Hub registry. Default: `LUI`
`RegistryHubHost`	Host name of the server with the Administration Hub component. Default: `localhost`
`RemoteAdminPassword`	Password for remote log file access. Default: none (no remote log file access allowed)
`RestoreBackup`	Path name of the folder containing the backup that shall be restored during the next startup. Note: This key will be automatically removed from the INI-file during the next startup. Default: none
`RMIPort`	Internal communication port (RMI-Port) of the Maestro User Interface server. Default: 1099
`TrackerHost`	Host name of the server with the Maestro Tracker component. Default: `localhost`

14.2 Administration Hub INI-File Entries

The following table shows all possible entries of the "hub.ini" file for the Administration Hub component. For any entry that is missing in the INI-file, the corresponding default value is assumed.

Table 4 Administration Hub INI-File Entries

Entry Key	Decription
`Home`	Home folder in which work-files are kept. Default: subfolder "`hub`" in installation folder
`RegistryDomain`	The domain name with which the Administration Hub component stores its settings in its own registry. Default: `HUB`
`RemoteAdminPassword`	Password for remote log file access. Default: none (no remote log file access allowed)
`RMIPort`	Internal communication port (RMI-Port) of the Administration Hub server. Default: 1099

14.3 Maestro Tracker INI-File Entries

The following table shows all possible entries of the "tracker.ini" file for the Maestro Tracker component. For any entry that is missing in the INI-file, the corresponding default value is assumed.

Table 5 Maestro Tracker INI-File Entries

Entry Key	Description
`Home`	Home folder in which work-files are kept. Default: subfolder "`trk`" in installation folder
`HubRMIPort`	Internal communication port (RMI-Port) of the Administration Hub server. Default: 1099
`RegistryDomain`	The domain name with which the Maestro Tracker component stores its settings in the Administration Hub registry. Default: `TRK`
`RegistryHubHost`	Host name of the server with the Administration Hub component. Default: `localhost`
`RemoteAdminPassword`	Password for remote log file access. Default: none (no remote log file access allowed)
`RMIPort`	Internal communication port (RMI-Port) of the Maestro Tracker server. Default: 1099

Back One Page | Forward One Page