About SOAP for xml and SOAP message structure. Web Services: WSDL and UDDI are explained

1. SOAP and Web Services
Unit - 4

2. SOAP
• Simple object access protocol.
• Carries on XML-RPC
• Background:
• SOAP 1.0
• SOAP 1.1
• SOAP 1.2

3. SOAP protocol
• HTTP, FTP, SMTP.

4. • SOAP use either direct connection or through middleware.
• SOAP has 3 parts:
• Encoding rules
• Rules for exchanging application
• Conventions
• One-way data transmission.

5. SOAP message structure
• 3 parts:
• SOAP envelope
• SOAP header
• SOAP body
• Example with zwiftbooks

6. Message path
• Server-to-server
• Intermediate nodes

7. SOAP intermediaries
• Proxies, caches, hops and gateways.
• URI

8. SOAP & Actors
• If no actor- reached final recipient.
• Rules: identify the parts, verify all parts, mustUnderstand

9. SOAP design pattern
• Layers pattern
• Pipe & filter pattern

10. SOAP faults
• Cannot understand or error occurs during process.
• It includes: faultcode, faultstring, details.

11. SOAP attachment
• DTD, Schema, UML diagrams, faxes, public & private keys.

12. SOAP & firewall
• SOAP uses port no:80

13. Web services Technologies
• Web service architecture:
• Service provider
• Service requester
• Repository/ broker
• Key technologies:
• UDDI
• WSDL
• SOAP

14. UDDI
• Universal description discovery & integration.
• Protocol for communicating with registries.
• Xml based specification.
• Public vs private registries.
• UDDI specification:
• UDDI programmer’s API specification.
• UDDI data structure specification.

15. UDDI & Zwiftswift
• Connect with UDDI business registry.
• Binding Template.
• Tmodel
• Invoke web services.

16. UDDI failure and recovery
• bindingTemplate
• Bindingkey
• Get_bindingTemplateAPI
• Retry on failure

17. WSDL
• Describes how to connect to web-service providers.
• XML format
• After discovering -> connect
• Direct client interaction

18. Port types & operations

20. • Web services pros & cons
• Maturity
• Security
• Transaction
• Configuration management