The following rules apply to the
lui.ini,
hub.ini,
tracker.ini, and
tomcat.ini INI-files, which are the configuration files for the Maestro User Interface, Administration Hub, and Maestro Tracker components. (The
my.ini configuration file of the internal MySQL database follows different rules since it’s a third party product. See the MySQL documentation for details.)
The key is "fruits" and the associated value is:
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.
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. Changes in INI files require a restart of the component to take effect.
|
|
|
Defines if the LISTSERV Maestro job ID should be included in the message ID of all outgoing emails or not. Set to either true or false.
|
|
Defines if the user is allowed to change the content charset on a job-by-job basis, or if he has to accept the default charset (see “ DefaultMailCharset”).
|
|
Defines if the special bi-directional charsets”ISO-8859-6-i” and “ISO-8859-8-i” will be used in outgoing mail instead of their normal Iso-8859 counterparts.
|
|
Defines if the Maestro User Interface is allowed to store persistent cookies in the client browser so that the user interface may remember certain user settings between two sessions. If set to “false”, then these settings will be stored as session-cookies only and will be forgotten when the browser is closed.
|
|
Specifies whether or not a change log of subscriber activities (for hosted lists and datasets) is to be created.
(Optionally) If a change log file is used, then this defines the time period for each log (i.e. daily, weekly, monthly, or yearly).
|
|
Path-part of the click-through tracking URL used for URLs without passing of merged parameters. Default: /trk/click
|
|
|
|
Specify whether full personal profiles should be stored in the system database when personal tracking is used. Default: true
|
|
Defines the language that is to be used for the membership area subscriber pages of all datasets that do not have their own membership area language defined. The language must be specified using its corresponding two-letter ISO language code (in lower case), as defined by the alpha-2 code of ISO-639-1 (see http://www.loc.gov/standards/iso639-2/php/English_list.php). Default: “English (Default)”
|
|
Defines the charset that is to be used as the charset of the content for newly created jobs that are not copies of existing jobs. May or may not be changed by user (see “ AllowCharsetChoice”). Default: ISO-8859-1
|
|
Defines if distribute chunking will be performed and with which chunk size. A chunk size of zero or less means that no distribute chunking will be performed. A positive non-zero chunk size means that chunking will be performed with chunks of the given size, but with a minimum size of 10000 (i.e. any positive chunk size less than 10000 will be treated as if 10000 had been specified).
|
|
Determines how often the system looks for (and cleans out) expired unconfirmed subscriptions to hosted tables and lists (i.e., subscriptions that were not confirmed during the given expiration interval – see INI-file parameter OptInConfirmationExpiration). Specified as a number, which defines the cleanup interval length in “hours” (i.e., every “N” hours the system checks for expired subscriptions and cleans them out).
See the LISTSERV Maestro Data Administrator’s Manual for more information about subscription confirmations.
|
|
The host name of the Maestro User Interface server as seen by clients that access the user interface with a web browser. To be used if clients shall access the server with a different host name than the normal internal host name of the server, for example when using a proxy. Default: The value of the HostName parameter, if present. Otherwise the normal host name (canonical host name) of the server running the Maestro User Interface.
|
|
The HTTP (or HTTPS) port of the Maestro User Interface server as seen by clients that access the user interface with a web browser. To be used if the external port of the server is different than the default for the protocol employed (both if the normal HTTP or the secure HTTPS protocol is employed). Default: 80 (if the protocol is HTTP) or 443 (if the protocol is HTTPS)
|
|
Defines if HTTPS is used as the access protocol for the Maestro User Interface web-interface pages. Set to “true” if HTTPS is used, or “false”, if normal HTTP is used.
|
|
Default: subfolder “lui” in installation folder
|
|
The host name of the local machine that is to be used whenever a name is required to identify the local host (and no other INI-parameter overrides this for a specific purpose).
|
|
|
|
The host name of the Administration Hub server as seen by clients that access the hub interface with a web browser. To be used if clients shall access the hub server with a different host name than the normal internal host name of the server, for example if the server has several names or when using a proxy.
Default: the host name defined by the RegistryHubHost parameter. If that parameter is not present either, the normal host name (canonical host name) of the server running the Maestro User Interface.
|
|
The HTTP (or HTTPS) port of the Administration Hub server as seen by clients that access the hub user interface with a web browser. To be used if the external port of the server is different than the default for the protocol employed (both if the normal HTTP or the secure HTTPS protocol is employed).
Default: 80 (if the protocol is HTTP) or 443 (if the protocol is HTTPS)
|
|
Defines if HTTPS is used as the access protocol for the Administration Hub web-interface pages. Set to “true” if HTTPS is used, or “false”, if normal HTTP is used.
|
|
|
|
|
|
|
|
The expiration time for unconfirmed subscriptions to hosted datasets and lists – i.e., the amount of time after the initial subscription request during which the subscriber may confirm the subscription (“double opt-in”) before the subscription request expires and is removed. Specified as a number, which defines the expiration time in hours. Default: 48
See the LISTSERV Maestro Data Administrator’s Manual for more information about subscription confirmations.
|
|
|
|
Password for remote log file access.Default: none (no remote log file access allowed)
|
|
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.
|
|
|
|
|
|
Define if the “Currently in the system” section of the dashboard is supposed to display the current count of events in the system or not. On systems with a lot of events, the calculation of this count may be slow, thus slowing down the dashboard display. In this case it may be a good idea to disable the display of this count by supplying “false”.
|
|
|
|
Defines if HTTPS is used as the access protocol for the TRK component (i.e. for the tracking URLs). Set to “true” if HTTPS is used, or “false”, if normal HTTP is used.
|
|
Determines how often the system looks for (and cleans out) subscribers of hosted LISTSERV lists that have unsubscribed by email (i.e. not by the LISTSERV Maestro web interface). Specified as a number, which defines the cleanup interval length in “minutes” (i.e., every “N” minutes the system checks for unsubscribed subscribers and cleans out their data.)
See the LISTSERV Maestro Data Administrator’s Manual for more information about subscription confirmations.
|
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. Changes in INI files require a restart of the component to take effect.
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. Changes in INI files require a restart of the component to take effect.
The following tables show all possible entries of the tomcat.ini file for Tomcat. For any entry that is missing in the INI-file, the corresponding default value is assumed. Changes in INI files require a restart of the component to take effect.
The following table shows the advanced entries of the
tomcat.ini file for Tomcat. Do not change these unless instructed by L-Soft Support.