This part describes the settings that can be handled through the management tool. If you wish to have different settings for different servers you can add “server nodes” in the management tool and then edit settings unique for that server in this view as well. The servernode name must be the same as the server-name recognized by the OS. We usually don’t encourage this as it is much harder to debug and maintain.
InfoGlue fetched any property it needs like this:
- Check if there is a server node matching the server running the InfoGlue instance wanting the property/setting. If so InfoGlue gets the application setting in question filled in under that node.
- If no value or no server node was found InfoGlue looks at the default application settings and fetches the value for that attribute.
- If no value was specified in either local server node or in general application settings InfoGlue fallbacks to the property files on disk. Mainly deliver.properties and cms.properties. It looks for the value there.
- If still no property was found a default value is used which is hard coded in the application.
We recommend all app settings to be handled in the management tool (and therefor database-stored) with one or two exceptions which must be handled in the property files as they are unique to each deliver-instance or actually concerns the database connection.
All application setting are located under Management --> Application settings. Since 3.0 this takes you directly into the settings view and you can see all settings are divided under tabs.
Below is a thorough walkthrough of the sections and fields under the edit properties button.
comments powered by Disqus