Web Services Design Principles


Nov 3, 2013 (4 years and 7 months ago)


Web Services Design Principles

• Web
based Protocols

services based on HTTP

protocols can traverse firewalls, can work in a heterogeneous environment

• Interoperability

SOAP defines a common standard that allows different systems to interop

based (XML schema)

readable documents

• Modularity

Service Components are useful in themselves, reusable, composable

• Availability

Services are available to systems that wish to use them

Services must be exposed outside of the
particular system they are available in

• Machine
readable description

used to identify the interface, the location and access information

• Implementation

Service interface available independent of the ultimate implementation

• Published

archable service repositories of service descriptions

Web Services Architecture

The Web architecture consists of three components

• The
service providers
that publish available services and offer bindings for


• The
service brokers that allow service providers to publish their services

(register and categorize). They provide also mechanisms to locate services and

their providers

• The service requestor that uses the service broker to find a service and then

invokes (o
r binds) the service offered by a service provider.

For each of the three activities the Web services architecture provides specific

namely SOAP, WSDL, and UDDI. SOAP and WSDL are W3C

standards, whereas UDDI
is an OASIS standard.

oriented architecture

Service broker

Service requestor

Service provider




"naming service"






es a mechanism for clients to find web services

UDDI registry is similar to a CORBA trader or a DNS for business applications.

defines services as collections of network endpoints or

A port is defined by associating a network address with
a binding (servers)


collection of ports define a service

is a message layout specification that defines a uniform way of

passing XML
encoded data and to bind to HTTP as the underlying

communication protocol

SOAP is basically a technology to allow
for “RPC over the Web"

Basic Web Service Usage Scenario

This figure illustrates a (possible) basic Web service usage scenario. A Web
service provider registers it's web service at a UDDI repository. This could be done
manually through a Web interface or

through a UDDI API. He registers the description of
the web service which is given in WSDL. A potential user may, for example, manually
look up in the UDDI repository the Web service through http and obtain the WSDL file.
This file contains all the inform
ation needed in order to access the Web service. Based on
this information he/she implements a client application that makes use of the web service.
When the client application is executed it accesses the web service by using the SOAP
protocol for service

Web Services Implementation

Application Server (web service

provides implementation of services and exposes it through WSDL/SOAP

implementation in Java, as EJB, as .NET (C#) etc.

• SOAP server

implements the SOAP protocol

• HTTP server

standard Web server

• SOAP client

implements the SOAP protocol on the client site


Simple Object Access Protocol

• Lightweight messaging framework based on XML

• Supports simple messaging and RPC

• SOAP consists of

Envelope constr
uct: defines the overall structure of messages

Encoding rules: define the serialization of application data types

SOAP RPC: defines representation of remote procedure calls and responses

Binding framework: binding to protocols such as HTTP, SMTP

ult handling

• Soap supports advanced message processing:

forwarding intermediaries: route messages based on the semantics of message

active intermediaries: do additional process
ing before forwarding messages,

modify message


Web Service Des
cription Language

Description of Web services in XML format

abstract description of operations and their parameters (messages)

binding to a concrete network protocol (e.g. SOAP)

specification of endpoints for accessing the service

• Structure of a

WSDL document