1 / 32

Wesley Budziwojski Senior Architect Sun ONE Portal Server

Web Services for Remote Portlets, WSRP. Wesley Budziwojski Senior Architect Sun ONE Portal Server. Jun/2003. Agenda. History & Currant Status Portal Server Architecture Sun ONE Portal Server Integration with EIS WSRP Architecture WSRP Interfaces WSRP & Portlets .

dixie
Download Presentation

Wesley Budziwojski Senior Architect Sun ONE Portal Server

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. Web Services for Remote Portlets, WSRP Wesley Budziwojski Senior Architect Sun ONE Portal Server Jun/2003

  2. Agenda • History & Currant Status • Portal Server Architecture • Sun ONE Portal Server • Integration with EIS • WSRP Architecture • WSRP Interfaces • WSRP & Portlets

  3. History and Current Status • Started in March/2002 • All key Portal vendors are involved • Just finished Public Review • Expected to be finalized by August

  4. Portal-Common Terminology User Agent Browser Phone, PDA Portlet Container Portlet Network Portal Portlet AggregationPersonalization Security Portlet

  5. Portal Integration EIS Portal Portlet Container SAP Portlet Vendor Specific User Agent (Browser) (PDA) (Phone) PSFT Portlet JDBC JDBC Portlet Network Network JCA Portlet Web Server XML Portlet XML WS Portlet SOAP URL Portlet Html

  6. WSRP Goal • Simplify Dynamic Integration of Remote Applications and Content to Portals

  7. What is WSRP? • Presentation Oriented Web Service • Interface and Protocol • Handles User Interaction • Provides Presentation Fragments tailored for aggregation

  8. WSRP Main Actors • WSRP Producer (portlet runtime) • Portlet • WSRP Consumer (Portal) • End-user

  9. High Level WSRP Actors’ Interactions • Finding Producer • Establishing Consumer-Producer Relationship • Establishing User-Consumer Relationship • Aggregating • Requesting Portal Page • Processing Interaction • Terminating CP Relationships

  10. WSRP Portal Architecture User Agent (Browser) Portal WSRP Consumer SOAP HTTP/S HTTP/S SOAP WSRP Producer Portlet Container Portlet Network Network Portlet Portlet

  11. Sun ONE Portal Architecture WSRP Consumer (remote Portal) HTTP/S SOAP WSRP Producer Portlet Container Portlet Portlet User Agent (Browser) Network HTML/WML VoiceXML Portal Portlet Network WSRP Producer (remote Portal) WSRP Consumer SOAP HTTP/S

  12. Sun ONE Portal Server • Upcoming support for WSRP • Comprehensive integration into the customer's infrastructure (Identity Management, Profile Management, Single Sing-On and Administration via Sun ONE Identity Server) • Developer tools for building Portlets (Portlet Builder plug-in for Forte For Java)

  13. Who will use WSRP? • Portal vendors (Producer & Consumer) • Content/Vertical vendors -Producer (Doc Management, ERP, CRM, etc) • Portlet developers *should never*

  14. WSRP Portlets Context Info • Interaction Parameters • Navigational State • Portlet Mode (VIEW, EDIT, HELP) • Window State (MIN, NORMAL, MAX) • Session • Properties • User Profile Attributes • User Categories

  15. WSRP Interfaces • Service Description (required) • Registration • Portlet Management • Markup (required)

  16. Service Description Interface • Indicates capabilities of the WSRP Producer • Indicates requirements WSRP Consumers must meet to interact with the WSRP Producer

  17. Service Description Info • It indicates if Consumer must register in order to use the Producer • Portlets the Producer offers • Properties Consumers must supply during registration • Extensions the Producer supports. Such as custom portlet modes, custom window states and custom user profile attributes • …

  18. Registration Interface • It allows Consumers to register, modify their registration and deregister from Producers • It allows Consumers to indicate their capabilities to Producers

  19. Registration Info • Consumer info (name, version) • Portlet Modes, Window States and user profile attributes the Consumer will support • Registration properties for the Consumer • Extensions the Consumer supports • …

  20. Portlet Management Interface • It allows Consumers to clone the Portlets offered by a Producer with their own properties • It allows Consumers to destroy cloned Portlets • It allows Consumers to access and modify properties of cloned Portlets

  21. Portlet Management Info • Portlet to operate on (PortletHandle) • Properties to modify • …

  22. Markup Interface • Consumers use this interface when handling requests for portal pages that include Portlets hosted by a Producer

  23. Two Types of Markup Calls • performBlockingInteraction • Invoked only when the User request to the Portal is an action targeted to the portlet • getMarkup • Invoked on every request to the portal, it produces output to create the portal page

  24. Portal & WSRP Requests Portal Portlet Container WSRP Consumer WSRP Producer Portlets A B C User Action on B A performBlockingInteraction(A) interaction B C getMarkup(A) markup getMarkup(B) markup getMarkup(C) markup A’ B’ C’

  25. performBlockingInteraction • It can modify Portlet Navigation State, Portlet properties, Portlet Mode and Window States • It can trigger a redirection • It can create a Session • It can do implicit Portlet cloning (I.e. because of a properties change)

  26. getMarkup • It returns Portlet content • It can create a Session

  27. Creating Portlet URLs • Producer rewriting (templates) • Consumer provides templates • Portlet generates URLs using the supplied templates http://foo.com/{wsrp-urlType}?mode={wsrp-mode}& • Consumer rewriting (tokens) • Producer writes info between tokens • Consumer scans Portlet generated content and rewrites tokens into URLs wsrp-rewrite?wsrp-urlType=###&wsrp-mode=###&name1=value1&.../wsrp-rewrite

  28. Caching • Producers may indicate to the Consumer to cache Portlet content • Types of cache: perUser & forAll • Expiration based cache with validateTag

  29. Portal Common Look & Feel • WSRP defines CSS style names • Links, Fonts, Messages (status, info, error, etc), Sections (header, footer, subheader, body, etc), Tables (header, body, alternate, etc), Forms (label, input, button, icon, etc.), Menus (menu, item, selected, hover, etc) • Portals (Consumer) provides the CSS definition with their style • The Portlets use the define CSS style names

  30. Some of WSRP Benefits • Flexible Architecture - decouples Portal aggregation from Portlet execution • Scalable - allows Portals to use/include Portlets running somewhere else • Plug and Play Solution -by standardizing on interface (WSDL)

  31. Important • Producer implementations SHOULD hide the complexity of WSRP from Portlets [Developers] • Programming a Portlet should be similar to programming a [I.e.] Java Servlet

  32. Thanks! Wesley.budziwojski@sun.com

More Related