The Gateway as of IF-3 uses local XML Job Definition files to contain the various metadata/annotation that it requires in order to (a) locate suitable services, e.g. by operation concept or input/output type (b) map inputs/outputs correctly, e.g. based on concept type (c) provide default values and (d) allow client-transparent job invocations for a number of invocation paradigms or idioms (direct web service, Soaplab, and workflow enactor).

Here is a sample Job Definition file, with comments! See also the Java interface for the operation client-plugin code (to query inputs and outputs, and start an invocation) and the Java base class for the idiom-specific (logical) operation invocation (including init, run, getStatus, stop, logProvenance), attached.

Note that the Gateway now allows the WSFL document to be included within the Job Definition, so that this becomes a complete description of the workflow, including concept annotations and default values.

-- ChrisGreenhalgh - 14 Feb 2003

The workflow for the sample Job Definition file is at ExampleBioFetchWorkflow. To run the workflow enactment engine standalone, rather than through the gateway, an input template file is used. This contains similar information to the Job Definition.

-- MarkGreenwood - 27 Feb 2003