Content  


Configuration

Our configuration approach is based on the XML. A configuration input file is forwarded to the scheduler, which use the information to setup the task graph. Additionally, plugin specific parameters can be forwarded to the plugins. In the following, the core mechanisms are introduced.

Framework and plugin configuration via XML
  1. <plugins>
  2. <plugin>
  3. <key>Dummy0</key>
  4. <step>0.3</step>
  5. </plugin>
  6. <plugin>
  7. <key>Dummy1</key>
  8. <delta>3.2</delta>
  9. </plugin>
  10. </plugins>

Each plugin has its own XML region (Lines 2-5, 6-9), which have to reside within the general plugins region (Lines 1-10).

Within the key tag, the exact name string of the plugin, which should be loaded, has to be entered (Lines 3,7).

Arbitrary parameters can be forwarded to each plugin (Lines 4,8). This data can be accessed from within the individual plugin bodies, via XPath expressions. A conversion utility and a mathematical expression mechanism based on Lua is provided to ease the incorporation of the string-based configuration parameters into numerical expressions.