Information Technology Reference
In-Depth Information
2.5.1 User Roles
A member of a gUSE community can be a power user or an end-user in the WS-
PGRADE portal environment. The power user or,
in other words, work
ow
developer develops work
ows for the end-user scientists (chemists, biologists,
etc.). The power user understands the usage of the underlying DCI and is able to
develop complex work
guring, and run-
ning workflows in the underlying DCI as well as monitoring and testing their
execution in the DCIs. In order to support the work of these power users, WS-
PGRADE provides a GUI through which all the required activities of developing
work
ows. This activity requires editing, con
ow is developed for end-user scientists, it
should be uploaded to a repository where scientists can download from and execute
it. In order to support this interaction between power users and end-users, gUSE
provides the earlier-mentioned Application Repository service in the gUSE ser-
vices-tier, and power users can upload and publish their work
ows are supported. When a work
ows for end-users
via this repository.
The end-user scientists are generally not aware of the features of the underlying
DCI nor of the structure of the work
ows that realize the type of applications they
have to run in the DCI(s). For these users, WS-PGRADE provides a simpli
ed end-
user GUI where the available functionalities are limited. Typically, end-user sci-
entists can download work
ows from the Application Repository, parameterize
them, and execute them on the DCI(s) for which these work
ows were con
gured
to run. They can also monitor the progress of the running work
ows via a sim-
pli
ed monitoring view. Any user of WS-PGRADE can login to the portal either as
a power user or an end-user and according to this login she/he can see either the
developer view or the end-user view of WS-PGRADE.
2.5.2 The Three-Phase Process of Workflow Development
The WS-PGRADE power users (work
ow developers) typically perform a three-
phase operation sequence (work
ow
execution) as shown in Fig.
2.2
. This step sequence covers the life-cycle of a
work
ow edit, work
ow con
gure, and work
ow. The life-cycle of a WS-PGRADE work
ow is the following:
1. During the editing phase, the user creates the abstract graph of the work
ow.
2. In the work
ow con
guring phase the executable, the input/output
files, and the
target DCI of the work
ow nodes representing the atomic execution units of the
work
ow are speci
ed.
3. Finally,
in the submitting phase,
the work
ow is submitted resulting in a
work
ow instance.
The following section gives a detailed description about what happens in the
three phases.
Search WWH ::
Custom Search