Web service introduction 2

  • 1,989 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,989
On Slideshare
0
From Embeds
0
Number of Embeds
15

Actions

Shares
Downloads
78
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Introduction to Web Service - 2
    SagaraGunathunga
    ( Apache web Service and axis committer)
  • 2. CONTENTS
  • 3. WS specification overview
    There are some standard bodies to define specification related to
    Web Services generally known as WS-* specifications .
    WS- Notification
    WS-MetadataExchange
    WS-Resource Framework
    WS-Transaction
    WS-AtomicTransaction
    WS-BPEL
  • 10. WS- Addressing
    SOAP does not provide a standard way to specify
    where a message is going ?
    how to return a response ?
    where to report an error ?
    transport protocol such as HTTP , JMS can be used to define those properties .
  • 11. e.g. HTTP Headers
    Host URI
    The type of the
    message being
    conveyed is SOAP
    SOAP Action
  • 12. Conclusion
  • 13. WS – Addressing and WSDL
  • 14. WS – Addressing
    WS-Addressing was originally authored by Microsoft, IBM, BEA, Sun, and SAP and submitted to W3C for standardization. The W3C WS-Addressing Working Group has refined and augmented the specification in the process of standardization.
    http://xml.coverpages.org/ws-Addressing.html
    http://www.w3.org/TR/ws-addr-core/
  • 15. Asynchronous communication
    The address of the sender of the
    message, the addresses for return
    reply or fault messages are given
    current message has id “uuid:someid”
    and it is related with another message
    that has id “uuid:someotherid” and the
    type of the relationship is “Reply”
  • 16. Dynamic endpoint addressing
    Endpoint is any addressable resource to which SOAP message can be sent (Web Service client or application, a SOAP router or any SOAP aware entity
    The most logical way to include endpoints is to use WSDL “Service” element, however WSDL does not allow extensibility of this element, therefore EndpointReference is defined.
    <From>, <ReplyTo>, <FaultTo> tags convey an “EndpointReference”
  • 17. WS – Security
  • 18. WS – Security
    Identification
    Authentication
  • 19. Authorization
    Message integrity
    Confidentiality
  • 20. Security Extensions
    WS – Security stack
    WS-
    Secure
    Conversation
    WS-
    Federation
    WS-
    Authorization
    WS-Policy
    WS-Trust
    WS-Privacy
    WS-Security
    XKMS
    SAML
    XACML
    SPML
    Soap Foundation
    XML
    Encryption
    XML
    Digital
    Signature
    14
    06.03.2005
  • 21. WS – Security stack
  • 22. WS – Security stack
  • 23. Message Security vs. Transport Security
    Message level Security - Advantages
    Message level Security - Disadvantages
  • 24. Message Security vs. Transport Security
    Transport level Security - Advantages
    Transport level Security - Disadvantages
  • 25. WS - Reliable messaging
  • 26. WS - Reliable messaging
  • 27. WS – interoperability (WS- I)
  • 28. WS-I Goals
    • Achieve Web services interoperability
    • 29. Integrate specifications
    • 30. Promote consistent implementations
    • 31. Provide a visible representation of conformance
    • 32. Accelerate Web services deployment
    • 33. Offer implementation guidance and best practices
    • 34. Deliver tools and sample applications
    • 35. Provide a implementer’s forum where developers can collaborate
    • 36. Encourage Web services adoption
    • 37. Build industry consensus to reduce early adopter risks
    • 38. Provide a forum for end users to communicate requirements
    • 39. Raise awareness of customer business requirements
  • WS- I Deliverables
    • Profiles
    • 40. Defined set of specifications or standards at specific version levels
    • 41. Guidelines and conventions for using these specifications together in ways that ensure interoperability
    • 42. Sample applications
    • 43. Use cases and usage scenarios based on customer requirements
    • 44. Sample code and applications built in multiple environments
    • 45. Demonstrate profile-based interoperability
    • 46. Test tools and supporting materials
    • 47. Tools that test profile implementations for conformance with the profiles
    • 48. Supporting documentation and white papers
  • WS- I Deliverables
    • Basic Profile
    • 49. Basic Profile 1.0 and 1.1
    • 50. More than 200 interoperability issues resolved in the Basic Profile 1.0; conventions around messaging, description and discovery
    • 51. Simple SOAP Binding Profile 1.0
    — Derived from Basic Profile requirements related to serialization of an envelope and its representation in the message
    • Sample Applications and Testing Tools for the Basic Profile
    • Attachments Profile 1.0
    • Complements the Basic Profile 1.1 to add support for conveying interoperable, SOAP with Attachments (SwA) with SOAP messages
  • WS- I Basic profile 1
    • What is a profile?
    • 52. A set of specifications at specific version levels
    • 53. Guidelines and conventions for using the specifications together
    WS- I BP 1.0
    SOAP 1.1
    WSDL 1.1
    UDDI 2.0
    XML 1.0 (Second Edition)
    XML Schema Part 1: Structures
    XML Schema Part 2: Datatypes
    The Secure Sockets Layer Protocol Version 3.0
    RFC2246: The Transport Layer Security Protocol Version 1.0
    RFC2459: Internet X.509 Public Key Infrastructure Certificate and CRL Profile
    RFC2616: HyperText Transfer Protocol 1.1
    RFC2818: HTTP over TLS
    RFC2965: HTTP State Management Mechanism
  • 54. WS Composition
    • I n most of the real world scenarios it is required to interact with several services in a predefine or dynamic order.
    • 55. Businesses requires to quickly adapt to customer needs and market conditions EAI and B2B interactions (through web services)
    • 56. Needs to be flexible internally and externally
    • 57. Without a common set of standard, each organization is left to build their own set of proprietary business protocols
    • 58. Leaving little flexibility for true web services collaboration
  • Web Service Composition
  • 59. Static – Dynamic WS Compositions
  • 60. BPEL - Overview
  • 61. BPEL – example process
  • 62. BPEL - code sample
    <sequence>
    <receive partner=”buyer” … operation=”sendOrder” container=”request”/>
    <invoke partner=”supplier” … operation=”request” container=”order”/>
    <reply partner=”buyer” … operation=”response” container=”proposal”/>
    </sequence>
  • 63. BPEL – sample
  • 64. Thank You
    Aeturnum Lanka (Pvt) Ltd
    197, Stanley Thilakaratna Mw, Nugegoda 10250, Sri Lanka
    Phone: +94 11 5518177 | Email: info@aeturnum.com
    Web: www.aeturnum.com | www.athiva.com