W eb Services for Remote Portlets (WSRP) Overview

1. Web Services for Remote Portlets (WSRP) Overview OASIS WSRP Technical Commitee September, 2003 OASIS WSRP Technical Commitee

2. Overview • Web Services for Remote Portlets (WSRP) has defineda standard for interactive, presentation-oriented web services. • WSRP defines: • A WSDL interface description for invocation of WSRP services • Semantics for interacting with WSRP services that can not be expressed in WSDL. • Markup fragment rules for markup emitted by WSRP services • Companies involved with WSRP: • BEA, Bowstreet, Citrix, Commerce One, Computer Associates, CrossWeave, Divine, Drake Certivo, Factiva, France Telecom, Fujitsu, Gluecode, HP, IBM, Interwoven, Kinzan, Lexis-Nexis, Lotus, MacDonald Bradley, Microsoft, Moravia IT, Netegrity, Novell, Oracle, Peoplesoft, Perficient, Plumtree, Reed Elsevier, SAP, SeeBeyond, Silverstream, Stellent, Sun Microsystems, Sybase, Tibco , Vignette, WebCollage OASIS WSRP Technical Commitee

3. WSRP Services Plug&Play with Portals Registry Find Publish Portals Portals Clients Portals Clients WSRP Services Portals Portals WSRP Services Portals Portals WSRP Services Web Clients Web Clients Web Clients Web Clients Portals Web Clients Portals Web Clients Bind Portals Web Clients Portals Web Clients Portals Web Clients Web Clients e.g. OASIS WSRP Technical Commitee

4. WSRP Goals • Enable interactive, presentation-oriented web services to be easily plugged into standards-compliant portals • Ensure concepts and data exchanged are aligned with other standards in both the portal and web service arenas. • Make the Internet a marketplace of visual web services, ready to be integrated into portals OASIS WSRP Technical Commitee

5. Scenario: Use of WSRP in Portals WSRP Consumer WSRP Producer • Portals can aggregate presentation from many WSRP services • WSRP services can be aware of portal context • User profile from portal • Desired locale and markup-type • Active user agent WSRP Service Portal WSRP Service WSRP Service Aggregated HTML, WML, VoiceXML, ... over HTTP Mark-Up Fragments Transferred via SOAP OASIS WSRP Technical Commitee

6. Scenario: Portal sharing Portlets WSRP Consumer WSRP Producer • Users of the second portal (WSRP Consumer) can select remote portlets like any local portlet and put them on their pages • In this case, the portal providing a portlet as a WSRP service adheres to the WSRP protocol and contracts just like any other WSRP Producer service Portals Server Portal Portlet Portals WSRP Interface Portals Portal Portlet Portlet Huge number of users Portals as Intermediaries, Caching offloads requests from WSRP Producer Publishing Portal OASIS WSRP Technical Commitee

7. Scenario: Use of WSRP in Client Apps WSRP Consumer WSRP Producer • Applications may embed WSRP Services through plugin mechanisms, e.g. COM Components or ActiveX Controls • In this case, the plugin in the client application adheres to the WSRP protocol and contracts as a WSRP Consumer WSRP Service Application (e.g. Word, Outlook, ...) WSRP Service WSRP Service User Info, Actions, Markup Fragments Transferred via SOAP Rendering within client application‘s view OASIS WSRP Technical Commitee

8. Abstract Portal  WSRP Interaction User WSRP Producer (Service) WSRP Consumer (Portal) Adds Portlet Clone Portlet I I Allocate new clone View Portlet Get Portlet Markup A I S I I Generate Markup, (opt: create Session) S A Click Action Perform Portlet Action I S A I S A I A Action Handling (opt: create Session) Removes Portlet Destroy Portlet clone I I I Destroy clone OASIS WSRP Technical Commitee

9. WSRPand related Standards (X)HTML WML Voice XML cHTML ... WSRP UDDI (Publish,Find&Bind) WSDL (Description) SOAP (Invocation) OASIS WSRP Technical Commitee

10. WSRP and Portlet API(s) Web Services for Remote Portals (WSRP) Platform Independent Web Service Interface Platform specific, local Portlet APIs C# “Portlet API“ (.NET) WSRP Impl. on plain J2EE or .NET platform Java Portlet API (JSR 168) . . . Portlet APIs may be defined for different programming languages; WSRP can bridge between the different platforms, leveraging platform independence of Web services Goal: Portlets written to Portlet API(s) can be published as WSRP services OASIS WSRP Technical Commitee

11. WSRP TC Areas of Work • Business Scenarios • WSRP Interfaces & Protocol • WSRP Markup Fragments Rules/Styles • WSRP and Security, Identity, SSO ... • WSRP Interoperability • WSRP Conformance • WSRP Publish, Find, Bind & Metadata (not in v1.0) • WSRP Coordination (not in v1.0) OASIS WSRP Technical Commitee

12. Business Scenarios • Content/Application Provider providing WSRP Service • Portal publishing Portlets as WSRP Services • Syndicated Content / Billing via WSRP • Enterprise Application • Current Awareness • Cooperating WSRP Services • Multimedia Sports Portal / Mobility OASIS WSRP Technical Commitee

13. WSRP Interfaces & Protocol • Define the operations for WSRP services • Life-cycle operations, e.g. clone a portlet for customization • Advanced operations for processing actions/getting markup • User profile information contained in requests • User agent information contained in requests • Locale information contained in requests • Protocol defining interaction between consumer and service • Allowed order of operation invocation • Caching considerations OASIS WSRP Technical Commitee

14. WSRP Markup Fragments Rules/Styles • Define valid markup fragments for • HTML / XHTML (in v1.0) • WML, cHTML, VoiceXML (targetted for v1.1) • Define URL rewriting • Define namespacing/prefixing OASIS WSRP Technical Commitee

15. WSRP and Security, Identity, SSO ... • Define how security mechanisms and protocols can be employed with WSRP • Define how Identity is to be provided by Consumers to Producers OASIS WSRP Technical Commitee

16. WSRP Interoperability • Provide forum for discussion of issues encountered when vendors test interoperability of their implementations. • Provide feedback to the WSRP Technical Committee of issues encountered and clarifications that would be useful to the specification. OASIS WSRP Technical Commitee

17. WSRP Conformance • Define Use Profiles for implementing various sets of optional features. Use marketplace realities to drive number and type of use profiles. • Define the set of test cases required by the conformance language of the specification or the functionality of the use profiles. • Define test suites for conforming to the specification and the use profiles. OASIS WSRP Technical Commitee

18. WSRP Publish, Find, Bind & Metadata • Define method used to publish services to directories • Metadata to be provided when publishing service • Name, Titles, Descriptions • Supported Markups / Locales • Hints for caching • ... • Provide concrete mappings for various publishing mechanisms: • UDDI – in progress • ebXML Registry/Repository – if there is sufficient interest • WSIL – if there is sufficient interest OASIS WSRP Technical Commitee

19. Planned WSRP Milestones • September 2003: WSRP Specification 1.0 approved as an OASIS standard • December 2003: Determine content of WSRP v1.1 • May 2004: WSRP Specification 1.1 approved as an OASIS standard • September 2004: Determine content of WSRP v2.0 OASIS WSRP Technical Commitee