Information Technology Reference
In-Depth Information
2. If the community needs just a generic but simple interface, gUSE can be tailored
automatically for each application by setting it to the end-user mode. In this
solution users are not allowed to create new work
ows, but they have access to
the local Application Repository to import already developed work
ows. These
work
ows should be stored as templates, and after importing such a shared
work
ow, the generic end-user interface automatically and dynamically gen-
erates a parameterization interface based on the imported work
s different
properties that were set with read and write permissions when the work
ow
'
ow
template was created.
Mode 2: Customization by ASM: In order to support the development of appli-
cation-speci
c Module (ASM) API by
which customized portlets can easily and quickly be created. Once this has hap-
pened, scientists who require such customization can run their work
c UI, gUSE provides the Application-Speci
ow applica-
tions on various DCIs via the application-speci
c portlets developed by means of
the ASM API. In this case the original WS-PGRADE UI is replaced or extended
with the customized application-speci
c UI, and this new UI can directly access the
gUSE services via the ASM API.
Mode 3: Customization by Remote API: gUSE can be extended to let the
community use its own user interface to send a complete WS-PGRADE/gUSE
work
ow via HTTP protocol without using the original WS-PGRADE interface.
Technically this extension is a new web service component called Remote API,
which should be deployed on the WS-PGRADE/gUSE portal server, and be reg-
istered among the general gUSE components. In this case the existing community
user interface can access the gUSE services via a direct API and run WS-PGRADE
work
ows directly via this API.
Mode 4: Own interface for work
ow submission: It is also possible to move the
DCI Bridge service from the gUSE tiers and make this service directly accessible
via the standard BES job submission interface. In this case WS-PGRADE/gUSE is
not used; only the stand-alone version of the DCI Bridge that can submit jobs to the
connected DCIs and the existing community gateway or work
ow system should
be enabled to submit jobs via the standard BES interface of DCI Bridge.
2.7 Conclusions
The main objective of WS-PGRADE/gUSE was to develop a gateway framework
that enables a large set of different communities to build their gateway instances by
simply customizing the framework according to their needs. In order to support
many communities,
flexibility enables
access to all the major DCIs and data storages with all the available authentication
methods and enables parallel/distributed execution of work
flexibility was a major design goal. This
ows at several parall-
elization levels. Subsequent chapters explain in detail those features that contribute
to this high degree of
flexibility in WS-PGRADE/gUSE.
Search WWH ::
Custom Search