This Reactor provides a generalized proxy for running Agave API jobs such that their inputs, parameterization, and outputs are connected to (and thus discoverable from within) the Data Catalog.
Before an Agave App can be run by this proxy, three things must happen:
- It must be architected to fit the PipelineJobs workflow
- It must be public or shared with user sd2eadm
- It must be registered as a Data Catalog
Pipeline
The app must generate filenames that are distinguishable between runs. This is
enforced to prevent accidentallly over-writing of files when multiple jobs
share an archiving destination. Furthermore, the app definition and any
interior runtime logic must use fully-qualified Agave files URLs to
define inputs. Finally, the app's id must be unique not only in the
Agave Apps Catalog (this is automatically enforced) but also in the
Data Catalog Pipelines collection.
Coming soon...
Coming soon...
Construct and send a message including the following components to the PipelineJobs Agave Proxy Reactor.
- An Agave job definition
- A metdata linkage parameter
- Optional control parameters
Note
The agave_pipelinejob format is documented in JSONSchemas.
The Agave job definition must be included as as subdocument in the message. To
illustrate this, start with a basic Agave job definition: Here is an
example for an imaginary Agave app tacobot9000-0.1.0u1.