1. Convert generic gUSE Portal into a science gateway Akos Balasko

2. Outline 1. Motivation 2. Terminology 3. Basic Idea 4. Concept of ASM 5. Classification of API methods 2

3. Motivation Representative teams of scientific communities want to build a Science Gateway for commonly used applications. See details in SCI-BUS project... See some examples →

4. Goal Community members want to: Execute scientific applications Using distributed systems to: decrease time cost Exploit storage & computational capacities use complex systems totally hidden Do not want to : learn any techniques that don't fit with scientific area of them → would like to use web-interfaces based on gUSE

5. Example gateways for Scientific Communities

6. Where are we now? 6 ASM API WS-PGRADE UI Customized UI Other, existing UI WS-PGRADE workflow UI

7. Terminology Grid Application Developer – would like to have a Portal customized for the application and end user community – knows how to develop a grid application in gUSE/ws-PGrade or how to port a legacy application to the grid with gUSE/ws- PGrade Grid Portal Developer – He knows the Java language and JSP (Java Server Pages) or other techniques (IceFaces etc) – He does not need to know the source code of gUSE – He and also the end users have user certificates to access the grid

8. Grid Application Developer: – Develops a new application – App. must be offered for others through a Web-based portal → Portal is highly customised for the application and the user community. People: – Do not know grids – Should be able to execute the grid application with their own custom inputs – Using the Web portal. Application specific portal Grid application developer End users Goal

9. Terminology Grid Application Developer Develops a grid application with gUSE Exports it to the local repository of gUSE End Users, Scientists execute a copy of the exported application with custom input parameters Grid Portal Developer Develops an interface (in general a portlet) that fits to the application I/O pattern and the end users’ needs and associate it with the role Connects the GUI to gUSE using the programming API of Application Specific Module(ASM)

10. Basic idea A new module called “Application Specific Module” has been developed for gUSE that ease the creation of Application Specified Portlets –The module provides programming API to control applications developed using gUSE –The module provides programming API to access inner gUSE services Any kind of Graphical interface can be developed on top of this module –GUI written in JSP, JSTL (Java Servlet Tag Library ) and Java –GUI can be customized for the grid application –GUI can be customized for end users

11. Concept ws-PGrade Internal components submitter Desktop or Service grids / cloud / Clusters DCIs gUSE Web browser Client 11

12. Concept ws-PGrade Internal components submitter Desktop or Service grids / cloud / Clusters DCIs gUSE Web browser Client Developed web-interface 12 We will focus on this!

13. Concept in details Web browser Client Developed web- interface Web pages (JSP, JSF or other) JAVA event handler, and inner classes Application Specific Module API Configuration files (wsdd) You develop it 13

14. Concept ws-PGrade Internal components submitter Desktop or Service grids / cloud / Clusters DCIs gUSE Web browser Client Developed web-interface 14 Placing web-app as gUSE component

15. DCI systems gUSE ws-PGrade Submitter Workflow Interpreter Repository Workflow Storage Storage Information User space Concept in details 15

16. DCI systems Grid Application Developer creates own Grid Application via ws-PGrade and export it to the local repository gUSE Repository ws-PGrade Grid Application Submitter Workflow Interpreter Workflow Storage Storage Information User space Concept in details 16

17. gUSE DCI systems Then the Grid Portal Developer creates a new web-application (mainly an web-interface) which fits to the user community's needs, and connects it to the gUSE using ASM API ws-PGrade Developed web- interface ASM Repository Grid Application Submitter Workflow Interpreter Workflow Storage Storage Information User space Concept in details 17

18. gUSE DCI systems Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet ws-PGrade Developed web- interface ASM Repository Submitter Workflow Interpreter Workflow Storage Storage Information User space Grid Application Concept in details > 18

19. gUSE DCI systems Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet ws-PGrade Developed web- interface ASM Repository Submitter Workflow Interpreter Workflow Storage Storage Information User space Grid Application Concept in details 19

20. gUSE DCI systems Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet ws-PGrade Developed web- interface ASM Repository Grid Application Submitter Workflow Interpreter Workflow Storage Storage Information User space Concept in details 20

21. gUSE DCI systems Finally the end-users create own application from the exported one, parameterize and execute it using the developed portlet ws-PGrade Developed web- interface ASM Repository Submitter Workflow Interpreter Workflow Storage Storage Information User space Grid Application Concept in details 21

22. gUSE DCI systems Then get back the results ws-PGrade Developed web- interface ASM Repository Submitter Workflow Interpreter Workflow Storage Storage Information User space Grid Application Concept in details 22

23. Classification of API methods Methods are provided for full scale of a) Workflow/Job Configuration a) Uploading inputs b) Settings input values c) Setting mysql query results as inputs d) Setting execution resources b) Execution management a) Submission/Resume/Abort b) Output retrieving possibilities offered by WS-PGRADE/gUSE But note: nothing for changing the workflow structure itself 23

24. Technical details and try-out tomorrow... Thanks for your attention! Questions?