Portlets overview

1
Portlets overview
2
OMII-SP Portlet Suite

• SCAMP (Scoped Attribute Manager Portlet)
• Allows correct manipulation of the attribute
  acceptance policy of a Shibboleth Service
  provider
• CCP (Content Configuration Portlet)
• Creates a filtered view of the available services
  in a portal based on Shibboleth AuthZ attributes
• ACP (Attribute Certificate Portlet)
• Allows a portal manager to issue X.509 Attribute
  Certificates to users for access to services
• ARP (Attribute Release Portlet)
• Enables a Shibboleth Identity Provider to
  manipulate its released attribute set

3
OMII-SP Portlets Use Cases

• SCAMP
• Can integrate with ANY Shibboleth-enabled service
  in the UK (with portal functionality)
• CCP
• Will be used in nanoCMOS/VOTES projects
  multi-service portal
• ACP
• Deployed on any PERMIS-supporting service (VOMS
  authorisation service)
• ARP
• Used with any UK Shibboleth Identity Provider
• SCAMP and ARP intended as PORTAL ADMIN portlets
• i.e. system administrators
• ACP and CCP intended as SERVICE ADMIN portlets
• i.e. portlet authors

4
OMII-SP Roadmap

• SCAMP
• Design, implementation and deployment complete
• Debugging and coding compliance underway just now
• Release to OMII 1st week of November
• Can be tested by any Shibboleth enabled site
• CCP
• Design underway
• Looking at integration with RAPID portlet
  (provide authorisation function for users to
  apply)
• 1st prototype in new year
• ACP and ARP Q2 2008

5
The SCAMP Portlet View
Current, active eduPersonEntitlement attribute
set
Set/edit attribute properties
Choose sites (IdPs) you accept attribute from
Choose attribute values you are willing to accept
6
JSDL Application Repository Portal/Portlet

• A JSDL Repository
• Search/browse for JSDL (personal and shared) by
  category of interest (e.g bioinformatics,
  chemistry, tutorials/examples). Select, load,
  modify, save.
• JSDL documents can be pre-configured and
  published by domain experts / resource
  administrators (users benefit from sharing
  expertise, artefacts and configuration captured
  in JSDL).
• Community formation around a best practice
  approach (OGF).
• JSDL GUI Editor for authoring, validating,
  sharing, uploading application descriptions.
• Grid Operations Application Submission,
  Monitoring (run application either
  out-of-the-box, or modify/tweak/save as
  required).
• Data Operations Browsing data resources, file
  operations, data staging.
• Deploy as JSR168 portlet or standalone Web app.

7
Example Use Case (NGS Applications Repository)
https//portal.ngs.ac.uk Deployed as an open
Web app rather than a JSR168 portlet. Free to
browse pubic JSDL documents without log-in (free
to use JSDL editor). Login required to browse
personal applications, save and submit jobs,
interact with Grid resources. List jobs, read
job descriptions and load a job to initialise the
Active Job. Changes to the parameters in the
GUI will update and validate the JSDL template
automatically.
8
Roadmap

• Facilitate Staging from more Data Grid Web
  protocols (e.g. SRB, SFTP). Browsing / file
  operations with different data storage resources.
  Staging across different protocols adds much
  complexity (data buffering required via portal
  server). Dec 07.
• Middleware extensions, Dependent on SAGA. Next
  year.
• Improvements / refinements (e.g. AJAXify)
• Desired but currently out of scope
• Parametric and multiple job submissions
  (parametric JSDL extension schema defines
  parametric variables, functions, ranges for
  modifying JSDL doc for iteration).

9
My Job Detail

• Input fields are pre-configured / filled out.
• Fields are taken from the JSDL and JSDL-POSIX
  extension schemas.
• POSIXApplication is a JSDL extension. It defines
  standard POSIX elements.
• stdin, stdout, stderr
• Working directory
• Command line arguments
• Environment variables

? ?
/? ?

10
Environment Variables
/tmpent envVar
Value1 ..
11
Command Line Arguments
Paste and parse command line arguments (space
and/or line separated values)
fasta34 gument-H humanDN
A2.input /var/dat
a/bioinformatics/..
ntS
12
Named File Systems
Named file systems used to declare mount points
on the consuming system. File system names are
referenced throughout the portal (and JSDL doc)
for substituting mount points. Changes to a FS
mount point will be updated automatically
throughout the portal/JSDL. Used when
specifying path info e.g. locations to
files/dirs, stage data locations etc.

/home/ngs0024/myScratchDir

stem nameDataDir"
/home/ngs0024/myDataDir
ntPoint
filesystemName"WORKINGDIR" fasta.out

13
Stage Data
List of data from across the Grid that should be
copied to the consuming system Before job
src URI After job tgt URI JSDL does
not mandate the protocol / URI format. Data is
staged relative to named file systems.
Mg.psfjsdlFileName WORKINGD
IR
overwrite
false
ination
gsiftp//ngs.rl.ac.uk2811/apps/Siesta_m
pi/

14
Candidate Hosts
Candidate Hosts resources that can be used to
run the given application. The candidate host
list can contain personal and default hosts
(available to all users). In future, a RB
matchmaking will be used to select execute host
from candidate hosts.

ngs.rl.ac.uk2119
clyde.dl.ac.uk2119

15
Browse Host / Data Transfer

• File and recursive directory transfers between
  hosts
• File and directory operations
• Actions for updating application

16
Technical

• JSFv1.1 (Java Server Faces) GUI.
• JSR-168 compliant. Vanilla JSF (core spec) is
  JSR-168 compliant so can host as Web application
  or portlet within institutional portals (JSF
  extensions can be problematic).
• Spring v2.0 for managing objects in an n-tier
  server application (highly recommended, adds J2EE
  to non J2EE apps, e.g. Tomcat/Jetty apps).
• Declarative transaction demarcation (akin to EJB
  3 session beans).
• Data source management (e.g. JPA PstCtx,
  Hibernate Session).
• Propagation of Data Source across DAOs / session
  façades during long running transactions.
• C3p0 pooled database connections.
• JPA (Java persistence API) for ORM (object
  relational mapping). Hibernate 3.2 for domain
  model (could use Kodo, Toplink, apache openJPA).
• CogKit for Globus API from Globus.
• Object / Xml data binding framework. JAX-B.

17
Portlet Access GridEasy Free Access Grid
Anywhere

• This project is building a fully-functional
  portlet client for the Access Grid Toolkit
  version 3 (AGTkv3), with the new architecture
  allowing for automatic and transparent switching
  between unicast and multicast. In addition the
  system is designed to accommodate restrictive
  firewalls and low bandwidth connections, as well
  as being extremely simple to install.

http//www.rcs.manchester.ac.uk/research/PAG
18
Portlet Access Grid

• Join in an Access Grid using only a browser with
  Java installed
• Connect to any Access Grid Toolkit 3 Server
• Full access to all AGTk client features
• Join an AG session from a hotel room / internet
  cafe
• In addition to AGTk client, PAG will also
• Switch automatically between unicast and
  multicast
• Install toolkit services as required
• Support additional bridges including
  low-bandwidth bridges
• Access additional data storage

19
Portlet Access Grid
Multicast
Access Grid Toolkit Version 3 Server
BridgeServer
UDP/TCP
UDP
Java Web-Start Application
SOAP
XML-RPC
AJAX
Java Servlet
UDP
JavaScript
Session
LiveConnect
Vic / Rat / Other
JSP Pages
Java Applet
Java Portlet
20
Portlet Access Grid Key Features
A fully JSR168 compliant Access Grid Portlet
uPortal, GridSphere, Sakai,
Access Grid video and audio automatic Java
launching
Jabber text chat integration
21
Portlet Access Grid Key Features
The portlet is web-browser independent IE,
Firefox, Netscape,
Access Grid full virtual venue selection and
control
22
Portlet Access Grid Project
Development project within Research Computing
Services at the University of Manchester
http//www.rcs.manchester.ac.uk/research/PAG
Acknowledgements to OMII-UK portal projects
programme as well as support through ESNW and the
AGSC at the University of Manchester.
Andrew.Rowley_at_manchester.ac.uk Tobias.Schiebeck_at_ma
nchester.ac.uk Anja.LeBlanc_at_manchester.ac.uk Marti
n.Turner_at_manchester.ac.uk Michael.Daw_at_manchester.a
c.uk
Contact