Web2.0 Ajax and REST in WebSphere Portal

10,683 views

Published on

Published in: Technology
1 Comment
4 Likes
Statistics
Notes
  • This is great. Loved it.

    http://www.kidsbathroomsets.org/
    http://www.kidsbathroomsets.org/BathAccessoriesForKids.php
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
10,683
On SlideShare
0
From Embeds
0
Number of Embeds
500
Actions
Shares
0
Downloads
209
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide
  • Web2.0 Ajax and REST in WebSphere Portal

    1. 2. ID506: Web 2.0, AJAX, and REST in IBM WebSphere Portal Thomas Schaeck, STSM Lead Architect Quickr and WebSphere Portal Web 2.0 Stephan Hesmer WebSphere Portal Web 2.0 Architect and Lead Developer
    2. 3. What is Web 2.0, AJAX and REST ?
    3. 4. What is Web 2.0 ? <ul><li>A term coined by Tim O‘Reilly (see http:// www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html ) </li></ul><ul><li>Increasingly used for next generation World Wide Web Applications and Services </li></ul><ul><li>Web 2.0 has many aspects: </li></ul><ul><ul><li>Business Models that survived and have promise for the future </li></ul></ul><ul><ul><li>Approaches such as services instead of products, the Web as a platform, ... </li></ul></ul><ul><ul><li>Concepts such as folksonomies, syndication, participation, reputation, .... </li></ul></ul><ul><ul><li>Technologies such as AJAX, REST, Tags, Microformats, ... </li></ul></ul><ul><ul><li>And many others ... </li></ul></ul>
    4. 5. How do Web 2.0 Sites differ from „Web 1.0“ Sites ? <ul><li>Strict „Web 1.0“ site </li></ul><ul><ul><li>„ Web Master“ runs web site, users consume </li></ul></ul><ul><ul><li>Few content editors </li></ul></ul><ul><ul><li>Web site provides content and applications for users </li></ul></ul><ul><ul><li>View-only markup </li></ul></ul><ul><ul><li>Only human users </li></ul></ul><ul><ul><li>Accumulates relatively small amounts of information and content </li></ul></ul><ul><ul><li>Fixed categories / Taxonomy </li></ul></ul><ul><ul><li>Unidirectional </li></ul></ul><ul><li>Modern „Web 2.0“ site </li></ul><ul><ul><li>Users collectively contribute to the web site, they don‘t just consume </li></ul></ul><ul><ul><li>Every user is a content editor and rater </li></ul></ul><ul><ul><li>Web site provides content, applications, and collective contributions of all users </li></ul></ul><ul><ul><li>Semantically tagged markup </li></ul></ul><ul><ul><li>Humans and applications as „users“ </li></ul></ul><ul><ul><li>Accumulates huge amounts of information and content </li></ul></ul><ul><ul><li>FlexibleTagging / Folksonomy </li></ul></ul><ul><ul><li>Bi-directional </li></ul></ul>Web Site Web Site Data Data App App App App
    5. 6. Observations <ul><li>Web 2.0 consists of social and technical aspects </li></ul><ul><li>The social aspects of Web 2.0 are much more fundamental than the technologies </li></ul><ul><li>Web 2.0 Sites can derive huge value from their user community if they achieve critical mass  Some Web 2.0 companies have achieved extremely high market captialization (Google ($109,66 bn) bought YouTube for $1,65 bn) </li></ul><ul><li>The Web 2.0 Site itself often only provides the infrastructure and guidelines for user participation </li></ul><ul><li>The community then adds value to the site, e.g. by writing articles, posting videos, sharing bookmarks, etc </li></ul><ul><li>Typically, these Web 2.0 sites have APIs for use by developers of mashup applications acting as multipliers </li></ul><ul><li>Web 2.0 user interfaces typically apply the AJAX technology in order to achieve more responsive UIs </li></ul>
    6. 7. What is AJAX ? <ul><li>AJAX is the acronym for A synchronous J avaScript a nd X ML </li></ul><ul><li>The purpose is to create more dynamic and responsive web pages </li></ul><ul><li>It is also about building web clients in a Service Oriented Architecture that can connect to any kind of server: J2EE, PHP, ASP.Net, Ruby on Rails, etc. </li></ul><ul><li>AJAX involves existing technology & standards: JavaScript and XML </li></ul><ul><li>Pattern: Page view displayed in a web browser retrieves data or markup fragments from a service and refreshes just a part of the page </li></ul><ul><li>AJAX is non-trivial, it requires deep and broad skills in web development ... ... but the benefits to be gained can be huge compared to classic web applications </li></ul><ul><li>AJAX enables major improvements in responsiveness and performance of web applications, e.g. used at Yahoo! Mail, Google Maps, live.com, and others </li></ul><ul><li>AJAX is NOT hype – it is very real and very useful for highly interactive applications </li></ul>
    7. 8. AJAX compared to classic Web UIs Browser Server Browser Server service In the typical web application, each request causes a complete refresh of the browser page An Ajax application begins the same way. After the initial page loads, Javascript code retrieves additional data in the background and updates only specific sections of the page <ul><li>Ajax forces you to think about discrete services. </li></ul><ul><li>It may drive requirements for new services from your IT department </li></ul>
    8. 9. What is REST ? <ul><li>REST is the acronym for „ Re presentational S tate T ransfer“ </li></ul><ul><li>It is the architectural model on which the World Wide Web is based </li></ul><ul><li>Principles of REST </li></ul><ul><ul><li>Resource centric approach </li></ul></ul><ul><ul><li>All relevant resources are addressable via URIs </li></ul></ul><ul><ul><li>Uniform access via HTTP – GET, POST, PUT, DELETE </li></ul></ul><ul><ul><li>Content type negotiation allows retrieving alternative representations from same URI </li></ul></ul><ul><li>REST style services </li></ul><ul><ul><li>are easy to access from code running in web browsers, any other client or servers  very popular in the context of AJAX </li></ul></ul><ul><ul><li>can take full advantage of the WWW caching infrastructure </li></ul></ul><ul><ul><li>can serve multiple representations of the same resource </li></ul></ul><ul><li>More info: http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm </li></ul>
    9. 10. Web 2.0 Concepts that are interesting for enterprise use <ul><li>Self-establishing Communities collaborating around topics of common business interest </li></ul><ul><li>Support User Contribution , treat users as co-authors and leverages their skills better </li></ul><ul><li>Accumulation of user knowledge to make apps smarter the more people use them </li></ul><ul><li>Enable users to add value by adding meta data, e.g. rate, tag, bookmark, comment </li></ul><ul><li>Allow users to Take Control and let them make applications most useful to them </li></ul><ul><li>Separate User Interface from Services to make services re-usable </li></ul><ul><li>Fine grained access to data supporting mashups </li></ul><ul><li>Mashups combining existing services into new, useful applications joining information </li></ul><ul><li>Situational Development of applications through line of business can help make businesses more agile </li></ul><ul><li>AJAX to enable rich, interactive, highly responsive Web UI </li></ul><ul><li>Use of Semantic Tags and Microformats to enable dynamic augmentation with contextual menus or information </li></ul>
    10. 11. Web 2.0 in WebSphere Portal
    11. 12. IBM WebSphere Portal is the User Interface to SOA MS Office & Windows Other Clients Web Browser Rich Clients Mobile Client Presentation Services eForms Xforms Other Clients
    12. 13. WebSphere Portal 6 Overview <ul><li>Instant messaging </li></ul><ul><li>Team Rooms </li></ul><ul><li>Electronic Forms </li></ul><ul><li>Workflow Builder </li></ul>WebSphere Portal Extend <ul><li>Web Content Management </li></ul><ul><li>Portal Document Manager </li></ul><ul><li>Workflow Engine </li></ul>WebSphere Portal Enable <ul><li>Presentation </li></ul><ul><li>Customization </li></ul><ul><li>Application aggregation </li></ul><ul><li>Java Portlet API </li></ul><ul><li>Use of 100’s of portlets </li></ul><ul><li>WSRP support </li></ul><ul><li>Admin </li></ul><ul><li>Single sign on </li></ul><ul><li>Search </li></ul><ul><li>Personalization </li></ul><ul><li>Portlet Generation Tool (Portlet Factory) </li></ul><ul><li>Composite Applications </li></ul><ul><li>Cluster Support </li></ul><ul><li>Application Server </li></ul><ul><li>Database </li></ul><ul><li>LDAP Directory Server </li></ul>WebSphere Portal Server
    13. 14. WebSphere Portal – An Example <ul><li>w3 portal for all IBM employees </li></ul><ul><li>> 300,000 users </li></ul><ul><li>Portlets provide essential information </li></ul><ul><li>Highly personalized - displays the right info to the right users at the right time </li></ul><ul><li>End-user customizable - users can create custom pages </li></ul><ul><li>Has become a key tool for every IBMer </li></ul><ul><li>Major productivity gain </li></ul><ul><ul><li>Targeted info delivery to users </li></ul></ul><ul><ul><li>Users can easily find the apps they need </li></ul></ul>
    14. 15. Portals are the way to provide governed business mashups combining public information, enterprise apps and data Openness Critical enabler: Standards based access to integration and innovation Thin Clients Mobile Clients Rich Clients Security-Rich Composite application or view, that assembles and delivers services in the form of portlets in the context of a business process role-based composite applications in context process- driven
    15. 16. Web 2.0 / AJAX / REST in WP and related Products - Today <ul><li>WP 6 allows User Contribution to portal sites through both WCM and PDM </li></ul><ul><li>WP 6 enables Situational Development through Composite Application Templates and through Lotus Designer / Portlet Factory / Forms Designer </li></ul><ul><li>WP 6 allows users Taking Control of their pages and choose content (if allowed by admin) </li></ul><ul><li>Custom AJAX Portlets can be written today to run on WebSphere Portal, e.g. using the Dojo framework and widgets or the AJAX support in RAD </li></ul><ul><li>WP 6.0 exploits AJAX for context menus, search menu, and some admin portlets </li></ul><ul><li>WebSphere Portlet Factory can generate AJAX Portlets with incremental update and autocomplete </li></ul><ul><li>IBM is strongly engaged in Dojo (see http://dojotoolkit.org/ ) as major contributor </li></ul>
    16. 17. Disclaimer <ul><li>The following includes material that is directional in nature and does not imply any product plan commitment on the part of IBM. </li></ul><ul><li>Screenshots in this presentation are from prototypes and likely to change significantly by the time products are released </li></ul>Eyebrow /breadcrumb (text below business unit or product name): 14pt Arial Regular, light gray R128 | G128 | B128 Text slide with single quote or statement Singe quote on page: 28pt Arial Italic, teal R204 | G 255 | B153 Reference: 20pt Arial, Regular black
    17. 18. New Web 2.0 Work under development for WebSphere Portal <ul><li>REST Services to open up portal for mashup applications – services for server persistence, portlet settings and user profile access to simplify Web 2.0 application development </li></ul><ul><li>AJAX Portlet Programming Model Extensions based on Dojo+IBM Extensions </li></ul><ul><li>Client Side Aggregation and Customization using REST Services for better UX and improved performance </li></ul><ul><li>AJAX Client Side Feed Consumption to enable highly efficient integration of information through feeds (Atom and RSS) </li></ul><ul><li>Semantic Tags to allow smart markup to enable value add by portal, e.g. dynamic menus </li></ul><ul><li>Client Side C2A/Property Broker and Drag & Drop based on Semantic Tag s integrated with server side property broker and C2A support to enable cross-portlet interaction locally in the browser as well as with server side code </li></ul><ul><li>Sample AJAX Portlets with source showcasing the new capabilities to demonstrate and give samples to customers for how to exploit all the above </li></ul><ul><li>Integration, Aggregation and Customization of Google Gadgets </li></ul>
    18. 19. REST style Web Services exposing Portal to Mashups <ul><li>Goals: </li></ul><ul><ul><li>Separate portal user experience from portal data </li></ul></ul><ul><ul><li>Expose relevant data separately for use by other apps (  Mashups) </li></ul></ul><ul><li>Public REST style Web services for </li></ul><ul><ul><li>Access to Navigation Node Hierarchy </li></ul></ul><ul><ul><li>Access to Page Definitions </li></ul></ul><ul><ul><li>Access to User Profiles </li></ul></ul><ul><ul><li>Access to generic Content Persistence </li></ul></ul><ul><ul><li>Access to markup fragments of individual portlets </li></ul></ul><ul><li>Mashups can use these services to implement custom applications leveraging portal infrastructure services </li></ul><ul><li>WebSphere Portal’s Web 2.0 Client Side Aggregation uses these services as well </li></ul>
    19. 20. Emerging WPLC Services&Feeds and Application Examples WebSphere Portal Portal Services User Service Persistence Service Contacts Service Domino Mail Services Calendar Services Sametime Portlet Service Awareness Service Conference Service IM Service Quickr Documents Services Team Space Services Custom Situational Application: Problem tracking application allowing to see author presence and location in map and contact via IM Custom Situational Application: Simple AJAX Mail / Cal summary views with awareness Product: WebSphere Portal Client Side Aggregation Search Service Geneva Portlets, Notes Plugin, Sametime Plugin, Desktop Integration Product: Common PIM Portlets for Mail and Calendar Access Connections Persona, Community Services Activity, Blog Services Internet Services Maps …
    20. 21. Web 2.0 Fragment Model <ul><li>Simple and extensible Web 2.0 fragment programming model </li></ul><ul><li>Agnostic of how fragments are generated , may be </li></ul><ul><ul><li>generated by portlets on WebSphere Portal </li></ul></ul><ul><ul><li>generated by PHP code on Web.0 or PHP servers </li></ul></ul><ul><ul><li>generated by .NET servers </li></ul></ul><ul><li>Can start simple , with option to grow more sophisticated </li></ul><ul><ul><li>Basic fragments – HTML only </li></ul></ul><ul><ul><li>Slightly more advanced – add use of Semantic Tags </li></ul></ul><ul><ul><li>More advanced – add use of Dojo and custom JavaScript </li></ul></ul><ul><li>Fragments can use public JavaScript interfaces to conveniently invoke WebSphere Portal’s REST-style Web services </li></ul>
    21. 22. Web 2.0 Fragment Programming Model Web 2.0 Fragment Semantic Tags Dojo Widget Markup JavaScript Functions REST Calls to Portal Services User Profile Access Settings Access Persistence Service Access REST Calls to other Services, e.g. other WPLC services Weather Info, News, Sports, … CRM, HR, … Services etc
    22. 23. Application Architecture Pattern Browser Cache Browser Cache Proxy Cache Produced Services REST Service REST Service REST Service Data Store(s) DS 1 Consumed Services Public APIs (Local) ... Application Logic Service 2 Service 1 Service n ... DS 2 DS n ... AJAX Views AJAX Views AJAX Fragments (e.g. Portlets) AJAX Views AJAX Views Expeditor Plugins Web Browser AJAX Views Expeditor Expeditor Plugins Local App Code (if co-located) Application User Interface Application Services Project to Expeditor Project to Browser REST SyncML REST
    23. 24. Web 2.0 Client Side Aggregation <ul><li>Browser-side Aggregation, Navigation and Customization </li></ul><ul><li>Superior user experience </li></ul><ul><ul><li>Highly reactive and direct user interface </li></ul></ul><ul><ul><li>Many actions possible without server roundtrips </li></ul></ul><ul><ul><li>Avoids page flickering </li></ul></ul><ul><li>Accesses and manipulates portal information through REST services </li></ul><ul><li>Renders XML obtained from the server on the browser side </li></ul><ul><li>Implemented using AJAX, XML, Dojo, and JavaScript </li></ul><ul><li>Improved performance and scalability through </li></ul><ul><ul><li>Reduced server side processing - offloads rendering to browser </li></ul></ul><ul><ul><li>Reduced bandwidth requirements between server and browser </li></ul></ul><ul><ul><li>Reduced client-side processing – mostly fragment reloads, few page reloads </li></ul></ul><ul><ul><li>Improved cachability, all artifacts can be cached independently </li></ul></ul>
    24. 25. AJAX based Client Side Aggregation in the Web Browser Services created with Google Gadgets Atom / RSS Feeds REST-accessible Markup Fragments from WP Portlets or any other URL WSRP Services
    25. 26. Client Side Aggregation in Web Browser Portal Pages Portlet Settings Portal Navigation Tree based on Access Control and Personalization Navigation REST Service (Atom) Page REST Service Portlet Settings REST Service Portlet Access REST Service Theme Client Side Aggregation Enabled Theme User Profiles User Profiles REST /Web Service Portlets
    26. 27. Semantic Tags, Context Menus and Drag&Drop <ul><li>Conference Participants </li></ul><ul><li>... </li></ul><ul><li>IBM ST Thomas Schaeck ST 5 Technology Park Dr 555-5555 ST Westford, MA ST </li></ul><ul><li> Group ST Locations ST‘ </li></ul>Click to dial <ul><li>Extensible set of tag types such as person, address, phone number, document, ... is used to mark content elements with types (semantic tagging) </li></ul><ul><li>Behaviours like e.g. context menus, annotations, highlighting, drag & drop, etc can be applied to everything that is semantically tagged </li></ul>D&D D&D
    27. 28. Semantic Tags (Portal-Independent Technology)
    28. 29. AJAX based RSS/Atom Feed Consumption <ul><li>Allow simple consumption and display of Feeds in portal pages </li></ul><ul><ul><li>Atom feeds </li></ul></ul><ul><ul><li>RSS feeds </li></ul></ul><ul><li>Implemented using AJAX, Dojo and JavaScript </li></ul><ul><li>Gets settings defining the feed to display from portal </li></ul><ul><li>Retrieves feeds from origin servers via AJAX proxy </li></ul><ul><li>Renders feeds in the browser rather than causing server load </li></ul>
    29. 30. AJAX RSS/Atom Feed Consumption directly from Origin
    30. 31. Google Gadget Integration <ul><li>Enable customers to easily integrate Google Gadgets into portal pages </li></ul><ul><li> From an end user perspective, Google Gadgets integrated in WebSphere Portal behave just like local portlets: viewable and customizable like any local portlet </li></ul><ul><li>If allowed by admin, users can drag Generic Gadget Portlets on their pages and select Gadgets to display from the Gadget Catalog </li></ul><ul><ul><li>Gadget Portlet initially lets user select the Gadget to display from the Gadget Catalog </li></ul></ul><ul><ul><li>Gadget Portlet then displays the selected Gadget </li></ul></ul><ul><ul><li>User can view and customize the selected gadget like any local portlet </li></ul></ul><ul><li>Administrators can pre-define Gadget Portlets for the portlet palette </li></ul><ul><ul><li>Generic Gadget Portlet is pre-configured by the admin to connect it to a certain gadget, e.g. an admin could create a “Map Portlet” by creating a Gadget Portlet and connecting it to the Google Maps Gadget </li></ul></ul><ul><ul><li>Users can then select such pre-configured Gadget Portlets from the palette and drag them onto their pages like any local portlet </li></ul></ul>
    31. 32. Google Gadget Integration – A Gadget integrated in WebSphere Portal as a portlet
    32. 33. Google Gadget Integration – Selecting a Gadget to integrate into WebSphere Portal as a portlet
    33. 34. IBM Portlet for Google Gadgets Architecture IBM Portlet for Google Gadgets Google Gadget Google RSS Feed listing available gadgets View Mode Customize Mode Configuration Mode Customize Mode View Mode
    34. 35. AJAX Portlets using Dojo
    35. 36. Web 2.0 Portal Architecture WebSphere Portal Foundation AJAX Feed Consumer Connections (Activities, Blue Pages, Social Bookmarks, Blogs) AJAX Fragment Consumer AJAX Programming Model Extensions (Dojo Framework & Widgets + AJAX.0 + REST accessor JS functions + Semantic Tags + Client Side Click-2-Action) REST style Portal Services (Persistence, User Profiles, Portlet Settings, Navigation, Pages, etc) Quickr (Wikis, Blogs, Lists, Doc Libs, Discussions) Connections Portlets MyPlaces Portlet Feed Service HTML+Dojo+JS Fragments (from J2EE,.NET,PHP, HTTP or other Server) WebSphere Application Server Classic JSR 168 Portlets AJAX enabled JSR 168 Portlets WSRP Consumer WSRP Service
    36. 37. Conclusion <ul><li>Web 2.0 is important for the enterprise </li></ul><ul><li>AJAX and REST are important technologies related to Web 2.0 </li></ul><ul><li>IBM uses Web 2.0 concepts and technologies sucessfully in its intranet </li></ul><ul><li>WebSphere Portal already today in WP 6 provides Web 2.0 capabilities and leverages Web 2.0 technologies such as AJAX </li></ul><ul><li>Future releases of WebSphere Portal will add more Web 2.0 features and expand use of AJAX and REST </li></ul><ul><li>WebSphere Portal will integrate with Lotus Connections and Lotus Quickr </li></ul>

    ×