Introduction to Science Gateways and Science Gateway Frameworks - Science Gateways for Distributed Computing Infrastructures - page 12

ported applications and application-speci that is accessible at the SCI-

BUS web page. Figure 1.2 shows those communities who have some relationship
with SCI-BUS to build their science gateway instances. Beyond these communities
there are many others without any relationship with SCI-BUS that also intensively
use the SCI-BUS gateway technology.

c gateways ”

1.6 Collaboration-Based SG Instance Development
Methodology

SCI-BUS technology helps the collaboration among the different types of people
developing and using the gateway technology. As already mentioned, two different
level repositories help collaboration between work ow

users. Inside a community using the same gateway, the internal gUSE Application
Repository can be used for work

ow developers and work

ow developers to publish the ready-to-use

work ows, and scientists in the end-user mode of the gateway can import these

ready-to-use work ows from the Application Repository. After parameterizing the

work ows they can be executed in the target DCIs. Of course, the Application

Repository can also be used to support collaboration between work ow developers.

A work ow stored in the Application Repository can be taken by any work ow

developer belonging to the same gateway ' s community and can extend or further

develop the imported work ow

developers and end-users belonging to different gateway communities via the
SHIWA Work

ow. Similar activities are supported among work

ow interoperability
technique developed in the SHIWA project, this repository and the WS-PGRADE/
gUSE gateway enable collaboration even in cases when the different communities
use different work

ow Repository. Using the coarse-grained work

ow systems (see details in Chap. 8 ) .
Collaboration is supported not only among work ow

users but also among gateway developers. For this purpose SCI-BUS developed and
set up the SCI-BUS Portlet Repository. This enables the sharing of Liferay portlets
between SG instance developers (see details in Chap. 9 ) . This sharing of existing
portlets can further accelerate the customization process of gateway frameworks.
In fact, these repositories, the SG framework stored in the open source
SourceForge repository and the customization concept of SCI-BUS enable the
introduction of a collaborative SG instance development methodology. Figure 1.3
shows the services required for the SG instance development methodology as well
as the different types of developers and users related to the SG instance. The steps
in developing an SG instance according to this SG instance development meth-
odology are as follow:

ow developers and work

Step 1: An SG instance developer downloads the WS-PGRADE/gUSE frame-
work from SourceForge and deploys it as a general purpose science gateway. It
contains the major functionalities to develop and run workflows by the work-

￿

flow developers and to run work ows by the end-user scientists.