Sysadmin resources for FMS Interactive Server?

I found those links earlier.

From my perspective, further information about debugging common server

errors would be helpful. For example, certain error messages might

indicate permissions problems or a configuration issue, etc. More

details on different configurations. For example, a long time ago I

posted a suggestion about configuration:

What I believe would make for an easier configuration process is to

utilize the inheritance aspect of XML, allowing for a LocalSettings.xml

file which would be read in by FMS last, overriding any default settings

thus eliminating the need to alter the default *.xml files. Any new

settings introduced that require changes can be imported as needed.

Overwriting the stock conf/*.xml files with new information would not

interfere with your custom settings as they would remain intact in

LocalSettings.xml. Any conflicts could be reported to the logs or stdout.

One exception being fms.ini -- which could easily be revamped into XML

and used in the above model.

Why do we have an FMS.INI file? This seems like a Windows cut-over.

We have a big license for FMS and thus we tend to roll FMS out on

development, test, and production versions. Doing the installation via

a script is tedious; I wonder if there is a better way to get these

rolled out. For example, I could probably template the configs and

distribute the binary tree (which would have correct permissions) via

Puppet -- but would the startup/shutdown work correctly via this mechanism.

Details along those lines would be really useful reference to have handy.

Thanks!

Forrest