Information Technology Reference
In-Depth Information
executable code, and target DCI of work
ow nodes) except the input
les of the
work
ow. The local input
files and the local output
files created during work
ow
execution are stored in the File Storage. The Work
ow Interpreter is responsible for
the execution of work
ows, which are stored in the Work
ow Storage. The
Information System holds information for users about work
ows running and job
status. Users of WS-PGRADE gateways work in isolated workspace, i.e., they see
only their own work
ows. In order to enable collaboration among the isolated
users, the Application Repository stores the WS-PGRADE work
ows in one of
their
five possible stages. (Physically all the
five categories are stored as zip
files.)
The
ows are as follows, and the collaboration among
the gateway users is possible via all these categories:
five categories of stored work
Graph (or abstract work
ow) containing information only on the graph structure
￿
of the work
ow.
Work
ow (or concrete work
ow) containing information both on the graph
￿
structure and on the con
guration parameters (input
files pointers, output
les
pointers, executable code and target DCI of work
ow nodes).
￿
Template: a work
ow containing information on every possible modi
able
parameter of the work
ow if they can be changed by the users or not. These play
an important role in the automatic generation of executable work
ows in the
end-user mode of a WS-PGRADE/gUSE gateway (Sect. 2.6 ).
Application is a ready-to-use workflow that contains all the embedded work-
￿
flows, too. It means that all the information needed to execute this work
ow
application is stored in the corresponding zip
le.
Project is a work
ow that is not completed yet and can be further developed by
the person who uploaded it into the Application Repository or by another person
(so collaborative work
￿
ow development among several work
ow developers is
supported in this way).
At the top of the three-tier structure, the presentation tier provides WS-
PGRADE, the graphical user interface of the generic SG framework. All func-
tionalities of the underlying services are exposed to the users by portlets residing in
a Liferay portlet container, which is part of WS-PGRADE. This layer can be easily
customized and extended according to the needs of the SG instances to be derived
from gUSE. The next section introduces the essential user-level elements of WS-
PGRADE.
2.5 Introduction to WS-PGRADE
Most users of gUSE come into contact with WS-PGRADE portal interface. The
WS-PGRADE portal is a Liferay technology-based web portal of gUSE. It can be
accessed via the major modern web browsers like Chrome, Firefox, etc.
Search WWH ::




Custom Search