09/04/2021

Sistemas de Informação
Web Services

1 Objectivos

´ Analisar os conceitos básicos de web services

´ Descrever as components dos web services

´ Entender os standards dos web services

´ Elucidar exemplos dos web services

´ Analisar as vantagens e desvantagens dos web services

1
 09/04/2021

2 Web Services are NOT …

´“…the latest revolutionary technology which will

enable seamless interoperability and solve all
integration problems across the entire World
Wide Web because all major software vendors
are going to support Web services related
standards with a new wave of powerful loosely
coupled tools.”

3 Defining Web Services

´ At one extreme, a Web service is any application program which is
accessible through the World Wide Web.

´ W3C defines Web services as: a software application identified by a

URI, whose interfaces and bindings are capable of being defined,
described and discovered as XML artifacts.

´ A Web service supports direct interactions with other software agents

using XML-based messages exchanged via the internet.

´ The long-term goal is just-in-time integration of applications by

discovering and orchestrating Web services available on the
network

2
 09/04/2021

4 Web Services Architecture (IBM)

5 Definitions
Web Services
´ Software systems designed to support interoperable
machine-to-machine interaction over a network.(W3C)
´ Messages in-between are XML-based

Web Service Description Language (WSDL)

´ A XML-based markup language for specifying interfaces
for consuming services over the network.

3
 09/04/2021

6 Definitions
UDDI
´ Universal Description, Discovery and Integration
´ A platform-independent XML-based registry for businesses
worldwide to list themselves on the Internet.

SOAP
´ Simply Object Access Protocol
´ A protocol for exchanging XML-based messages over
computer networks by HTTP/HTTPS.

7 Web Services

4
 09/04/2021

8 Web services roles

Service provider
´ Implements the services
´ Makes the services available on the web

Service requestor
´ Consumes the web services

Service registry
´ Logically centralized registry provides a central place where
allows developers to publishnew services or search (or
discover)existing ones

9 Web services orchestration

1. Web services providers register in UDDI Registry.

2. Web service consumers discover the desired web services in

UDDI server.

3. Consumers retrieve the WSDL documents from desired web

service providers.

4. Consumers send SOAP request messages to service providers.

5. Providers receive the requests, process them request, and return

SOAP responses.

5
 09/04/2021

10

10

11

11

6
 09/04/2021

12 Web services
Service offered trough a website

12

13 Web + Web services

13

7
 09/04/2021

14 Web services components

´ Component Based Software Engineering (CBSE) defines

system architectures in terms of the dependencies
connecting a set of reusable components

´ Service Oriented Architectures (SOA) define the

architecture of a distributed system in terms of the
interactions among its component services

14

15 Components
´ Software components are reusable.

´ To be used a component must:

´be packaged to be deployed as part of some larger

application system,

´fit with the existing framework used to develop the system.

´ Components can be sold, usually on a per-deployment basis.

´ There are many component frameworks available for building

distributed systems (e.g., J2EE, DCOM, .NET, CORBA).

´ But they are not compatible…

15

8
 09/04/2021

16 Web Services
´ Web services are reusable too.
´ To be used a service must:
´ be published on the Web (once)
´ advertise its description and location to potential clients across
the Web so that they can access it using standard protocols.
´ Web Services can be sold too: service providers can charge on a
per-call basis.
´ Like components, web services can be reused, composed into
larger systems and (of course) they can be found on the Web.
´ Unlike components, Web services do not have to be downloaded
and deployed in order to be used by clients.
´ Instead, a client may discover and access their functionality by
using standard protocols (SOAP, HTTP)

16

17 Component Interoperability
´ Due to lack of interoperability, it is not always possible to build
a distributed system using heterogeneous components.

17

9
 09/04/2021

18 Web service interoperability

´ If the components are published as Web services, they can
interoperate across different component frameworks
(interoperability through wrapping).

18

19 API
´ An application programming interface(API) is a set of
routines, protocols, and tools for building software and
applications

´ A web API is an API for a webserver

´ Web APIs can be either SOAP or REST services

´ http://www.programmableweb.com/category/all/apis

19

10
 09/04/2021

20 API Examples
´ Twitter (http://www.tweetbeam.com)

´ Google Maps Geocoding (example)

´ CTT Postal Code Validation (example)

´ Twilio SMS (example)

20

21

´ Web services provide standards for developing large

scale distributed systems.

´ “The grid” and “the cloud” are examples of adopting

Web services as standard protocols to build a large
distributed infrastructure for utility based computing.

21

11
 09/04/2021

22 Standards and Layers

´ Distributed systems are built using standardized layers of
increasingly higher abstraction levels.
´ It took 20 years to go from the TCP/IP (Internet, 1973) standard
to the HTTP/HTML (World Wide Web, 1992) standards.
´ By reusing HTTP, the time to standardize SOAP/XML was halved
(Web Services, 2000).

22

23 Properties of Web Services

´ A Web Service must be defined, described and discovered to
be accessed by clients.
´ XML is the foundation for all standards that are going to be
used (SOAP, WSDL, UDDI) to do so.
´ Web services are intended to be used as components that
can be readily integrated into more complex distributed
applications.
´ Web services are meant for software based consumption
(clients are programs).
´ Web-based applications are meant to be used by humans
equipped with a www browser (clients are users).

23

12
 09/04/2021

24 Benefits of Web Services

´ The main difference regarding conventional middleware is
related to the standardization efforts at the W3C.

´ Platform independence (Hardware, Operating System).

´ Reuse of existing networking infrastructure (HTTP has

become ubiquitous).

´ Programming language neutrality (e.g. .NET talks with

Java, and vice versa).

´ Portability across middleware tools of different vendors.

´ Web services are loosely coupled, reusable and can be

adopted incrementally.

24

25 Problems of Web Services

´ What is the price to pay for interoperability?
´ Currently web services standards are still rapidly evolving and
only the core is stable.
´ A good and a bad thing about standards is that there are so
many to choose from: many WS-* standards are competing
and overlapping.
´ Not all standards are supported by tools. Tools must play
catch-up with new standard versions.
´ The performance of some of the available tools and protocols
is quite poor.

25

13
 09/04/2021

26 The (partial) Web services stack

26

27

´Dúvidas!!!

27

14