Web services use SOAP, WSDL, and UDDI to enable communication between systems. SOAP defines an XML format for messages, WSDL describes available services and operations, and UDDI provides a directory for services to publish themselves. Services communicate by exchanging SOAP messages, with requests and responses defining common operations, and faults handling errors.
2. • SOAP (Simple Object Access Protocol) is a simple
protocol for exchange of information.
• UDDI (Universal Description, Discovery, and
Integration) is a specification designed to allow
businesses of all sizes to benefit in the new digital
economy.
• WSDL (Web Services Description Language) defines
the XML grammar for describing services as
collections of communication endpoints capable of
exchanging messages.
simplesourcecodes@live.com
4. Introduction
• A Web service is a method of communication between
two electronic devices over the web (internet).
• It has an interface described in a machine-processable
format (WSDL)
• Other systems interact with the Web service using SOAP
messages
Features of Web Services
• Language Independent
• Operating System Independent
4
5. WSDL
• WSDL is written in XML
• used to describe & locate Web services
WSDL Ports
• The <portType> element is the most
important WSDL element.
• It defines a web service, the operations that
can be performed, and the messages that are
involved.
simplesourcecodes@live.com
7. Operation Types
The request-response type is the most common operation type, but
WSDL defines four types:
Type Definition
One-way The operation can receive a message but
will not return a response
Request-response The operation can receive a request and will
return a response
Solicit-response The operation can send a request and will
wait for a response
Notification The operation can send a message but will
not wait for a response
simplesourcecodes@live.com
8. UDDI
• Universal Description, Discovery and Integration
(UDDI)
• UDDI is a directory for storing information about web
services
• UDDI is a directory of web service interfaces
described by WSDL
• UDDI communicates via SOAP
• UDDI uses WSDL to describe interfaces to web
services
simplesourcecodes@live.com
9. SOAP-based communication
Waiting for
Waiting for Sending
Sending
requests
requests Data in XML format requests,
requests,
(known location,
(known location,
known port)
getting
getting
known port)
results
results
• SOAP:
– Data in a well-defined XML format
– Transport over various protocols
• HTTP, SMTP are the most used, perhaps because
they are firewall-friendly
– server side: either an RPC call or a message delivered
10. SOAP Elements
• Envelope (mandatory)
– Top element of the XML document representing the
message.
• Header (optional)
– Determines how a recipient of a SOAP message should
process the message
– Adds features to the SOAP message such as
authentication, transaction management, payment,
message routes, etc…
• Body (mandatory)
– Exchanges information intended for the recipient of the
message.
– Typical use is for RPC calls and error reporting.
13. SOAP Fault
• Used to carry error and/or status information within
a SOAP message
• Appears within the SOAP body
• Defines the following:
– faultcode (mandatory)
• algorithmic mechanism for identifying the fault
• defined in the SOAP spec
– Faultstring (mandatory)
• human readable explanation of the fault
14. SOAP Fault
– faultactor (optional)
• information about who caused the fault to happen
• URI value identifying the source
– Detail
• error information related only to the Body element.
• if not present then indicates that the fault is not
related to the Body element.