Scribd
Upload
18 views

5 xml-SOAP

SOAP is a protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. It allows applications to communicate over the internet in a decentralized, distributed environment. SOAP defines rules for encoding an HTTP header and XML markup to define the content of a message and how to process it, enabling cross-platform remote procedure calls and invocation of services. Key benefits are that SOAP uses XML for its message format, making it extensible and platform-independent for integrating web services across different operating systems, programming languages, and frameworks.

Uploaded by

Sayali Mahajan
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
18 views

5 xml-SOAP

SOAP is a protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. It allows applications to communicate over the internet in a decentralized, distributed environment. SOAP defines rules for encoding an HTTP header and XML markup to define the content of a message and how to process it, enabling cross-platform remote procedure calls and invocation of services. Key benefits are that SOAP uses XML for its message format, making it extensible and platform-independent for integrating web services across different operating systems, programming languages, and frameworks.

Uploaded by

Sayali Mahajan
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

SOAP

A.A.Deshmukh
SKNCOE,COMP

Outline

The problem.. Why XML? Why HTTP? XML+HTTP = SOAP SOAP Details Uses of SOAP Example

The problem..

Client App.

Proxy Server

Server
Application Server

Firewall

Implications

Industry not shifted completely to either one Vendor specific

Lack of interoperability
Require high-tech runtime environment

Why XML?

Simple text markup language

Platform, language and vendor agnostic Easily extensible


Capable of solving interoperability problem

Why HTTP?

Ubiquitous

Supported by every web browser and server


Effective technology for transferring text, graphics and other information

XML + HTTP = SOAP

HTTP is used for transport

XML as encoding scheme


Endpoint HTTP based URL for the target Object mapping: implementation specific

SOAP call anatomy

SOAP Component
HTTP Headers SOAP method name

Object Endpoint ID Method/Interface ID

SOAP Envelope SOAP Header SOAP Body Call element

Extension Headers

Parameter Data

Uses of SOAP

SOAP greatly simplifies data exchange in B2B application over extranet Enables web site to integrate services from other sites Remote scripting more prevalent with SOAP Non-browser client could seamlessly access a service across web

Example Message
POST /string_server/Object17 HTTP/1.1 Host: 209.110.197.2 Content-Type: text/xml Content-Length: 152 SOAPMethodName: urn:strings-com:IString#reverse <Envelope> <Body> <m:reverse xmlns:m='urn:strings-com:IString'> <theString>Hello, World</theString> </m:reverse> </Body> </Envelope>

Example Response
200 OK Content-Type: text/xml Content-Length: 162 <Envelope> <Body> <m:reverseResponse xmlns:m='urn:stringscom:IString'> <result>dlroW ,olleH</result> </m:reverseResponse> </Body> </Envelope>

Conclusion

SOAP is platform independent, language neutral protocol SOAP does not replace COM and CORBA SOAP works in place of DCOM and IIOP SOAP does not pose huge security risks Supports interoperation between different vendor specific implementations

You might also like