Information Technology Reference
In-Depth Information
Fig. 3.3 A graph in Graph Editor
3.5.2 Design Time Concrete Work fl ow View
Once the graph view of a workflow is created, the next step is to con
gure it with
all
ne the circumstances of the concrete execution.
Therefore, the result of the con
those properties that de
guration phase is a concrete workflow. In the
con
guration phase the user should de
ne the semantics of each workflow node,
the
files to be consumed and produced, as well as the infrastructure where the given
node should be executed.
Figure 3.4 shows the possible options for a node con
guration. As it can be seen,
in the root the main decision to make is the type of node that can be set to represent
a job (application binary), a service (service), or a workflow. Considering the
learning curve of a job con
guration, the simplest way is to invoke a service. gUSE
language offers several ways to declare a service invocation: it can be set as a SOAP
using AXIS implementation, a simple HTTP invocation, or using REST. Some
options require specifying the method to be called (such as GET or PUT in case of
REST). Users are allowed to send inputs encoded in the URL or as
files, of course,
besides the returning stream are mapped to the
first output port of the job
constantly.
In most cases, users own their applications, and they would like to execute them
on remote computational resource. gUSE, and its submitter component called DCI
Search WWH ::




Custom Search