XCAT Science Portal Status & Future Work July 15, 2002

1. XCAT Science PortalStatus & Future WorkJuly 15, 2002 Shava Smallen Extreme! Computing Laboratory Indiana University

2. Outline • Current Status: • Architecture • Case Study: Grappa • US-ATLAS • GriPhyN • Future Work: • Recent developments • Web portal frameworks & portlets • Application Factory Web Services (AFWS) • Web Services for Remote Portals (WSRP) • xportlets

3. Motivation • Lots of Grid tools & services • Requires a good deal of expertise to • develop an application • use an application (more than what many users want to know) XCAT Science Portal screenshot • Grid portal: • web portal by which users can access Grid tools & services • common approach

4. XCAT Science Portal (previously known as Active Notebook project ) • Grid portal framework for building personal science portals • Active notebook (execution management) • HTML pages to describe the features of the notebook and how to use it • HTML forms which can be used to launch parameterizable scripts • Results archived - parameters stored in a sub-notebook

5. app1 Scripts • Very flexible • Jython - access to Java classes • Globus Java CoG kit • XCAT • XMESSAGES • Not every user has to write scripts • Notebooks can be shared among users • Import/export capability parameters Invoke jython interpreter jython script portal Launch app1 Grid

6. XCAT Science Portal Architecture User’s Web Browser Portal Web Server (tomcat server + java servlets) GSI Authentication Jython Intepreter Notebook Database Grid

7. Case Study: Grappa • Grappa: Grid access portal for physics applications • provide a Gridportal front-end by which physicists can manage computation and data • Joint work with Rob Gardner’s group (IU Physics & U. of Chicago Physics) • Part of the ATLAS collaboration (US-ATLAS) • Subproject of Grid Physics Network (GriPhyN)

8. ATLAS • Detector for the Large Hadron Collider (LHC) at CERN • 2000 physicists, 150+ universities & laboratories, 34 countries ATLAS detector • Expected to be on-line in 2006 • Why the Grid? • Raw data: 2 PB/yr • Analysis: 8 PB/yr • Participant in several Grid projects: LCG, GridPP, INFN Grid, DataGrid, PPDG, GriPhyN/IVDGL

9. XCAT Science Portal & ATLAS • Athena = ATLAS software framework • Athena Notebook Prototype/Demo • ATLAS Software Week (March) • Allow user to submit sequence of Athena job options files to US-ATLAS testbed resources • File staging, remote job option file editing, basic monitoring, ad-hoc viz • Packaged with Pacman – installed with single command • Distributed to US-ATLAS testbed this month • Interactive jobs • Production – scripting interface to launch and portal to monitor

10. GriPhyN: Grid Physics Network • Targets data-intensive applications • ATLAS, CMS, LIGO, and SDSS • Provide a set of tools for collaborative data analysis • 90% of data is derived • Virtual data - transparency with respect to location and materialization • Data replicated & distributed – transfer or recompute

11. Application Catalog Services Monitoring DAG Planner Info Services DAG Repl. Mgmt. Executor Policy/Security Reliable Transfer Service Compute Resource Storage Resource Virtual Data Browser • Search virtual data • Publish virtual data: create transformations and derivations • User Profile – bookmarks, credential mgmt, resource mgmt, etc. • Provide functionality analogous to that of a web browser

12. Outline • Current Status: • Architecture • Case Study: Grappa • US-ATLAS • GriPhyN • Future Work: • Recent developments • Web portal frameworks & portlets • Application Factory Web Services (AFWS) • Web Services for Remote Portals (WSRP) • xportlets

13. Web Portal Frameworks • Separation of appearance & functionality • User customization of appearance (multi-user support) • Functionality packaged into portlets Jetspeed screenshot • Examples: IBM Websphere, Apache Jetspeed, etc. • Many Grid portal efforts • Encourages interoperability

14. Application Factories • Applications are difficult to deploy • Libraries, licensing, environment setup, etc. • E.g., Athena: 10 GB library, Redhat 6.1 • Web services approach • XCAT implementation • App. factory web service (AFWS) is a stateless, persistent service and launches one instance of the application • Distributed component applications • Both individual components and composite application are web services

15. WSRP Specification • Web Services for Remote Portals • Generic proxy portlet • Talks to any remote WSRP-enabled web service • Web service handles content • WSRP web service registry • Advantage? • No installation required; just contact WSRP web service

16. Grid Portal Archiving (sub-notebooks) (1) AFWS proxy portlet (2) (7) (3) (6) (4) Application instance AFWS Application coordinator (5) jython scripts app1 Notebook(s) Putting It Together AFWS Registry Portal Grid AFWS = Application Factory Web Service

17. xportlets • Use Jetspeed as web portal framework • Open source from apache • xportlets – bundle of portlets • AFWS proxy portlet • MyProxy portlet • Xmessages pull • GridFTP File Browser • Scripting API to create Application Factories • Different kinds – XCAT, notebooks, etc.

18. Summary • Current XCAT Science Portal architecture • Active notebooks, scripts • Case Study: Grappa • US-ATLAS • GriPhyN • Redesign to portlet & web services architecture • Jetspeed takes care of presentation • Interoperability – pluggable into any portlet-enabled portal framework • Easy deployment – web services & generic proxy

19. More Information • Extreme! Computing Laboratory: http://www.extreme.indiana.edu • XCAT Science Portal: http://www.extreme.indiana.edu/xcatsp • Grappa: http://iuatlas.physics.indiana.edu/grappa • xportlets: (coming soon…) http://www.extreme.indiana.edu/xportlets • Email: ssmallen@cs.indiana.edu

20. Grid Portal (1) AFWS proxy portlet (2) (7) (3) (6) (4) Application instance Application coordinator (5) Component instance Component instance component Instance Putting It Together Archiving (sub-notebooks) AFWS Registry Portal AFWS Grid jython scripts Notebook(s) AFWS = Application Factory Web Service