Legals | Data Protection | Sitemap | Home


bwGRiD portal template 3.6 (teamwork function, file editor)

bwGRiD Portal Template 3.5 (hardware features, working with large files, job mail function)

bwGRiD portal template 3.4 (Dacapo clone, resource monitor)  

final bwGRiD portal projekt meeting in Karlsruhe  

bwGRiD portal template 3.3 (security manager, JobListTag)  

bwGRiD portal template 3.1 (file manager update)  

bwGRiD portal template 3.0 (meta submit system)  


March/April 2013
bwGRiD portal template 4.0 (migration to Liferay)

Introduction to Gatlet

The aim of the Gatlet project is to implement an interface for portlets accessing Grid computing resources through the Grid Application Toolkit (GAT). The advantage in using GAT is that it provides access to all three major Grid middlewares (Globus Toolkit, UNICORE and gLite) through one common interface. Since Gatlet is JSR 168 compliant it should work with any JSR168-conform portal. Gatlet is implemented and tested within the GridSphere portal framework.

The diagram below shows the structure of Gatlet in the context of GridSphere and GAT. The design of Gatlet enables the Portlet programmer to easily use any supported Grid middleware as well as to switch to more recent tools like JSaga later.



See Gatlet_NGI_DE (245 KB) for a talk about Gatlet given by Stefan Bozic at the Karlsruhe Institute of Technology (KIT).