1 / 14

SOAP Presentation

SOAP Presentation. By Raymond Tuong 12/02/2002. SOAP Overview. A SOAP Message is an envelope with two distinct parts Header Body <soap:Envelope> <soap:Header> </soap:Header> <soap:Body> </soap:Body> </soap:Envelope>. What is SOAP?. An XML-based messaging protocol.

kalona
Download Presentation

SOAP Presentation

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. SOAP Presentation By Raymond Tuong 12/02/2002

  2. SOAP Overview • A SOAP Message is an envelope with two distinct parts • Header • Body <soap:Envelope> <soap:Header> </soap:Header> <soap:Body> </soap:Body> </soap:Envelope>

  3. What is SOAP? • An XML-based messaging protocol. • SOAP defines a set of rules for structuring messages that can be used for simple one-way messaging • Particularly useful for performing RPC-style (Remote Procedure Call) request-response dialogues.

  4. Why is SOAP useful? • Not tied to any particular operating system or programming language. • Important building block for developing distributed applications that exploit functionality published as services over an intranet or the internet. (Ex. Web Services)

  5. SOAP Benefits • Standard communication format • Use existing infrastructure • Connecting diverse systems • New revenue streams

  6. SOAP Advantage/Disavantage • Pros • Works well with firewalls • Great for communicating between different platforms • Uses XML, therefore allows rich, extensible messages • Cons • Limited tools (for now…)

  7. SOAP message types • Request • Response • Fault

  8. SOAP message structure: Request • POST /StockQuote HTTP/1.1 Host: www.stockquoteserver.com Content-Type: text/xml Content-Length: nnnn SOAPAction: Some-Namespace-URI#GetLastTradePrice • <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> • <SOAP-ENV:Body> <m:GetLastTradePrice xmlns:m="Some-URI"> <symbol>DIS</symbol> </m:GetLastTradePrice> </SOAP-ENV:Body></SOAP-ENV:Envelope>

  9. SOAP message structure: Response • HTTP/1.1 200 OKContent-Type: text/xml; charset="utf-8“Content-Length: nnnn • <SOAP-ENV:Envelopexmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> • <SOAP-ENV:Body> <m:GetLastTradePriceResponse xmlns:m="Some-URI"> <Price>34.5</Price> </m:GetLastTradePriceResponse> </SOAP-ENV:Body></SOAP-ENV:Envelope>

  10. Transporting SOAP messages: protocol bindings • A SOAP envelope needs to be sent from one point to another. • Protocol designed must fit in the existing architecture. • Protocol binding: give information to an underlying protocol (HTTP, BEEP, ...) about what to do with a message.

  11. Security of the Web services architecture • SOAP extensions: digital signatures, encryption. • Overall security work.

  12. SOAP/HTTP and Security • HTTP Header Filtering • M-POST verb • HTTP • Basic • SSL • Header filtering (on SOAPAction) • Application Level Restriction • Only allow access to “Web Service” registered components

  13. SOAP Clients & Servers • In the world of web services, there are: • Web service providers (Servers) • Web service consumers (Clients) • Servers and clients communicate using SOAP

  14. Summary • SOAP = XML + HTTP (eventually other protocols) • Cross platform • Language independent • Works with firewalls

More Related