1. Application Specific Module Tutorial Zoltán Farkas, Ákos Balaskó 03/27/2012 1

2. Outline General Session: Goal gUSE orchestration Way from application to service Comparison Terminology Basic Idea Concept of ASM 2

3. Goal End users 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

4. 4 gUSE orchestration gUSE WS-PGRADE ASM Application Specific Interface Remote access API Client side Server side Remote access client Full access 90% access of internal services 60% access of internal services Limited access 20%

5. Way from application to service Simple Application Complex Workflow Personal CommunityApplication Specific Module Remote API general gUSE Own Research Usage Types Our Suggestions

6. Remote API vs. ASM Remote API: Pro: Servlet-technology Language-independent Hidden complexity Easy API Cont: Workflow must be on „client side” No workflow management Tight range of functionalities

7. Remote API vs. ASM ASM API: Pro: Wide range of functionalities Covers whole workflow-lifecycle Workflow management Hidden complexity Easy API Cont: Language-dependent (Java)

8. 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

9. Terminology Portal Administrator: installs gUSE Grid Application Developer Develops a grid application with gUSE Exports it to the local repository of gUSE End Users 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) 13

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

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. Technical details Provided functions:

24. Technical details FuncionalityMethodReturn TypeDescription Get List of Workflow Developers getWorkflowDevelopers String[] get a stringlist of applivation Developer IDs that have exported at least one application to the local repository according to the necessary requirements (see ApplicationType object) Get ASM workflows getASMWorkflows List Returns a list of ASMWorkflow objects which are the applications of the user Import ImportWorkflow Void Imports an application from the local shared repository to the user space Download Output getFiletoPortalServer Void Downloads the needed file to the portal server Download Output getFileStream Stream Returns the file in a stream Upload uploadFiletoPortalServer Void Uploads a file to the portal server Associate a file for a port placeUploadedFile Void Place a file that has been already uploaded to portal server, in a workflow as an input file Submit submit Void Submits an imported application Get Status getWorkflows -> Overall status statistics in JobStatistics bean List Gets general status statistics about the workflow that is being executed Get Detailed Status getDetails WorkflowInsta nceBean returns detailed status codes about every job that is being submitted according to the application (it returns) Rescue rescue ASMService Rescues an application Abort abort ASMService Aborts an application

25. End of General Session! Questions? Knowledge about JAVA+web-technologies are needed for followings!