...
Essentially the same as the Workflow object in the IBroker interface. Siege displays this XML to the user via an intermediate object, called the WorkflowBuilder, which allows the entire description, including the script payloads, to be represented as XML (ELF/Ogrescript), if appropriate, inside an Eclipse editor. When launching to the Broker, the builder wraps the payload (XML or otherwise) as CDATA and sets this string as the contents of the payload element.
eventLevel | Tells the event-sending components, such as services or ELF Elf, involved in handling the workflow, which level of information to publish as remote events on the bus (rather than or in addition to logging). The enumeration below is in ascending order, such that successive levels include the preceding ones. |
priority | Expresses a global priority for this workflow. (Currently unused.) |
global-resource | Scheduling can be overridden by setting this element. The named resource is applied to all nodes in the expanded graph, unless the individual node carries a different resource indication. If no resources are set, the resource is determined by a call to the scheduler (not yet fully implemented, but coming soon). |
failure-constraint | See further below. These are global constraints applying to the entire workflow graph; each node can also have its own set of constraints. Default behavior is that a single node failure makes the entire workflow fail. |
...
type | elf or csh; but see below. |
reference | A URI for a file to fetch and read in as the script content. |
contents | The actual script content. As noted above, this is habitually ELF Elf container XML (holding Ogrescript executable XML) – the only script for which there is full support in the Broker infrastructure; but in theory this could be any executable script (pending the addition of the appropriate modules to the Broker and/or ELF itself). |
...