Introduction to Web Services

Praveen Singh Pokharia

What is a Web Service

A web service is a piece of business logic, located somewhere on the Internet, that is accessible through standard-based Internet protocols such as HTTP or SMTP. Using a web service could be as simple as logging into a site or as complex as facilitating a multi-organization business negotiation. Ex: Creating a Sales Order and initiating a workflow.

Ref: Java Web Services, Chappel et al, O'Reilly

Web Services: Alternate definition

A web service is just a web page meant for a computer to request and process. More precisely, a Web service is a Web page thats meant to be consumed by an autonomous program as opposed to a Web browser or similar UI tool.

Copyright 2005 John Cowan under GPL

Service Oriented Architecture

Requestor FIND, UDDI Registry

PUBLISH, UDDI

BIND, SOAP/WSDL

Providers

Components of SOA

Participants:
Provider Registry

(broker) Requestor

Interactions:
Publishing Direct HTTP GET request Dynamic discovery Service Binding

location (finding)

SOA: Publishing (dynamic)

Provider Registry

Here is my service !

SOA: Locating Service

Requestor Registry

Where is the service?

Find it here !

SOA: Binding
Registry

How can I access ?

Requestor

Here is how !
Provider

What is the temperature today?

40 C

Characteristics of a Web Service

XML-based Loosely coupled Ability to be synchronous or asynchronous Supports Remote Procedure Calls Supports document exchange

Major Technologies for WS

SOAP Simple Object Access Protocol WSDL Web Services Definition/Description Language UDDI Universal Description, Discovery, and Integration

Ref: Java Web Services, Chappel et al, O'Reilly

SOAP
SOAP stands for Simple Object Access Protocol. It is based on XML. It is a wired protocol and was defined to be highly interoperable. As of today there are extensive libraries support in virtually all languages to support SOAP based communication.

SOAP: Layers
SOAP-ENV:Envelope

SOAP-ENV:Header

SOAP-ENV:Body

SOAP: Example
POST /InStock HTTP/1.1 Host: www.example.org Content-Type: application/soap+xml; charset=utf-8 Content-Length: 299

<?xml version="1.0"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Header>

</soap:Header>
<soap:Body> <m:GetStockPrice xmlns:m="http://www.example.org/stock"> <m:StockName>IBM</m:StockName> </m:GetStockPrice> </soap:Body> </soap:Envelope>

Creating a SOAP message

<?xml version="1.0"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/0 5/soap-envelope"> <student> <roll>120</roll> <firstName>Kiran</firstName> <lastName>Reddy</lastName> <grades> <english>A</english> <maths>B</maths> </grades> </student> <soap:Header>

</soap:Header>
<soap:Body> <student> <roll>120</roll> <firstName>Kiran</firstName> <lastName>Reddy</lastName> <grades> <english>A</english> <maths>B</maths>

</grades>
</student> </soap:Body>

SOAP: Envelop

The SOAP envelope declaration is simply the outermost XML tag that delineates the boundaries of the SOAP document. The following envelope tag shows three required attributes, which specify the namespace and the schema to be used for this envelope:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> ... </SOAP-ENV:Envelope>

SOAP: Header & Body

The SOAP header and body are syntactically similar. It is simply a place to put directives to the SOAP processor that receives the message. The sending and receiving parties need to agree on which elements go there and what they mean.

SOAP: Fault

SOAP errors are handled using a specialized envelope known as a Fault Envelope. If an error occurs while the server processes a SOAP message, it constructs a SOAP Fault and sends it back to the client.

RESTful Architecture

HTTP: Introduction
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World-Wide Web global information initiative since 1990.

HTTP: How does it work?

The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, and possible body content over a connection with a server.

HTTP: How does it work?

The server responds with a status line, including the message's protocol version and a success or error code, followed by a MIME-like message containing server information, entity meta information, and possible entity-body content.

HTTP: Request/Response
Client Request GET /vnav/labs/PHP/HTTP.php HTTP/1.1 Host: loadaveragezero.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.14) Gecko/20110218 Firefox/3.6.14 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 ...

Server Response HTTP/1.1 200 OK

Server: Apache/1.3.41 (Unix)

Content-type: application/xhtml+xml; charset=UTF-8 ...

What is REST?

REST stands for Representational State Transfer. Its basically a stateless communication protocol relying on lightweight protocols like HTTP. It is basically an architectural design methodology.

REST: The other verbs

GET to retrieve information POST to add new information, showing its relation to old information PUT to update information DELETE to discard information

RESTful Application Cycle

Resources are identified by URIs Clients communicate with resources via requests using astandard set of methods Requests and responses contain resource representations informats identified by media types Responses contain URIs that link to further resources

REST: Give Everything an ID

ID is a URI http://example.com/widgets/foo http://example.com/customers/bar http://example.com/customers/bar/orders/2 http://example.com/orders/101230/customer

Thank You!

Q&A