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.

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

5. WS- Addressing

6. WS-security

7. WS- Policy

8. WS- Reliable Messaging

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

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