The configuration file is JAMAMA_HOME/config/config.xml. The schema defining what kind of entries are allowed is at JAMAMA_HOME/dtd/jamama.dtd.

Do not put comments into config.xml, because Jamama dynamically updates the file if there are any run-time configuration changes. (Therefore, your comments will get lost).

Only edit config.xml when Jamama is not running. It wouldn't hurt anything to do so, but the changes won't get picked up until the next Jamama startup; and your changes will get lost if there is any run-time configurationchange (see previous item).

You can make run-time configuration changes by connecting to the HTML Adaptor which will be running on the port specified in the config.xml file (unless you have disabled it). You use a browser to connect to the Adaptor, and you can then view, modify, add/remove, start/stop, etc., all of the Jamama components.

Configuration changes to any of our components will be persisted (and restored the next time Jamama is started).

To create new component instances at run-time, use the supplied ConfigurableFactory object instead of the JMX management tool's constructor features. You can create objects with a JMX management tool, but JMX will not be able to link to the object from other Jamama components, and will not store configuration changes to it, or even know to re-create it when Jamama is restarted. N.b.: As of Fri Nov 28 17:07:14 EST 2003, ConfigurableFactory is not yet implemented.