WSRP leveraging WSRF Use case for Portlets as

WSRP leveraging WSRF Use case for Portlets as WS-Resources July 28, 2004 WSRF Technical Committee F 2 F meeting 1

WSRP Motivation Enable the sharing of portlets (UI components => markup fragments) over the internet with a common interface => Cross vendor publishing and Visual Component Pool Internet consuming of content Client Browser Client Text processor Client Portal July 28, 2004 WSRF Technical Committee F 2 F meeting 2

Presentation vs. Data Oriented WS Data service Presentation Service 100 101 96 100 Presentation Layer 100 101 96 100 WS Presentation Layer WS Presentation WS => visual & user facing & WSRF Technical Committee F 2 F interactive July 28, 2004 meeting 3

Actors in a WSRP World Ü Portlet: A particular configuration of a component that renders its state in markup (for example, a component that renders markup for the projected weather for a particular postal code). Ü Producer: The service provider hosting the remote interactive Web service (for example, weather. com as a weather service provider). Ü Consumer: Integrates the remote service into its Web application, often times using a portal toolkit (for example, Yahoo or a corporate portal uses the weather portlet). Ü End User: The person that comes to the Consumer’s Web site to use the Producer’s components in the WSRF Technical Committee F 2 F Consumer’s context. July 28, 2004 meeting 4

WSRP Architecture End User Consumer http Producer Portlets SOAP Portlet this is a link WS-Client WSRP ports The Consumer is a Web Service client that communicates with the Producer via the four WSRP interfaces (ports) Required Interfaces Optional Interfaces Service Description Markup Registration Portlet Entity Management July 28, 2004 WSRF Technical Committee F 2 F meeting 5

General Interaction Flow End User view page Consumer Producer Portlets get. Markup (navigational state) Portlet this is a link markup fragment HTTP July 28, 2004 WSRP WSRF Technical Committee F 2 F meeting Private 6

General Interaction Flow - Render End User Consumer Interaction Producer Portlets get. Markup (navigational state‘) Portlet this is a link markup fragment for new nav state Click! HTTP WSRP Private The interaction only modifies navigational state Note: Consumer is allowed to invoke get. Markup on all Portlets in parallel. July 28, 2004 WSRF Technical Committee F 2 F meeting 7

General Interaction Flow - Interaction End User Consumer Producer Portlets perform. Blocking. Interaction() Interaction state change Portlet this is a link Portlet get. Markup() this is a link markup fragment for new state Click! HTTP WSRP Private The interaction may modify any type of state Note: Consumer is allowed to invoke get. Markup on all Portlets in parallel. July 28, 2004 WSRF Technical Committee F 2 F meeting 8

WSRP v 1 (August 2003) Ü Defined single API to UI components (indirect through their container) that is rapidly gaining traction in the marketplace. get. Markup() to render current state perform. Blocking. Interaction() to process user interactions Basic state management (registration, portlet, session, navigation and interaction) Ü Treats each portlet like an independent web app. Consumer can to aggregate these for presentation to the end-user. Ü Portlets treated indirectly (reference passed in most operations) as we hoped underlying work WSRF Technical Committee F 2 F interactingmeeting with stateful entities would July regarding 28, 2004 9

WSRP v 1 Ü Interop Demo – internet access available? BEA: http: //wsrp. avitek. com: 7001/consumer/portal IBM: http: //wsrp. dyndns. org: 9081/wps/portal Oracle: http: //portalstandards. oracle. com/portal/page? _pa geid=34, 38707&_dad=wsrp&_schema=WSRP Ü Other: Sun: http: //sunwsrp. dyndns. org/portal/dt Net. Unity: http: //www. netunitysoftware. com/e/e. dll? Function= Portal&Site=6 E 72 CD 92 D 1 E 48 F 45906 F 7 CEC 3 F 5 WSRF Technical Committee F 2 F CF 52 D July 28, 2004 meeting 10

WSRP v 2 target Ü Treat portlets as UI components that may be integrated (rather than just aggregated) into the Consumer’s web app. Supporting cross-portlet coordination Ü Increase leveraging of emerging WS specs. WSS: Many of our security scenarios relate to portlet-specific security issues WSN: Exploring how. Committee well F 2 F our coordination WSRF Technical July 28, 2004 meeting 11

WSRP v 2 issues Ü As WSRP becomes a more complete protocol for treating portlets as remote UI components, the fact that v 1 only addresses them indirectly becomes an issue. Ü Portlets are deployed components All use a common interface Are usually customized as they are added to a page. – e. g. my use of a weather portlet is customized to initially display weather WSRF Technical Committeefor F 2 F my home town. July 28, 2004 meeting 12

WSRP v 2 issues Ü Customized portlets are typically treated hierarchically: Existing portlet reference is passed to a Factory to generate a unique reference that may be independently customized Customization parameters not explicitly set are inherited from portlet used to generate the new reference. WSRP v 1 declined to require this in the remote case, but many vendors/customers desire the ability to be exposed. July 28, 2004 WSRF Technical Committee F 2 F meeting 13

Proposed leveraging of WSRF Ü Recast WSRP API to directly expose portlets. Ü Each deployed portlet accessed via an URL. Reference properties of the EPR provide applied customizations Ü Move current metadata to a required WSResource. Property (or two) to reduce WSRPspecific operations. Ü With portlet-specific WSDL, other specs can be leveraged without WSRP-specific issues: WSS WS-Policy WSN … July 28, 2004 WSRF Technical Committee F 2 F meeting 14

Proposed leveraging of WSRF Ü Customizations referenced via a set of customization records. <wsa: Endpoint. Reference> <wsa: Address> http: //Producer. com/Weather. Portlet </wsa: Address> <wsa: Reference. Properties> <wsrp: Customization. Record order=“ 0”>A</wsrp: Customization. Record > <wsrp: Customization. Record order=“ 1”>B</wsrp: Customization. Record > <wsrp: Customization. Record order=“ 2”>C</wsrp: Customization. Record > </wsa: Reference. Properties> </wsa: Endpoint. Reference> Ü WSRP Consumer can reason that customizations applied to a portlet with just the first two customization records Technical Committee F 2 F MAY impact this. WSRF portlet. July 28, 2004 meeting 15