|
|
|
|
|
|
Contextualise SPP |
|
Funding Body, JISC IE |
|
Rationale, Deliveries & Guiding Principles |
|
Partners, Project Structure & Features |
|
Portals |
|
General, JISC & SPP Perspectives |
|
Portal Frameworks & Related Standards |
|
Portlets |
|
Functionality |
|
Access Management Functionality |
|
Athens |
|
LDAP/SSL |
|
Conclusion |
|
Where We Are Now |
|
Exit Strategy |
|
Demo |
|
|
|
|
|
|
Joint Information Systems Committee (JISC) |
|
Promote and Disseminate Best Practice |
|
Information Communication and Technologies (ICT) |
|
Higher and Further Education (HE/FE) |
|
Serving 600+ UK Institutions |
|
Information Environment Context |
|
|
|
|
|
|
Current UK JISC Information Environment |
|
Multiple Disparate Information Resources and
Services |
|
Learning, Teaching & Researching |
|
Different User Interfaces |
|
Search, Browse, Alert, … |
|
|
|
|
|
|
|
|
|
SPP |
|
Two Year (August 2001/03) |
|
Develop Subject Portals |
|
Distributed and Collaborative Project at the RDN
Hubs |
|
SPP Exit Strategy |
|
One Year (September 2003) |
|
Upgrade the Project to a Service |
|
Allow Hubs to Present Enhanced Subject-based
Portal View of Relevant Content |
|
JISC IE Collections |
|
Hub’s Information Resource Catalogues (IRC) |
|
Deliveries |
|
Upgrade Hub Services to Portals |
|
|
|
|
|
|
Distributed and Collaborative Development Team |
|
Support |
|
Portal Development in Each Hub |
|
Produce |
|
Portal Framework Independent Functionality |
|
Commitment Wherever Possible |
|
Open Source |
|
Open Standards |
|
Accessibility |
|
Usability |
|
|
|
|
|
|
|
|
|
|
|
|
Distributed Collaborative Development Team |
|
Features |
|
Identifying Functionality |
|
Initial Requirements |
|
Questionnaire Survey |
|
Consultancy Groups |
|
Modelling the Functionality (UML) |
|
Common Development Environment |
|
Version Management (CVS) |
|
Synched via Email and available via HTTP |
|
Bug Tracking Software (RT) |
|
Standard Build Environment (Ant) |
|
Project and Developer’s Fora |
|
Web Sites |
|
Mailing Lists |
|
|
|
|
|
|
|
Distributed Collaborative Development Team |
|
Features |
|
Meetings |
|
Virtual:
Weekly (IRC) |
|
Face-to-Face: Frequently (TRAIN) |
|
Pub: Sometimes (BEER) |
|
Strengths |
|
Sharing Knowledge |
|
Stopping Duplication of Effort |
|
Weaknesses |
|
Synchronisation |
|
Overlapping |
|
Tensions |
|
|
|
|
|
|
|
|
|
Infrastructure for Services |
|
Similar to a Windows-based Operating System |
|
Basic Services |
|
Windows Management |
|
Security |
|
Registry |
|
… |
|
Services |
|
Similar to a Window |
|
GUI Applications |
|
Provide Access to the Content |
|
|
|
|
|
JISC Definition |
|
Technically, a portal is a network service that
brings together content from diverse distributed resources using
technologies such as cross searching, harvesting, and alerting, and
collates this into an aggregated form for presentation to the user, usually
via a website. |
|
Typical Features |
|
Single Point of Access (One Stop Shop) |
|
Resources & Services brought together from
1+ source |
|
Security |
|
Aggregation & Integration |
|
Personalisation & Customisation (one size
does not fit all) |
|
Sense of Community |
|
…. |
|
|
|
|
|
|
|
Portal Framework |
|
Supporting Software to Provide Access to the
Content, but Independent of the Content |
|
Independent of the User’s and Content Software |
|
Users Access From Anywhere |
|
Via Preferred Web Browser |
|
Seamless Access to Resources |
|
Built-in Functionality |
|
Security |
|
Access Management (Authentication &
Authorisation) |
|
Personalisation |
|
User/Group Profiles |
|
Presentation |
|
Variant of Model View Control (MVC)
Paradigm (e.g. JSP,
XSP, Velocity , XML/XSLT) |
|
|
|
|
|
|
|
|
Portlets |
|
Web Components such as Servlets |
|
Abstractions or Metaphors |
|
Channels, Modules, Etc. |
|
Plugable Functionality |
|
Common Integration Layer |
|
Between the Content and the Presentation |
|
Standards to Access the Content |
|
Z39.50, SOAP, XML/RSS, SMTP/POP3/IMAP… |
|
Standard-based |
|
JSR 168, WSRP, … |
|
Ensure Interoperability Across Different Portal
Frameworks |
|
Third Party Development Potentially Reduces Time
and Cost Becoming Crucial for the Institution’s Core Business
Infrastructure |
|
|
|
|
|
|
Currently |
|
Jetspeed |
|
Portal Framework |
|
Portlets Abstraction |
|
Java Based |
|
Open Source (Apache) |
|
Open Standards (JSR 168, ?WSRP?) |
|
Exit Strategy – September 2003 |
|
uPortal |
|
Portal Framework |
|
Channel Abstraction |
|
Java Based |
|
Open Source (JA-SIG) |
|
Open Standards (WSRP, ?JSR 168?) |
|
|
|
|
|
Criteria? |
|
Integration with Existing Functionality |
|
Easy to Develop New Functionality |
|
Programming Language Independence |
|
Standards to Access Content |
|
Standards for Interoperability and Portability |
|
|
|
|
|
|
Java Specification Request (JSR) 168 |
|
Java Community Process (JCP) |
|
Open Organisation of Java Developer Institutions
with the remit to develop and revise specifications, reference
implementations for the Java Platform |
|
Portlet Abstraction |
|
Java Portlet API |
|
Interoperability and Portability |
|
Status |
|
Community Review: April 2003 |
|
Public Review: June 2003 |
|
Release Version 1.0: August 2003 |
|
|
|
|
|
|
Web Services for Remote Portals (WSRP) |
|
Organization for the Advancement of Structured
Information Standards (OASIS) |
|
World-Wide Consortium that Drives the
Development, Convergence and Adoption of e-Business Standards |
|
Portlet Abstraction |
|
XML and Web Services to Specify, Exchange and
Plug Portlets in any WSRP-Compliant Portal Framework |
|
Interoperability and Portability |
|
Status |
|
Approved for Public Review: 31st May |
|
IBM and Vignette have Draft Implementations |
|
|
|
|
|
|
|
JSR 168 vs. WSRP |
|
Work at Different Levels |
|
JSR 168 Specifies the Interfaces for Local
Portlets |
|
WSRP Specifies the Interfaces for Exchanging
Portlets for Remote Portal Frameworks |
|
Have to be Aligned |
|
Same Notion of the Objects |
|
Instantiate Locally the Portlets |
|
Details of the Portlet API have to be Exposed to
WSRP in order to Exchange them |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Portal Framework |
|
Bridges (ILRT) |
|
Plug-ins |
|
Access Management (HUMBUL) |
|
User Profiling (BIOME) |
|
Portlets |
|
Abstract Portlet (ILRT) |
|
Functionality |
|
Cross Searching (SOSIG) |
|
Alerting (EEVL) |
|
News-Feeds (PSIgate) |
|
Additional Services (???, Exit Strategy) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Classical API |
|
Username/Password |
|
Athens Single-Sign On (AthensSSO) |
|
Login Once at the Athens Authentication Point
(AAP ) |
|
Authentication Protected Domain |
|
Use a Ticket for Every Other Athens Protected
Resources/Services (DSP) |
|
Valid for a Browser Session or for 8h |
|
User Just Exchanges Transfer Tokens |
|
Valid for 60s |
|
Athens Single-Sign On++ (AthensSSO++) |
|
Extend SSO to Access non-HTTP-SSO DSPs |
|
|
|
|
|
|
Devolved Authentication (AthensDA) |
|
Institution use their own “Trusted”
Authentication System |
|
Can be Implemented |
|
LDAP-based Authentication |
|
Digital Certificates within a PKI |
|
Institution's VLE |
|
Provide Just Authorisation |
|
Similar to Shibboleth (Internet2) |
|
Relies on AthensSSO++ |
|
|
|
|
|
|
|
|
AthensSSO++ Already Integrated |
|
Consists of Two Parts |
|
AM Interceptor |
|
Redirects the user to the AAP |
|
Provides Transfer Tokens for Authentication |
|
AM Implementation |
|
Login Modules |
|
Integrated in the Portal Framework |
|
Portal Service as a Web Service via SOAP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Access Management |
|
Package |
|
AthensSSO++ for National Authentication |
|
LDAP/SSL for Local Authentication |
|
Approach Proved to be Reasonable |
|
Flexible to Work with Multiple AMSs |
|
New Login Modules Developed in Few Days |
|
SPP is Working with X.509 Certificates |
|
Prepare SPP for the Future JISC AMS |
|
|
|
|
|
|
SPP |
|
End of Round 2 Phase |
|
See Demo |
|
Following |
|
Local User Testing (15 May) |
|
Round 3 Phase (June/August) |
|
Prototype Subject Portals |
|
Documentation |
|
Dissemination |
|
Exit Strategy |
|
|
|
|
|
Portal Framework |
|
Write New Bridges for Plug-ins L |
|
Integrate AM Interceptor L |
|
Reuse Existing Plug-ins J |
|
Portlets |
|
Write a Bridge for the Abstract Portal L |
|
Reuse Existing Functionality J |
|
|
|
|
|
|
|
|
|
Subject Portals Project |
|
http://www.portal.ac.uk/spp/ |
|
SPP
Additional Services Research |
|
http://www.eevl.ac.uk/public/ASP/info/ |
|
Resource Discovery Network |
|
http://www.rdn.ac.uk/ |
|
JISC |
|
http://www.jisc.ac.uk/ |
|
JISC UK Information Environment |
|
http://www.jisc.ac.uk/dner/development/IEstrategy.html |
|
The Future of Authentication for JISC Services |
|
http://www.jisc.ac.uk/pub02/ar1/future_auth.html |
|
Notes