2. Content TCD’s past experience with portals Plans for WS-Pgrade and SCI-BUS – Integration with HELIO to build a portal for the Heliophysics community – Use WS-Pgrade as the standard user interface to Grid-Ireland’s computational and storage facility.

3. TCD and portals Migrating Desktop (2003-2008) – CrossGrid and Grid-Ireland sites Ganga and Diane (2008-now) – Used to test jobs for the Costas’ arrays. Genius (2004) – Used with EDG middleware P-Grade – Deployment with Quattor profiles – GENE-VO applications developed in P-Grade

4. HELIO HELIO - Introduction HELIO is designed to help the scientist in: finding, retrieving and analyzing data regarding the sun, its related phenomena and their effects on: the Earth, and, the other planets of the Solar System.

5. HELIO Technological Challenge Data and Metadata from the various instruments are: Dispersed Non completely standardized There is a complex feedback between data and metadata. Codes and Computational facilities are: Dispersed Non completely standardized Different User’s Profiles

6. Different users Users that possess a Grid Certificate Users that do not possess a Grid Certificate BUT are willing to login to the HELIO portal Users that do not possess a Grid Certificate AND are NOT willing to login to the HELIO portal Security Prefer to use IDL code Prefer to use HELIO Portal Prefer to write workflows HELIO Access Layer + HELIO API + Community Interaction Service HELIO Access Layer + HELIO API + Community Interaction Service

7. Different Resources Low Security Authentication High Security Authentication Authorization Simple User Profile

8. HELIO Architecture (Abstract) Resources Data & Metadata Data & MetadataStorage Computation Computation Existing Code Existing Code Security Security HELIO Service HELIO Service HELIO Service HELIO Service HELIO Service HELIO Service Access Layer Access Layer HELIO API HELIO API Web Service Web ServiceBased IDL, Java IDL, Java Decoupling layer Decoupling layer Hides unnecessary Information Hides unnecessary Information Connects to services independently Connects to services independently Use them in a workflow Use them in a workflow Use a GUI Use a GUI

9. The Access Layer and API Service I API HFE Workflow Engine (Server) Workflow Engine (Desktop) Standalone GUI

10. Overall Architecture

11. How to merge HELIO and SCI-BUS ? ?

12. Interesting areas User access: – Port the Helio Front End into WS-Pgrade ? – How to give access to IDL-Oriented users ? Resources access: – How to merge the storage and processing services into SCI-BUS ? – How to merge the HELIO security model into SCI- BUS ? General architecture issues: – How to merge the HELIO API ? – How to merge the other HELIO services ?

13. WS-PGrade as Grid Ireland User Interface Move Grid Ireland users to WS-Pgrade. – How to support the users that still wand a text- based approach ?

14. The Community Interaction Service Authentication Back End Community Interaction Service Community Interaction Service Access Layer & API Access Layer & API HELIO Identity Token

15. The HELIO Identity Token 1/2 Through Portal and APIDirectly through API Grid Certificate UID Personal proxy certificate User Profile UID Personal proxy certificate User Profile Login/Password UID Robot Proxy certificate User Profile UID User Profile Anonymous UID Robot Proxy certificate User Profile UID User Profile

16. The HELIO Identity Token 2/2 Proxy-based component (for high level of security) UID-based component (for low level of security) KM234454353GD User Profile (Based on the ClassAd language) [Service=HEC; Preference=...;] [Service=HEC; Preference=...;]