Scribd Logo
Upload

Welcome to Scribd!

  • Ashish V. Tendulkar: Directory Database Integration Group Persistent Systems Pvt. Ltd. Pune

    Uploaded by

    Farooq Mohammed
    87 views13 pages
    SOAP Outline The problem.. Why XML? Why HTTP? XML+HTTP = SOAP SOAP Details Uses of SOAP Example The problem.. Client App. Proxy Server Server Application Server Firewall Implications Industry not shifted completely to either one Vendor specific Lack of interoperability Require high-tech runtime environment Why XML? Simple

    Original Title

    xml-SOAP

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    SOAP Outline The problem.. Why XML? Why HTTP? XML+HTTP = SOAP SOAP Details Uses of SOAP Example The problem.. Client App. Proxy Server Server Application Server Firewall Implications Industry not shifted completely to either one Vendor specific Lack of interoperability Require high-tech runtime environment Why XML? Simple

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    87 views13 pages

    Ashish V. Tendulkar: Directory Database Integration Group Persistent Systems Pvt. Ltd. Pune

    Uploaded by

    Farooq Mohammed
    SOAP Outline The problem.. Why XML? Why HTTP? XML+HTTP = SOAP SOAP Details Uses of SOAP Example The problem.. Client App. Proxy Server Server Application Server Firewall Implications Industry not shifted completely to either one Vendor specific Lack of interoperability Require high-tech runtime environment Why XML? Simple

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    of 13

    SOAP

    Ashish V. Tendulkar
    Directory Database integration group
    (www.eusersolutions.com)
    Persistent Systems Pvt. Ltd. Pune
    (www.pspl.co.in)
    Outline

     The problem..
     Why XML?
     Why HTTP?
     XML+HTTP = SOAP
     SOAP Details
     Uses of SOAP
     Example
    The problem..

    Client Proxy Server


    App. Server
    Application
    Server

    Firewall
    Implications
     Industry not shifted completely to
    either one

     Vendor specific

     Lack of interoperability

     Require high-tech runtime


    environment
    Why XML?
     Simple text markup language

     Platform, language and vendor


    agnostic

     Easily extensible

     Capable of solving interoperability


    problem
    Why HTTP?

     Ubiquitous

     Supported by every web browser and


    server

     Effective technology for transferring


    text, graphics and other information
    XML + HTTP = SOAP
     HTTP is used for transport

     XML as encoding scheme

     Endpoint HTTP based URL for the target

     Object mapping: implementation specific


    SOAP call anatomy
    SOAP Component
    HTTP Headers Object Endpoint ID

    SOAP method name Method/Interface ID

    SOAP Envelope

    SOAP Header Extension Headers

    SOAP Body

    Call element Parameter Data


    Uses of SOAP
     SOAP greatly simplifies data exchange in
    B2B application over extranet
     Enables web site to integrate services
    from other sites
     Remote scripting more prevalent with
    SOAP
     Non-browser client could seamlessly
    access a service across web
    Example Message
    POST /string_server/Object17 HTTP/1.1
    Host: 209.110.197.2
    Content-Type: text/xml
    Content-Length: 152
    SOAPMethodName: urn:strings-com:IString#reverse

    <Envelope>
    <Body>
    <m:reverse xmlns:m='urn:strings-com:IString'>
    <theString>Hello, World</theString> </m:reverse>
    </Body>
    </Envelope>
    Example Response
    200 OK
    Content-Type: text/xml
    Content-Length: 162

    <Envelope>
    <Body>
    <m:reverseResponse xmlns:m='urn:strings-
    com:IString'>
    <result>dlroW ,olleH</result>
    </m:reverseResponse>
    </Body>
    </Envelope>
    Conclusion
     SOAP is platform independent, language
    neutral protocol
     SOAP does not replace COM and CORBA
     SOAP works in place of DCOM and IIOP
     SOAP does not pose huge security risks
     Supports interoperation between different
    vendor specific implementations

    You might also like