Web service introduction 2
Download as PPTX, PDF2 likes1,172 views
This document provides an overview of web service specifications and standards including SOAP, WSDL, WS-Addressing, WS-Security, WS-Reliable Messaging, and BPEL. It discusses how WS-Addressing specifies endpoints and message addressing, how WS-Security provides identification, authentication, authorization, integrity and confidentiality, and how WS-Reliable Messaging ensures reliable message delivery. It also summarizes WS-I goals of achieving interoperability and its Basic Profile 1.0 recommendations.
Web service introduction 2
- 1. Introduction to Web Service - 2 SagaraGunathunga( Apache web Service and axis committer)
- 2. CONTENTS
- 3. WS specification overviewThere are some standard bodies to define specification related to Web Services generally known as WS-* specifications . SOAP
- 4. WSDL
- 6. WS-security
- 7. WS- Policy
- 9. WS -evening WS- NotificationWS-MetadataExchangeWS-Resource FrameworkWS-TransactionWS-AtomicTransactionWS-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 HeadersHost URIThe 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.htmlhttp://www.w3.org/TR/ws-addr-core/
- 15. Asynchronous communicationThe 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 addressingEndpoint is any addressable resource to which SOAP message can be sent (Web Service client or application, a SOAP router or any SOAP aware entityThe 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 ExtensionsWS – Security stackWS-SecureConversationWS-FederationWS-AuthorizationWS-PolicyWS-TrustWS-PrivacyWS-SecurityXKMSSAMLXACMLSPMLSoap FoundationXMLEncryptionXMLDigitalSignature1406.03.2005
- 21. WS – Security stack
- 22. WS – Security stack
- 23. Message Security vs. Transport SecurityMessage level Security - AdvantagesMessage level Security - Disadvantages
- 24. Message Security vs. Transport SecurityTransport level Security - AdvantagesTransport level Security - Disadvantages
- 25. WS - Reliable messaging
- 26. WS - Reliable messaging
- 27. WS – interoperability (WS- I)
- 28. WS-I GoalsAchieve Web services interoperability
- 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 requirementsWS- I DeliverablesProfiles
- 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
- 43. Use cases and usage scenarios based on customer requirements
- 44. Sample code and applications built in multiple environments
- 46. Test tools and supporting materials
- 47. Tools that test profile implementations for conformance with the profiles
- 48. Supporting documentation and white papersWS- I DeliverablesBasic 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 messageSample Applications and Testing Tools for the Basic Profile• Attachments Profile 1.0Complements the Basic Profile 1.1 to add support for conveying interoperable, SOAP with Attachments (SwA) with SOAP messagesWS- 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.0SOAP 1.1WSDL 1.1UDDI 2.0XML 1.0 (Second Edition)XML Schema Part 1: StructuresXML Schema Part 2: DatatypesThe Secure Sockets Layer Protocol Version 3.0RFC2246: The Transport Layer Security Protocol Version 1.0RFC2459: Internet X.509 Public Key Infrastructure Certificate and CRL ProfileRFC2616: HyperText Transfer Protocol 1.1RFC2818: HTTP over TLSRFC2965: 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 collaborationWeb 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 YouAeturnum Lanka (Pvt) Ltd197, Stanley Thilakaratna Mw, Nugegoda 10250, Sri LankaPhone: +94 11 5518177 | Email: [email protected]: www.aeturnum.com | www.athiva.com