XCAT Science Portal Status Future Work July 15

XCAT Science Portal Status & Future Work July 15, 2002 Shava Smallen Extreme! Computing Laboratory Indiana University

Outline 1. Current Status: a. Architecture b. Case Study: Grappa i. US-ATLAS ii. Gri. Phy. N 2. Future Work: a. Recent developments i. Web portal frameworks & portlets ii. Application Factory Web Services (AFWS) iii. Web Services for Remote Portals (WSRP) b. xportlets

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) • Grid portal: XCAT Science Portal screenshot – web portal by which users can access Grid tools & services – common approach

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

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

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

Case Study: Grappa • Grappa: Grid access portal for physics applications – provide a Grid portal 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 (USATLAS) • Subproject of Grid Physics Network (Gri. Phy. N)

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

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

Gri. Phy. N: 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

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

Outline 1. Current Status: a. Architecture b. Case Study: Grappa i. US-ATLAS ii. Gri. Phy. N 2. Future Work: a. Recent developments i. Web portal frameworks & portlets ii. Application Factory Web Services (AFWS) iii. Web Services for Remote Portals (WSRP) b. xportlets

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

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

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

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

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

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

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

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