Simple Object Access Protocol (SOAP)

MehulBoricha 769 views 19 slides Feb 17, 2019
Slide 1
Slide 1 of 19
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19

About This Presentation

It explains the basics of SOAP. This presentation covers the following topics:

+ Introduction
+ Design Goals
+ Architecture
+ SOAP Message Format
+ Messaging Models
+ Security & Issues
+ Advantages & Disadvantages
+ WSDL Overview
+ Conclusion


Slide Content

Simple Object Access Protocol (SOAP) Presented by Mehul Kumar

What we are going to Discuss? Introduction Design Goals Architecture SOAP Message Format Messaging Models Security & Issues Advantages & Disadvantages WSDL Overview Implementation Example

What is SOAP? Simple Object Access Protocol Messaging Protocol Protocol to Access Web Services Based on XML Developed by IBM, Microsoft, Lotus, and others

Example

Design Goals of SOAP Simplicity Extensibility Neutrality (Protocols) Independence (Programming Language)

In Brief SOAP is a way for a program running in one operating system to communicate with a program running in either the same or a different operating system, using HTTP (or any other transport protocol) and XML.

SOAP Architecture

SOAP Message Format Envelope - What is in the message & who should deal with it. Header (Optional) - Generic Container for Control Information. Can contain any number of elements. Body - Message Payload

Format - SOAP Envelope Code <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <!-- optional --> <!-- header blocks go here... --> </soap:Header> <soap:Body> <!-- payload or Fault element goes here... --> </soap:Body> </soap:Envelope>

Format - SOAP Header Code <soap:Header> <!-- security credentials --> <s:credentials xmlns:s="urn:examples-org:security"> <username>dave</username> <password>evad</password> </s:credentials> </soap:Header>

Format - SOAP Body Code <soap:Body> <x:TransferFunds xmlns:x="urn:examples-org:banking"> <from>22-342439</from> <to>98-283843</to> <amount>100.00</amount> </x:TransferFunds> </soap:Body>

SOAP Messaging Models Request/Response One Way Multicast

SOAP Security & Issues D oes not define encryption for XML Web Services. L eft up to the implementer . Issues Encryption places dependency on transport protocol Cost of Encryption

SOAP Advantages Simplicity Portability Firewall Friendly Use of Open Standards Interoperatibility

SOAP Disadvantages Too much reliance on HTTP Statelessness Serialized by Value and not by Reference

What is WSDL? Web Service Description Language Pronounced as 'wiz-dull' Provides Metadata for SOAP Service Follow Specific Structure

WSDL Structure <definitions> <types> ........ </types> <!--Type of Data--> <message> <part></part> </message> <!--Data Elements--> <portType> ....... </portType> <!--Operations--> <binding> .... </binding> <!--Protocol & Data Format for a Port--> <service> .... </service> <!--URI & Details--> </definitions>

Implementation of SOAP Let's see an example using PHP

Conclusion Fallen-out of Favor due to new public APIs Commonly used for B2B Applications Independent of Programming Languages XML Based