The Future of Web Services: Overview. Paul Cotton

Transcription

1 The Future of Web Services: Overview Paul Cotton

2 Introduction! XML Web Services: a flexible programming model for applications! The architecture is evolving " We began with the Baseline Specifications " Oct 2001 Microsoft provided four specs as part of the Global XML Web Services Architecture (GXA) " We will continue to add specifications to meet customer requirements! With key industry partners, we are building a rich architecture of public standards for distributed applications

3 The Story To Date! Commitment to standardization! Broad, deep, early product investment

4 Roadmap From July, 2000 Initially presented July 2000 at XML DevCon Submitted April 2001 to W3C with IBM popa/paper51 Reliability Attachments Messaging (SOAP) XML Security Routing Wire Process Orchestration (XLANG) Service Description (WSDL) XML Schemas Description Directory (UDDI) Inspection (Disco) Discovery

5 Global XML Web Services Architecture - GXA Transactions Reliable Messaging Referral Security Directory Routing License Inspection Description

6 Design Principles! Modular " Exploit SOAP extensibility model! General Purpose " Consistent model from address space to WAN! Federated " No globally central server or administration " Assumes applications span trust boundaries! Standards-Based " Build on current foundation: SOAP, WSDL, and UDDI " All new specifications on standards path

7 Modular Framework! AKA Why so many bubbles?! Bubbles complement each other! Re-use don t re-invent! No single spec is a complete solution! Construct rich messaging semantics by mixing and matching

8 Baseline Specifications! SOAP " Base encoding for messages! WSDL " Description of web services! UDDI " Directory for finding service descriptions

9 SOAP Drilldown! Based on semi-structured structured data " Support orthogonal extensions! Modularity through extensibility " Dynamic composition of data " Dynamic composition of processes! Simplicity and extensibility at the core " Rich functionality built on top! Status " SOAP 1.1 is W3C Note (May 2000) " SOAP 1.2 is Working Draft (contains updates and clarifications)

10 SOAP Example <s:envelope xmlns:s=" <s:header> <c:alertcontrol xmlns:c=" =" <c:priority>1</ >1</c:priority> <c:expires> t14:00:00-05:00</ 05:00</c:expires> </c:alertcontrol c:alertcontrol> </s:header s:header> <s:body> <m:alert xmlns:m=" =" /alert"> <m:msg>pick up Mary at school at 2pm</m:msg m:msg> </m:alert m:alert> </s:body s:body> </s:envelope s:envelope> =" envelope">

11 WSDL Drilldown! WSDL (Web Service Description Language) is a joint effort between MS and IBM " Combines best of NASSL and SDL " Currently in version 1.1 " Submitted jointly as W3C note in Mar Major pieces within a WSDL " Service " Binding " Operations " Messages " Types

12 UDDI Drilldown! UDDI is the Universal Description, Discovery and Integration specification " Managed by an industry-wide consortium; for details visit SOAP-based Web service for locating WSDL descriptions " Shares information about Web services across the enterprise and the Internet

13 Global XML Web Services Architecture - GXA Transactions Reliable Messaging Referral Security Directory Routing License Inspection Description

14 Extending The Semantics! Security: primary concern today " Support end-to to-end security including authentication, authorization, message integrity, and message encryption! Routing: scalability & fault tolerance " Dynamically configure message routing paths! Reliable Messaging: needed for mission critical apps " End-to to-end guarantee of message delivery with a range of semantics (at-least least-once, at-most most-once, once, and exactly-once)! Transactions: need to transact across companies! " Support variety of transaction and compensation semantics

15 Technical Preview Of GXA! Security " WS-Security Security " Credential exchange, message integrity, and message confidentiality " WS-License " Encoding for common license formats! Routing " WS-Routing " Route messages across intermediate SOAP nodes " WS-Referral " Partition URL namespaces between nodes!

16 Security! Core security extensions for SOAP " WS-Security Security and WS-License! Modular " Integrated with other SOAP bubbles " Framework for higher-level protocols " Not a complete solution! Enable secure web services to authenticate and authorize incoming requests " Support existing industry-standard standard identity and rights management systems " Work across trust domains

17 WS-Security Security Drilldown! Enable secure SOAP messaging " Passing Credentials " Message Integrity " Message Confidentiality! Modular extensions " Used independently or together " Standalone or with other SOAP extensions! Extensible!

18 WS-License Drilldown! Extension to WS-Security Security! Defines common license formats! Modular & extensible structures! Examples include : " X.509, Kerberos " SAML, XrML!

19 Example Credentials Integrity Confidentiality <?xml version= 1.0 encoding= utf-8?> <S:Envelope xmlns:s=... xmlns:xsd=... xmlns:xsi=...> <S:Header> <m:path xmlns:m= = > <m:action> us.org/getquote</ </wsrp:action> <m:to>soap://tickers-r-us.org/stocks</ us.org/stocks</wsrp:to> <m:from>mailto:johnsmith@isps mailto:johnsmith@isps-r-us.com</ </wsrp:from> <m:id>uuid:84b9f5d0-33fb-4a81-b02b-5b76064 </ 5b76064 </wsrp:id> </m:path m:path> <wssec:credentials > <wslic:binarylicense >MIIEBAgI MIIEBAgI...</...</wslic:binaryLicense> </wssec:credentials wssec:credentials> <wssec:integrity > <ds:signature > </ds:signature ds:signature> </wssec:integrity wssec:integrity> </S:Header S:Header> <S:Body> <enc:encrypteddata > </enc:encrypteddata enc:encrypteddata> </S:Body S:Body> </S:Envelope S:Envelope>

20 Routing! Core routing extensions to SOAP " WS-Routing and WS-Referral! Enable a virtual network " Architecture for creating fault-tolerant tolerant and load-balanced applications " Support proxies, data caches, and routing to the best replica (data center)

21 WS-Routing Drilldown! Our view on SOAP-based asynch messaging " Previously known as SOAP-RP " Builds on SOAP modularity! Provides transport and route flexibility " Supports message forwarding, resolution, and reverse path routing! Deliberately does not provide " Guaranteed Messaging, Caching, Pub/Sub, Notification, Privacy, Signing, Encryption, etc.!

22 WS-Routing Example Mom Send Message Through Relay Relay Dad

23 WS-Routing Example <S:Envelope xmlns:s=" =" <S:Header> <p:path xmlns:p=" =" /"> <p:action> > /alert</p:action> <p:to>soap:// >soap://foo.com/dad</ /dad</p:to> <p:fwd> <p:via>soap:// >soap://relay.com</ </p:via> </p:fwd p:fwd> <p:from>soap:// >soap://bar.com/mom</ /mom</p:from> <p:id>uuid:12dfs asd-s234-s3df-d25656adssf4</ d25656adssf4</p:id> </p:path p:path> <c:alertcontrol xmlns:c=" =" <c:priority>1</ >1</c:priority> <c:expires> t14:00:00-05:00</ 05:00</c:expires> </c:alertcontrol c:alertcontrol> </S:Header S:Header> <S:Body> <m:alert xmlns:m=" =" <m:msg>pick up Mary at school at 2pm</m:msg m:msg> </m:alert m:alert> </S:Body S:Body> </S:Envelope S:Envelope>

24 WS-Referral Drilldown! Our view on SOAP-based configuration of SOAP routers " Builds on SOAP modularity! Enables route configuration " Describe a referral " Query a SOAP router for a referral " Insert, delete, and exchange referrals! Deliberately does not provide " Guaranteed Messaging, Caching, Pub/Sub, Notification, Privacy, Signing, Encryption, etc.!

25 WS-Referral Example Mom Tell About Relay Relay Dad

26 WS WS-Referral Example Referral Example <r:ref r:ref xmlns:r xmlns:r=" =" <r:for r:for> <r:exact r:exact>soap:// >soap://foo.com foo.com/dad</ /dad</r:exact r:exact> </ </r:for r:for> <r:if r:if> <r:ttl r:ttl> </ > </r:ttl r:ttl> </ </r:if r:if> <r:go r:go> <r:via r:via>soap:// >soap://relay.com relay.com</ </r:via r:via> </ </r:go r:go> <r:refid r:refid>uuid: uuid: b 345b b623 b623-5dsf35sgs5d6 5dsf35sgs5d6</ </r:refid r:refid> </ </r:ref r:ref>

27 Putting It All Together SOAP Message Routing Security and License <?xml version="1.0" encoding="utf-8"?> <S:Envelope xmlns:s=" xmlns:xsd=" <?xml version="1.0" encoding="utf-8"?> xmlns:xsi=" <S:Envelope xmlns:s=" <S:Header> xmlns:xsd=" <m:path xmlns:xsi=" xmlns:m=" <m:action> <S:Header> <m:to>soap://tickers-r-us.org/stocks</m:to> <m:path xmlns:m=" <m:action> <m:to>soap://tickers-r-us.org/stocks</m:to> <m:id>uuid:84b9f5d0-33fb-4a81-b02b-5b760641c1d6</m:id> <!-- A Simple Quote Web Service --> </m:path> <m:id>uuid:84b9f5d0-33fb-4a81-b02b-5b760641c1d6</m:id> <wssec:credentials </m:path> xmlns:wssec=" <wssec:credentials <wslic:binarylicense xmlns:wssec=" <wslic:binarylicense xmlns:wslic=" wslic:valuetype="wslic:x509v3" xmlns:wslic=" xsi:type="xsd:base64binary"> wslic:valuetype="wslic:x509v3" dwjzy3jpymvylvblc..efw0wmtewmtawmd xsi:type="xsd:base64binary"> </wslic:binarylicense> dwjzy3jpymvylvblc..efw0wmtewmtawmd </wssec:credentials> </wslic:binarylicense> </S:Header> </wssec:credentials> <S:Body> </S:Header> <S:Body> <tru:stocksymbol <tru:stocksymbol xmlns:tru=" xmlns:tru=" QQQ QQQ </tru:stocksymbol> </S:Body> </S:Body> </S:Envelope>

28 Summary! SOAP-based XML Web services are a rich architecture for distributed applications! This architecture is " Modular " General-purpose " Federated " Standards-based! We have released Baseline Specs and a technical preview of several GXA Specs! Additional extensions are on the way! Deep native support in our tools and platform

29 Resources! Web Services XML information msdn.microsoft.com/xml/! W3C

30 2002 Microsoft Corporation. All rights reserved.