Presentation on theme: "Building QuakeSim portlets with GTLAB Mehmet A. Nacar 1, Marlon E. Pierce 1, Andrea Donnellan 2, and Geoffrey C. Fox 1 1 Community Grids Lab, Indiana University."— Presentation transcript:
Building QuakeSim portlets with GTLAB Mehmet A. Nacar 1, Marlon E. Pierce 1, Andrea Donnellan 2, and Geoffrey C. Fox 1 1 Community Grids Lab, Indiana University 2 Jet Propulsion Lab, California Institute of Technology
Grid Portlets for QuakeSim QuakeSim portlets in production – Initial effort was to build the portal Web services – QuakeSim portlets invoke the services and then execute simple workflows built in shell scripts Problem: QuakeSim portlets should also work on TeraGrid resources. – TeraGrid restricts the services run on TeraGrid resources. Our approach: – Prototyping QuakeSim portlets using Grid Tag Libraries and Beans (GTLAB). Advantages: – QuakeSim portlets utilize IU, SDSC, NCSA and other TeraGrid resources – Rapid development by using reusable components 3
QuakeSim portlets using TeraGrid Disloc is used to calculate surface displacements from earthquake faults. 1994 Northridge earthquake 2003 San Simeon Earthquake 2004 Great Sumatran Earthquake.
Grid tags are embedded into JSF view pages and decorated with standard JSF form, input, output and button components – Grid components are non-visual. GTLAB Standard JSF JSF Action
GTLAB Grid Tag Libraries and Beans (GTLAB) Encapsulates clients to common Grid services as XML tag libraries and server side Java beans. – Embedded by portlet developers in their portlet pages to invoke common tasks – Specification of the composite action you want to occur when a user hits the submit button. – Allows portal developers to concentrate on the user interface components. Tags can be arranged in directed acyclic graphs (dependency chains). – These represent simple workflows. Based on extensions to Java Server Faces (JSF) and the Java CoG Kit. Implements a component model for User Interfaces (UI) that is more powerful than portlets
Architecture Overview Grid portals are client to backend codes through Web/Grid services. Grid tags are part of user interface tier and embedded into portlet container. Grid tags use local services in Apache Tomcat to manage sessions and handlers. Implies that “portal” is quite sophisticated as must support integration Note CoG kit is here to act as a broker to hide complexities of evolving services (e.g. different versions of Globus) “violates service model” in that core software centralized in portal application 9
GTLAB features GTLAB provides common components for building portlets using tags and reusable parts. The goal of GTLAB to simplify Grid portlet development – Enable rapid development from reusable components GTLAB capabilities include Grid operations with XML based tags within JSF framework. Grid tag libraries are built using JSF custom component development techniques Grid tags are interfaces to backing Grid beans – End users pass values to Grid beans by using tag attributes. Each backing Grid bean has equal capability with a portlet application in case of Grid portlet approach. – GridFtp tag generates GridFTP Portlet But tags allow service backend component model to map into an intermediate UI component models – each tag set is a component – The components/tags can easily be composed into a rich UI which portlets cannot do 10
Grid TagsAssociated Grid BeansFeatures ComponentBuilderBean Creating components, job handlers, submitting jobs. This is visually rendered as HTML MonitorBean Handling monitoring page actions MultitaskBean Constructing simple workflow MultitaskBean Defining dependencies among sub jobs MyproxyBean Retrieving myproxy credential FileOperationBean Providing Gridftp operations JobSubmitBean Providing GRAM job submissions FileTransferBean Providing Gridftp file transfer (Other JSF UI Tags) ResourceBean Describes common properties among all tags and beans. Passing values given by standard visual JSF components.
Encoding DAGs in Portlets Multitask provides a simple Directed Acyclic Graph (DAG) This example demonstrates a composite Grid job using multi- staged multitask GTLAB handles lifecycle of DAG within JSF application
13 DAG Example JSF Page This encodes the DAG on the previous page.
Advantages of GTLAB GTLAB provides simplicity to develop science portals – Rapid development – Easy deployment Grid tags provide rich selection of attributes to initialize Grid beans. Composite tasks can contain an unlimited number of subtasks GTLAB gives flexibility to developers to use their own Grid beans library or add more Grid beans to the existing ones. – Following the method name convention of GTLAB Grid beans also can be imported to any presentation logic – GCEShell is a command-line tool Grid bean methods are bound to tags with attributes to simplify the building of new Grid portlets
Total overhead = T submit -T request = 156 msec (that includes JSF overhead) Average overhead of GTLAB is about few milliseconds GTLAB does not add up significant delay on processing the requests. 15 GTLAB ProcessingJSF ProcessingHandler storingSubmitting Time (msec)21531410 GTLAB Overhead
Conclusion We have described Grid portlets to QuakeSim portal. – Initial effort was to build the portal Web services Described the process for creating Grid portlets using GTLAB. – We gained rapid development by using reusable components Grid tags can handle composite Grid operations within QuakeSim applications. Prototyped QuakeSim portlets – Disloc and Simplex portlets. 16
More Information GTLAB version 1.0 Beta release available at – http://grids.ucs.indiana.edu/users/manacar/GTLAB- website http://grids.ucs.indiana.edu/users/manacar/GTLAB- website See link from main OGCE web site – http://www.collab-ogce.org http://www.collab-ogce.org Contact OGCE: firstname.lastname@example.org@ogce.org Contact Mehmet: email@example.com@indiana.edu 17
Motivation OGCE Grid portlets typically wrap each single Grid capability in a separate portlet – GridFTP-->GridFTP Portlet Gateway portlets encapsulate sophisticated but specialized functionality. – Such as submitting multiple linked jobs – Each functionality requires a separate portlet We need a middle way to “automatically” build complex functionality from component parts – Traditional portlets don’t work as no agreed way to combine component portlets into an integrated user capability – We need a component model for portlets: reusable portlet parts JSF is our starting point – Removes dependencies on the Servlet API. – Backend software is just beans, so can be reused more easily outside of web and portlet applications. JSF also provides an extensible framework (tag libraries)