Developing Application Portals using the GridPort Client Tools (GCT)

1. Mary Thomas, Steve Mock, Kurt Mueller {mthomas,mock,kurt}@sdsc.edu Presented at the NPACI All Hands Meeting Training Class Sunday, February 25, 2001 Developing Application Portals using the GridPort Client Tools (GCT)

2. Agenda • Lecture • Introductions • GridPort Project Overview • Tour of GridPort Portals: • Genie • LAPK, GAMESS • Introdcution to the GridPort Client Tools • Accounts • Lab • Account setup • Using Genie • demoApp Portal

3. GridPort Architecture

4. What Can You do With GridPort Client Tools? • The GridPort Client Tools (GCT) provide application developers with the ability to create their own portals. Key Goal: • Clients just need to learn some basic HTML - focus on science. • Features: • Application website can be located on any server. • Connection to portal services is through the GCT: • https://portals.npaci.edu/client/tools/FUNCTIONS • Clients do NOT • Have to install complex code to get started: • webservers, no Globus, no SSH, no SSL, no PKI, etc. • Have to write complex interface scripts to access these services (we’ve done that already) • Takes advantage of the Service Portal (SP): • Full security model from the GridPort Toolkit • Connect to ALL PACI resources (expanding to workstations and cluster in 2001) • Portal user account services (personalization, etc).

5. What Can You do With GridPort Client Tools? • Limitations: • GCT V1.0: very low level set of features because of the complexities of managing HTTP/HTML/CGI environment: • How do you control webpage redirection? • Solutions • Extend current set of client scripts to allow more client variable controls • Develop Portal-to-Portal communication (avoids complexities of webpage redirection • Client and server-side XML • Goal: • Users create portals with Genie level capabilities (2002)

6. How do GridPort Client Tools Work? • GridPort model: two kinds of portals • Application Portals (AP): • Client HTML pages written by users • perfom computational science tasks • Service Portals (SP): • used by AP’s to get the job done • connect clients to Grid services, provide security, etc. • How? • Client AP calls CGI code residing on SP • Client uses simple HTTP <FORM ACTION=“URL”> • Clients assing values to pre-defined hidden tags • Pass data to the CGI scripts • User login, machine, file name • URLS to redirect to when tasks are done

7. Building an Application Portal

8. How do I Start Using the Tools ? • All the tools use the services provided by the NPACI Service Portal • Read on-line documentation & Download (soon): • https://portals.npaci.edu/client/examples/download • Read on-line documentation & Download (soon): • https://portals.npaci.edu/client/examples/download • Client Tools are accessed at: • https://portals.npaci.edu/client/tools • For a list of tools, see: • http://portals.npaci.edu/client/examples

9. What do I Need Use the Tools ? • Get a user account on a PACI funded resource • Get a user portal account • http://portals.npaci.edu/accounts • You need a website - your own local site • Access to website filespace • HTML • Perl/CGI • Javascript (just a little, if you like it) • Download GCT examples: • Modify any links/data options that you want • experiment

10. Authentication: Login Logout Check authentication state Jobs: Sumbit jobs to queues Cancel jobs Execute commands (command like interface) Files: Upload from local host Download to local host FTP – move FILE View Portal FILEpace (?) Commands: Pwd Cd Whoami Etc. Categories of GridPort Client Tools

11. GridPort Keywords: Authentication

12. GridPort Keywords: Jobs

13. GridPort Keywords: Files (general)

14. GridPort Keywords: Files (transfer)

15. GridPort Keywords: Files (manipulation)

16. GridPort Keywords: Commands

17. GridPort Client Tools: How Do They Work? user login.html https://portals.npaci.edu/client/tools/auth/login.cgi MyProxy SDSC Repository LoginFail LoginOK default login_success.html default login_error.html user login_error.html user login_success.html FORM/CGI action

18. GridPort Client Tools: Using Form Elements <FORM ACTION=https://portals.npaci.edu/client/tools/auth/cgi-bin/login.cgi target=“demoDataFrame”> Username:<input type=text name=AUTH_USERNAME > Passphrase<INPUT type=password name="AUTH_PASSPHRASE"> Use MyProxy<INPUT type=checkbox name="AUTH_TYPE_MYPROXY" value="true"> <!----REQUIRED: USED BY SERVICE PORTAL TO TRACK YOUR PORTAL MUST BE UNIQUE AND THE SAME FOR ALL REQUESTS FROM YOUR PORTAL- <INPUT type=hidden name="PORTAL_APP_NAME” value="GCT_EXAMPLES"> <!----REQUIRED: THIS IS WHERE THE SERVICE PORTAL WILL RETUR THE USER AFTER LOGIN. THIS CAN BE A WELCOME MESSAGE-----> <INPUT type=hidden name="AUTH_LOGIN_SUCCESS_URL“ value="https://portals.npaci.edu/client/examples/auth/login_success.html"> <!----REQUIRED: THIS IS WHERE THE SERVICE PORTAL WILL RETURN THE USER IN THE CASE OF A LOGIN ERROR-----> <INPUT type=hidden name="AUTH_LOGIN_ERROR_URL“ value="https://portals.npaci.edu/client/examples/auth/login_error.html"> </FORM>

19. References • GridPort Toolkit Website • https://gridport.npaci.edu • Contact: Mary Thomas (mthomas@sdsc.edu) • NPACI Genie User Portal • https://genie.npaci.edu • Account: • http://portals.npaci.edu/accounts • Contact: Kurt Mueller (kurt@sdsc.edu) • Download Example Portal (frames based) • http://portals.npaci.edu/client/examples/demoApp/ • Contact: Steve Mock (mock@sdsc.edu)