1 / 15

A Service Oriented Architecture for Portals Using Portlets

A Service Oriented Architecture for Portals Using Portlets. Asif Akram, Dharmesh Chohan, Xiao Dong Wang, Xiaobo Yang and Rob Allan CCLRC e-Science Centre, CCLRC Daresbury Laboratory Warrington WA4 4AD, UK. Service Oriented Architecture. Advantages etc. of SOA: Modular software Re-usable

ddionne
Download Presentation

A Service Oriented Architecture for Portals Using Portlets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Service Oriented Architecture for Portals Using Portlets Asif Akram, Dharmesh Chohan, Xiao Dong Wang, Xiaobo Yang and Rob Allan CCLRC e-Science Centre, CCLRC Daresbury Laboratory Warrington WA4 4AD, UK

  2. Service Oriented Architecture Advantages etc. of SOA: • Modular software • Re-usable • Loosely coupled • Components can be developed independently and swapped in/ out based on an agreed API • Agreed protocols/ standards • Can be pluggable in one application, e.g. JSR-168 portlets • Can be distributed using Web services, e.g. WSRP • Components/ agents are self contained • Web services mean language independence • Perl, Java, C, Python, PHP, etc. • So, can wrap existing “heritage” applications (R, C, Fortran, etc.) Facilitates working as a distributed team – Conway’s Law(Herbsleb and Grinter, IEEE Software, September 1999, pp63-9)

  3. JISC e-FER E-Framework for Education and Research • Part of the Integrated Information Environment • Development of terminology and procedures for an SOA • Integration of many existing tools and services • Collaboration, education and research -> personal learning • Research -> information -> learning life cycle • Customisation to end-user requirements • Promote standards and re-usability • International partners

  4. Common Service Component Framework

  5. E-Research Framework Choices now • Portal Software: • uPortal, GridSphere, Liferay, StringBeans, Jetspeed2, JBOSS, eXo Platform • We are evaluating these in a collaboration with Jason Novotny and will produce a technical report • JSR-168 portlets have been demonstrated to be portable between frameworks • WSRP is becoming useable • .NET not yet evaluated • Digital Repository Software: • Fedora, DSpace, Plone • Collaborative Software: • Sakai, Sharepoint, NaradaBroker, Lotus Notes, OpenOffice ? • Web Services and loose coupling are helping us to realise the vision.

  6. Portals and Web Services JSR-168, WSRP WSRP Portlet Portlet Portlet SOAP, WSDL, UDDI Service Service Service Common Services Common Services

  7. WP2: So what Tools are we working with? Sakai Collaboration Tools • Schedule • Resources • Web Content • Chat • Discussion • E-Mail New Sakai Tools • LDQ Upload • Whiteboard • CopperCore • IRC • Wiki • Audio Conferencing • Resource Search CREE InformationTools • JAFER • GetRef • HEIRPORT • Google Grid Tools • MDS LDAP Browser • Grid Proxy Manager • Grid Job Submission • Grid Job monitor • Grid FTP • InfoPortal Other Portlets • Narada Conferencing • Semantic Search Grid Markets Tools • Negociation Client • Payment Service Client Data Management Tools • SRB • OGSA-DAI Service Registry • UDDI publish/ discovery • Dynamic WSDL Interface Support Tools • Certificate Upload • Desktop FTP

  8. WSRP Activities Sakai/ uPortal • SunGard-led and funded: Vishal Goenka • Working with uPortal in their WSRP uPortal 3.0 effort • As we really try to use WSRP, we identify issues in the standard and WSRP4J implementation • Sakai and uPortal are becoming involved in WSRP standards activities and WSRP4J UK e-Research community will organise a WSRP workshop for early 2006 • Sign up to eResearch@jiscmail.ac.uk for information

  9. WSRP“Portal” WSRP Consumer Portal Apache WSRP4J WSRP Placements Sakai WSRP Sakai Sites Kernel Tool Registry Request Filter Tool A Tool B Tool C Web Services

  10. WSRP Image

  11. Portal Frameworks • Sakai http://www.sakaiproject.org • Broadly used in Collaborative Learning Environments • Separate Sakai Evaluation Exercise done for JISC http://www.grids.ac.uk/Sakai/sakai_doc • uPortal http://www.uportal.org • Widely used for academic institutional portals • GridSphere http://www.gridsphere.org • Earl adopter of JSR-168, EU GridLab project • eXo Platform http://www.exoplatform.com • Populat plaform • LifeRay http://www.liferay.com • Popular, good user interface, optional functionality • StringBeans http://www.nabh.com/projects/sbportal • Ease of use

  12. Evaluation Procedure • JSR-168 compliance • Ease of installation • Documentation standards • On-line support • Including helpdesk, Web site, Wiki etc. • Portal management • Ease of deploying portlets, adding users, assigning roles and categories, skining, customisation, etc. • Portlet resources • Built in, e.g. Grid, calendar, mail, search • Performance and scalability • Startup time, deployment time, db access time, etc. • Security • Compatibility with JAAS, JOSSO, SSL, etc. • Technology used • Struts, JSF, Spring, Hibernate, Tiles, EJB, Web services, etc. • Portal features • CMS, Workflow, Admin tools, Monitoring tools, etc. • Server dependency • WSRP compliance • Producer or consumer

  13. Evaluation Results

  14. Evaluation Results (2)

  15. The Future? Web Services/Tools WS/WSRP WS/WSRP WSRP Desktop WS/WSRP WS/WSRP uPortal Registry

More Related