July 28, 2004WSRF Technical Committee F2F meeting1 WSRP leveraging WSRF Use case for Portlets as WS-Resources

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

July 28, 2004WSRF Technical Committee F2F meeting3 Presentation WS => visual & user facing & interactive Presentation vs. Data Oriented WS Data service WS Presentation Layer Presentation Service WS Presentation Layer

July 28, 2004WSRF Technical Committee F2F meeting4 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 Consumer’s context.

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

July 28, 2004WSRF Technical Committee F2F meeting6 General Interaction Flow view page getMarkup (navigational state) ConsumerProducer markup fragment HTTP WSRP Portlet this is a link End UserPortlets Private

July 28, 2004WSRF Technical Committee F2F meeting7 General Interaction Flow - Render Interaction getMarkup (navigational state ‘ ) ConsumerProducer HTTP WSRP Portlet this is a link End UserPortlets Private markup fragment for new nav state Click! The interaction only modifies navigational state Note: Consumer is allowed to invoke getMarkup on all Portlets in parallel.

July 28, 2004WSRF Technical Committee F2F meeting8 General Interaction Flow - Interaction Interaction getMarkup() ConsumerProducer HTTP WSRP Portlet this is a link End UserPortlets Private markup fragment for new state Click! The interaction may modify any type of state Note: Consumer is allowed to invoke getMarkup on all Portlets in parallel. performBlockingInteraction() state change

July 28, 2004WSRF Technical Committee F2F meeting9 WSRP v1 (August 2003)  Defined single API to UI components (indirect through their container) that is rapidly gaining traction in the marketplace. getMarkup() to render current state performBlockingInteraction() 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 regarding interacting with stateful entities would become useful.

July 28, 2004WSRF Technical Committee F2F meeting10 WSRP v1  Interop Demo – internet access available? BEA: IBM: Oracle: 707&_dad=wsrp&_schema=WSRP 707&_dad=wsrp&_schema=WSRP  Other: Sun: NetUnity: e=6E72CD92D1E48F45906F7CEC3F5CF52D e=6E72CD92D1E48F45906F7CEC3F5CF52D

July 28, 2004WSRF Technical Committee F2F meeting11 WSRP v2 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 well our coordination semantics map onto the WSN specs.

July 28, 2004WSRF Technical Committee F2F meeting12 WSRP v2 issues  As WSRP becomes a more complete protocol for treating portlets as remote UI components, the fact that v1 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 for my home town.

July 28, 2004WSRF Technical Committee F2F meeting13 WSRP v2 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 v1 declined to require this in the remote case, but many vendors/customers desire the ability to be exposed.

July 28, 2004WSRF Technical Committee F2F meeting14 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 WS-ResourceProperty (or two) to reduce WSRP-specific operations.  With portlet-specific WSDL, other specs can be leveraged without WSRP-specific issues: WSS WS-Policy WSN …

July 28, 2004WSRF Technical Committee F2F meeting15 Proposed leveraging of WSRF  Customizations referenced via a set of customization records. A B C  WSRP Consumer can reason that customizations applied to a portlet with just the first two customization records MAY impact this portlet. Example: Page designer changing overall layout of a site … which portlets should the customizations be applied to. Certainly do not want to have to independently update all user-customized portlets!