Simple Object Access Protocol

(SOAP)
Reporter:
BSIT IV-D GROUP IV

Parrenas, Jay Anthony Lopez, Mariel

Parada, Rolly C Lontes, Jessebell
Santianes, Djonel Sancio, Rasel
 SOAP and Web Services
Simple Object Access Protocol (SOAP), Web Services
Description Language (WSDL), and Universal
Description, Discovery and Integration (UDDI) are
emerging as the de facto standards for Web
services. A Web Service can be consumed by any
client irrespective of the platform that the client is
using. This is because Web Services are based on the
HTTP protocol. The .NET Framework encapsulates
the support for SOAP internally.
Simple Object Access Protocol)
is a protocol specification for exchanging
structured information in the
implementation of web
services in computer networks. Its purpose
is to induce extensibility, neutrality and
independence.
Simple Object Oriented Protocol (SOAP) is
an Open Standard protocol.
 What is SOAP?
SOAP - Simple Object Access Protocol
It is an XML-based messaging protocol for
exchanging information among computers.
Is an application of the XML specification.
SOAP is platform independent, language
independent and messaging between
applications makes this protocol a robust and
standardized mechanism in order to handle
message communication across homogenous
or heterogeneous networks.
 All SOAP messages are transmitted in XML
format.
XML, a platform independent Meta (Language
composed of non-binary ASCII text), has
revolutionized the way data is transferred
between systems. XML is fast becoming as
ubiquitous as HTTP. It has now already
become an accepted standard for
representation and interchange of data in
structured form across systems. All SOAP
messages are transmitted as XML.
 Nature of SOAP
SOAP is a communication protocol
designed to communicate via internet
SOAP can extend HTTP for XML
messaging
SOAP provides data transport for Web
Services
SOAP can exchange complete documents
or call a remote procedure
 SOAP can be used for broadcasting a
message
SOAP is platform- and language-
independent
SOAP is the XML way of defining what
information is sent and how
SOAP enables client applications to easily
connect to remote services and invoke
remote methods
As per the SOAP specification, SOAP is typically
composed of the following three parts:
A framework that describes how the message
can be constructed and how it can be
processed
A set of encoding rules for exchanging the
data types
A convention and a procedure for
representing the Remote Procedure Calls
 Simple Object Access Protocol
Messages
Elements: A SOAP message format:
Envelope <SOAP: Envelope>
Header <SOAP: Header>
</SOAP: Header>
Body <SOAP: Body>
</SOAP: Body>
</SOAP: Envelope>
 SOAP MESSAGES
Envelope - Defines the start and end of the message.
(mandatory element)
Header -Contains any optional attributes of the
message used in processing the message, either at
an intermediary point or at the ultimate end-
point. (Optional element)
Body -Contains the XML data comprising the
message being sent. (mandatory element)
Fault an Optional fault element that provides
information about errors that occur while
processing the message.
Simple Object Access Protocol
Process Model
(SOAP)
 SOAP provides the envelope for sending Web
Services messages over the
Internet/Internet. It is part of the set of
standards specified by the W3C. SOAP is an
alternative to Representational State Transfer
(REST) and JavaScript Object Notation
(JSON)
The most common messaging pattern used in
SOAP is Remote Procedure Call or RPC.
 The SOAP envelope contains two parts:
An optional header providing information on
authentication, encoding of data, or how a
recipient of a SOAP message should process
the message.
The body that contains the message. These
messages can be defined using the WSDL
specification.
 SOAP commonly uses HTTP, but other
protocols such as Simple Mail Transfer
Protocol (SMTP) may by used. SOAP can be
used to exchange complete documents or to
call a remote procedure.

NOTE: SOAP at one time stood for Simple

Object Access Protocol. Starting with SOAP
Version 1.2, the letters in the acronym have no
particular meaning.
The following figure illustrates using SOAP
for Web Services.
 A client sends a SOAP message to the
server. This requesting data is also called a
SOAP Request. The server receives the
request, processes the same and sends a
response back to the client. This returning
data is known as the SOAP Response. This
communication back and forth between the
client and the server takes place through
HTTP protocol.
The Advantage and Disadvantage
of (SOAP)
Simple Object Access Protocol
Advantages of SOAP Web Services
WS Security: SOAP defines its own security
known as WS Security.
Language and Platform independent: SOAP
web services can be written in any
programming language and executed in any
platform.
 Simplicity -- The SOAP messages are in
simple, human readable XML format.
Scalability -- This is because it uses HTTP
protocol for transport.
Language neutrality -- Can be developed
using any language.
Interoperability and Platform Independence--
SOAP can be implemented in any language and
can be executed in any platform.
Disadvantages of SOAP Web Services
Slow: SOAP uses XML format that must be
parsed to be read. It defines many standards
that must be followed while developing the
SOAP applications. So it is slow and
consumes more bandwidth and resource
WSDL dependent: SOAP uses WSDL and
doesnt have any other mechanism to
discover the service
Conclusion
It should be noted that SOAP does not
address object activation, marshaling
objects/references, garbage collection,
etc. Further, as SOAP is a wire protocol, it
does not provide an activation
mechanism. However, we can still use these
in our applications as a layer on top of
SOAP if required.
 1. Simple Object Access Protocol
2. SOAP
3. True
4. False
5. Body
6. Envelope
7.False
8.True
9. Simplicity
10.Language Neutrality
 Thank You
for Listening
References:
http://www.tutorialpoint.com/soap/what_is_soap.htm
http://www.javatpoint.com/soap-web-services