Scribd Logo
Upload

Welcome to Scribd!

  • 338 views

    Webservices

    Uploaded by

    Sachin Singh
    This document provides an overview of web services, including definitions, basic and extended architectures, technologies, and standards. It defines a web service as a software system identified by a URI that exposes its interfaces using XML. The basic architecture involves technologies for exchanging messages, describing services, and publishing/discovering descriptions. Extended architectures add features like asynchronous messaging and reliable messaging. Key standards include SOAP for messaging, WSDL for interface descriptions, and WSIL/UDDI for service discovery.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    Webservices

    Uploaded by

    Sachin Singh
    338 views23 pages
    This document provides an overview of web services, including definitions, basic and extended architectures, technologies, and standards. It defines a web service as a software system identified by a URI that exposes its interfaces using XML. The basic architecture involves technologies for exchanging messages, describing services, and publishing/discovering descriptions. Extended architectures add features like asynchronous messaging and reliable messaging. Key standards include SOAP for messaging, WSDL for interface descriptions, and WSIL/UDDI for service discovery.

    Original Title

    webservices.ppt

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides an overview of web services, including definitions, basic and extended architectures, technologies, and standards. It defines a web service as a software system identified by a URI that exposes its interfaces using XML. The basic architecture involves technologies for exchanging messages, describing services, and publishing/discovering descriptions. Extended architectures add features like asynchronous messaging and reliable messaging. Key standards include SOAP for messaging, WSDL for interface descriptions, and WSIL/UDDI for service discovery.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    338 views23 pages

    Webservices

    Uploaded by

    Sachin Singh
    This document provides an overview of web services, including definitions, basic and extended architectures, technologies, and standards. It defines a web service as a software system identified by a URI that exposes its interfaces using XML. The basic architecture involves technologies for exchanging messages, describing services, and publishing/discovering descriptions. Extended architectures add features like asynchronous messaging and reliable messaging. Key standards include SOAP for messaging, WSDL for interface descriptions, and WSIL/UDDI for service discovery.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 23

    Web Services

    ICS 243F presentation


    Francesco Garelli, Leila Naslavsky

    Web Services - Definition from


    W3C
    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.

    Basic Architecture
    Technologies capable of:
    Exchanging messages
    Describing Web services
    Publishing and discovering Web
    service descriptions

    Role

    service
    requestor
    retrieves a
    service
    description

    Operation

    One-way,
    conversational,
    many-to-many

    A service publishes its


    description

    Component

    Extended Architecture

    Incorporates additional features and functionality by


    extending technologies and components defined within the
    basic architecture, such as:

    Asynchronous messaging
    Attachment typical usage : associating binary data with SOAP
    messages.
    Caching
    Message exchange pattern (MEP) - Describes a generalized
    pattern of message exchange between two services. e.g. : oneway, request/response, publish/subscribe, and broadcast.
    Reliable message - implementation of Reliable Messaging one
    MEP is a series of requests between two nodes with an
    acknowledgement SOAP Module.
    Message confidentiality Can transmit the message via SSL or
    TLS, or have a SOAP Module provides for encryption and
    decryption.
    Message integrity Can have a SOAP Module use digital
    signature.
    Session

    The Complete Web Services


    "Stack"

    More
    mature
    technologies

    The Wire Stack


    Transport: HTTP is
    the de facto, other
    may be supported.
    Packaging: SOAP is
    the de facto standard
    for XML messaging.
    Extensions :
    Additional information
    attached to web
    services messages.

    The Description Stack


    It is actually a stack of description
    documents defined using XML
    Schema.

    Not fully
    specified
    facts, or assertions, and
    rules that apply to a
    particular Web service

    minimum service description


    necessary to support
    interoperable Web services.

    Input/
    Output
    rendering
    Satisfied
    by WSDL

    The Discovery Stack


    WSIL : de-centralized
    service discovery method

    Service can be published using a variety of mechanisms:


    Direct publish: description sent directly to requestor;
    WSIL : HTTP GET retrieves descriptions from URL;
    Universal Description, Discovery and Integration (UDDI) registries: a
    Web-based distributed directory.
    Service requestors can retrieve a service description at design time
    (search by interface) or runtime (by communication and QoS) from a Web
    page (URL), a service description repository, a simple service registry or a
    UDDI registry. Discovery depends on how services are published;

    The technology so far


    The WS technology is completely based on XML.
    Therefore, both the data format and the
    interaction protocols are XML-based:
    costumized XML -> data format
    SOAP -> communication protocol
    WSDL -> the Interface definition language
    WSIL/UDDI -> standards for services discovery
    The lowest-level layers (the transport layer)
    should exploit some existing Internet
    protocols, like HTTP or SMTP

    What is XML
    XML is a simple tag-based language for
    describing information in a structured way.
    Basic elements:
    Tags
    Attributes
    LastName
    Allen
    Text
    StartTag

    Attributes

    Text

    EndTag

    <xhtml:table><xhtml:tr>
    <xhtml:td width="40%">LastName</xhtml:td>
    <xhtml:td width="60%">Allen</xhtml:td>
    </xhtml:tr></xhtml:table>

    How to work on XML


    The tree-like structure of XML makes developers
    life hard.
    In practice there is not a standard way for
    editing and analyzing, but the best method
    depends on your need. Just choose among:
    SAX -> callback-based parser
    DOM -> tree representation
    XSLT -> XML to XML conversion
    XPATH -> queries
    XML Binding -> transparent conversion to
    objects

    Simple Object Access


    Protocol
    SOAP is a technology to support the exchange of
    XML-coded messages over a transport protocol,
    such as HTTP and SMTP. (wire stack)

    Server

    Client

    HTTP
    SOAP
    XML

    Skeleton

    Stub

    SOAP
    Protocols Folding

    XML

    XML

    HTTP client

    POST
    HTTP 1.1 200 OK

    SOAP
    HTTP server

    SOAP basic mechanism

    Simple Object Access


    Protocol
    A SOAP runtime engine basically adds a XML
    envelope to an existing XML document
    SOAP Envelope
    SOAP Header
    Communicatio
    n Info
    SOAP Body
    XML
    Document

    Document Container

    Example

    <soap:Envelope>
    <soap:Header>
    <axis:SessionKey>
    SDHH37TYEW7R7
    </axis:SessionKey>
    </soap:Header>
    <soap:Body>
    <GetPrice>
    <Item>Apples</Item>
    </GetPrice>
    </soap:Body>
    </soap:Envelope>

    Session, Authentication,
    Routing, Security

    SOAP Encoding
    Dealing directly with XML messages is not easy.
    Therefore, SOAP provides a RPC emulation
    technology
    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.

    SOAP Encoding
    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

    Service Request

    ClockService.getTime(location="USA");
    <soap:Body>
    <getTime>
    <location xsi:type="xsd:string">USA</path>
    </getTime>
    </soap:Body>

    Web Service Description


    Language
    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 dinamically decode messages.

    Web Service Introspection


    Language
    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 anologous 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
    <inspection>
    <abstract>Acme Industries Public Web Services</abstract>
    <service>
    <name>Store Finder Service</name>
    <abstract>
    A service to perform a geographical search of Acme stores.
    </abstract>
    <description
    location="http://example.org/services/storefinder.wsdl"/>
    </service>
    <link location="http://example.org/services/ecommerce.wsil"/>
    </inspection>

    Service name

    Link to an other WSIL page


    Service location and description

    UDDI
    UDDI is a complimentary approach for searching
    based on a centralized repository.
    The repository is an electronic yellow pages for
    firms that offer web services online. Besides the
    names of services and their WSDL descriptors,
    firms can add a description of their business,
    phone numbers, addresses...
    At the moment UDDI repositories are offered by
    IBM, Microsoft and HP.

    Thank you
    This presentation is available at:
    http://www.dei.unipd.it/~garelli/ics243

    References
    J2EE: A platform of choice for Web Services.
    http://www.sun.it/eventi/codecamps_2002/pdf/j2ee_a_platfor
    m_of_choice_for_web_services.pdf
    XML in J2EE Platform.
    http://www.sun.it/eventi/codecamps_2002/pdf/xml_in_j2ee_pl
    atform.pdf
    A Busy Developers Guide to WSDL 1.1
    http://radio.weblogs.com/0101679/stories/2002/02/15/aBusy
    DevelopersGuideToWsdl11.html
    A Busy Developer's Guide to SOAP 1.1 .
    http://www.soapware.org/bdg
    A Young Person's Guide to The Simple Object Access Protocol.
    http://msdn.microsoft.com/msdnmag/issues/0300/soap/soap.
    asp
    An XML Overview Towards Understanding SOAP.
    http://msdn.microsoft.com/library/enus/dnwebsrv/html/xmloverchap2.asp

    References
    Deploying Web Services on Java 2, Enterprise Edition.
    http://developer.java.sun.com/developer/technicalArticles/Web
    Services/wsj2ee/
    The Python Web services developer. http://www106.ibm.com/developerworks/webservices/library/wspyth1.html
    Understanding WSDL in a UDDI registry. http://www106.ibm.com/developerworks/webservices/library/ws-wsdl/
    Dot-com builder overview of WSDL.
    http://dcb.sun.com/practices/webservices/overviews/overview
    _wsdl.jsp
    Getting Started with JAX-RPC.
    http://developer.java.sun.com/developer/technicalArticles/Web
    Services/getstartjaxrpc/
    Introduction to WSDL.
    http://www.devxpert.com/tutors/wsdl/wsdl.asp

    References
    Integrating SOAP into ebXML.
    http://www.itworld.com/AppDev/1472/ITW010404ebXML/
    Top ten FAQs for Web Services.
    http://www.oreillynet.com/pub/a/webservices/2002/02/12/web
    servicefaqs.html
    Web Services Introduction.
    http://www.perfectxml.com/WebSvc1.asp
    SOAP archives. http://www.soap.org/archive.iphtml
    SOAP Introduction.
    http://www.w3schools.com/soap/soap_intro.asp
    Web Services Description Language (WSDL) Explained.
    http://msdn.microsoft.com/library/enus/dnwebsrv/html/wsdlexplained.asp
    WSDL Interop Adventures.
    http://www.byte.com/documents/s=7031/byt1015007393289/
    0304_udell.html
    Java Web Services Tutorial.
    http://java.sun.com/webservices/docs/1.0/tutorial/doc/JavaWS
    TutorialTOC.html

    You might also like