The configuration file
Grafikhuset Publi PDF store its configuration information in Windows INI file format, i.e. a simple text file that can be edited with any ASCII editor such as Windows Notepad. For details refer to The configuration file format.
Publi PDF cannot run without at least one properly configured queue. By default Publi PDF look up the required configuration information in a file called »Settings.ini«, which Publi PDF expect to find in the folder where you installed Publi PDF.
This is very practical with single-user or single-server installations, but if you have a corporate environment with multiple servers to maintain it's definitely not practical to maintain a »Settings.ini« file for each unit running Publi PDF.
Sharing a configuration file
Therefore, upon startup Publi PDF is seeking for a special key in the Windows Registry for a valid path to a centrally stored configuration file, which is used when found. Otherwise Publi PDF will fall back to the default »Settings.ini«.
The inspected key is:
.keyroot:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Grafikhuset
\Publi Service
\Settings
.key:
SettingsFile
where the value is a REG_SZ string containing the complete file name including the full path specified with full UNC notation, e.g. \\MyServer\MyShare\MyConfigDirs\MySettingsFile.ini.
If the value is wrong or Publi PDF cannot access the file, Publi PDF will fall back to use the local »Settings.ini«, and the following message will be written to the »Debug.log« file:
The settings file: »<ValueReturnedFromRegistryLookup>« not
found.
Using »<InstallationFolder>\Settings.INI« instead.
Either the path is wrong or security settings prevent file
reading.
Note: The file »Debug.log« can be found in the local installation folder for Publi PDF.
If the local »Settings.ini« doesn't exist or doesn't set out a valid configuration for at least one queue all monitoring will stop and a notice about the cause will be written to »Debug.log«.
Publi PDF does NOT write any user-configurable information to the Windows Registry. The here mentioned registry key must be entered manually or via a custom deployment script.
See also: Important security considerations and The settings file format.
Last revised: 19-12-2007.