Scribd
Upload
31 views17 pages

Week 10-11 SOAP PDF

This document discusses inter-system communication through web services and middleware. It proposes that Hewlett-Packard first introduced the concept of web services through e-Speak in 1999, while Microsoft popularized the term in 2000 and made web services a key strategy. The document then outlines the open standards of XML, SOAP, WSDL, and UDDI that enable web services and interoperability. It provides examples of real-world web services implementations and describes technologies like SOAP and WSDL that are used to define and access web services.

Uploaded by

Lavina Xielle Constancia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
31 views17 pages

Week 10-11 SOAP PDF

This document discusses inter-system communication through web services and middleware. It proposes that Hewlett-Packard first introduced the concept of web services through e-Speak in 1999, while Microsoft popularized the term in 2000 and made web services a key strategy. The document then outlines the open standards of XML, SOAP, WSDL, and UDDI that enable web services and interoperability. It provides examples of real-world web services implementations and describes technologies like SOAP and WSDL that are used to define and access web services.

Uploaded by

Lavina Xielle Constancia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Week 10&11

Inter-systems Communications
Web Service and Middleware (SOAP)
Who Was First?

What company first proposed the web services concept?


• Hewlett-Packard's e-Speak in 1999
• was an enabler for e-services
• Microsoft introduced the name "web services" in June 2000
• MS "bet the company" on its web services strategy
• now every major vendor is a player

Open, Standard Technologies


– XML – tagging data such that it can be exchanged between applications and platforms
– SOAP – messaging protocol for transporting information and instructions between applications (uses
XML)
– WSDL – a standard method of describing web services and their specific capabilities (XML)
– UDDI – defines XML-based rules for building directories in which companies advertise themselves
and their web services.
“A Web service is a software system identified by a URI, whose public interfaces and bindings are defined and described using XML.
Its definition can be discovered by other software systems. These systems may then interact with the Web service in a manner
prescribed by its definition, using XML based messages conveyed by internet protocols.” - W3C

Advantages
– Open, text-based standards
– Modular approach
– Inexpensive to implement (relatively)
– Reduce the cost of enterprise application integration
– Incremental implementation

Real Web Services


• UC-Berkeley
– Unified Communications Technical Project
– unify email, voice, and fax into in-boxes accessible from cell phones, PDAs, or e-mail clients
Eastman Chemical Company
– distributors access chemical catalog in real-time and push info to customers

Accenture
– Live Information Models
– stock traders access real-time information from a single terminal

Dollar Rent-a-Car + Southwest Airlines


– Southwest runs Unix
– Dollar runs MS Windows
– Dollar turned its system into a web service
XML (Extensible Markup Language)
– Developed from Standard Generalized Markup Method (SGML)
– XML widely supported by W3C
– Essential characteristic is the separation of content from presentation
– XML describes only data
– Any application that understands XML can exchange data
– XML parser checks syntax
– If syntax is good the document is well-formed
– XML document can optionally reference a Document Type Definition (DTD), also called a Schema
– If an XML document adheres to the structure of the schema, it is valid
SOAP (Simple Object Access Protocol)
– SOAP enables between distributed systems
– SOAP message has three parts
– envelope – wraps entire message and contains header and body
– header – optional element with additional info such as security or routing
– body – application-specific data being communicated
A SOAP runtime engine basically adds a XML envelope to an existing XML document
SOAP Encoding
• Dealing directly with XML messages is not easy.
• Therefore, SOAP provides a “RPC emulation” technology (remote procedure call)
• The result: developers work with web services like with traditional RPC (e.g. CORBA,DCOM,DCE)
• The “RPC emulation” is named SOAP encoding.
• Fundamentally it is a set of rules to map a procedure invocation to a XML document.

The rules:
– method name -> first level element in the SOAP Body
– arguments identifiers -> second level elements
– arguments values -> third level elements
– arguments types -> attribute xsi:type
WSDL (Web Service Description Language)
• Web services are self-describing
• Description is written in WSDL, an XML-based language through which a web service conveys to
applications the methods that the service provides and how those methods are accessed
• WSDL is meant to be read by applications (not humans)

WSDL is a standard format to describe a Web Service (description stack)


A WSDL document is composed by two sections:
– An abstract interface section -> like in traditional IDL, it defines the signatures of procedures (RPC-
style) or messages (document-style)
– A deployment section -> it defines the service location and the supported transport protocols

Fundamentally a client uses the WSDL to create the stub or to dynamically decode messages.
– WSIL and UDDI are the standard way to search Web Services. (Discovery stack)
– WSIL is the decentralized approach.
– Fundamentally a WSIL document contains a directory of the Web Services deployed on a server.
– It is analogous to the index.html document for web pages.
– In the future, specific crawlers will browse the Internet looking for WSIL documents, like Google does
today for web pages.

Web Service Introspection Language


UDDI (Universal Description, Discovery and Integration)
– UDDI defines an XML-based format that describes electronic capabilities and business processes
– Entries are stored in a UDDI registry
– UDDI Business Registry (UBR)
– "white pages" – contact info, description
– "yellow pages" – classification info, details
– "green pages" – technical data
– uddi.microsoft.com

OASIS (The Organization for the Advancement of Structured Information Standards)


– Not competition to W3C
– Ensure that businesses acquire e-business tools that meet their needs
– United Nations Centre for Trade Facilitation and Electronic Business produced Electronic Business
XML (ebXML)
Web Services Security Architecture

WS-Security
Describes how to attach signature and encryption headers to SOAP messages; how to attach security tokens such
as X.509 certificates and Kerberos tickets.

WS-Policy
Describes the capabilities and constraints of the security and business policies on intermediaries and endpoints
WS-Privacy
Model for how web services and requesters state privacy preferences and organizational privacy practice
statements

WS-Secure Conversation
Manage and authenticate message exchanges between parties, including security context exchange and
establishing and deriving session keys

WS-Federation
Manage and broker trust relationships in a heterogeneous federated environment, including support for
federated identities.

WS-Authorization
Manage authorization data and authorization policy.

You might also like