Xml For Dummies Chapter 15 Using Xml With Web Servicesit-slideshares.blogspot.com


Published on


Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Xml For Dummies Chapter 15 Using Xml With Web Servicesit-slideshares.blogspot.com

  1. 1. XML FOR DUMMIES<br />Book author: Lucinda Dykes and Ed Tittel<br />Slides Prepared by Cong Tan<br />Part V : XML Application Development<br />Chapter 15: Using XML with Web services.<br />
  2. 2. Contents.<br />What’s up with Web Services?<br />A Web Services Architecture<br />Where Will Web Services Lead?<br />
  3. 3. 1. What’s up with Web Service.<br />In the Web services world, services customers—individuals, corporation, organizations, associations.<br />In this same world, service providers seek to advertise and promote their services so that service consumer can take a look at the wealth of resources and pass these services on to their customers.<br />Figure 15-1 illustrates how an e-mail client on the desktop sends and receive messages via mail servers on the Internet.<br />
  4. 4.
  5. 5. • A Web services model for e-mail(Hotmail, Yahoo! Mail, and other) take a different approach to e-mail access.<br />• Figure 15-2 shows how the Web services e-mail approach is different from the desktop client e-mail approach.<br />• You have to access a Web page and provide an account name and password to supply proof of identity before you can access stored data of the Web application service.<br />
  6. 6. 2. A Web Services Architecture.<br /> The Web Services Architecture is divided into four layers.<br />Higher layers depend and build on the capabilities supplied at lower layers. Here’s the list:<br />Discovery is the part of Web services environment in which service providers can supply descriptions of the information and services that they have to offer.<br />Description is the part of Web services in which available services and information are described in detail, along with the mechanisms necessary for prospective service consumers and service providers to exchange information with one another.<br />Packaging/Extensionsis the part of Web services that handles issues related to managing, packaging, and securing exchanges of information between a service consumer and a service provider.<br />Transportis the part of Web services that implements protocols related to moving messages from a sender to a receiver.<br />
  7. 7. 2.1 Transport: Moving XML messages.<br /> At Transport level — the bottom of the stack — software clients(like Web browsers) and service delivery software on Web servers communicate with each other.<br />Bottom line? The Transport layer acts like the highway that carries messages from senders to receivers.<br />
  8. 8. 2.1.1 SOAPing it up.<br /> SOAP is independent of platform and language.<br /> A SOAP message is an XML document that is sent via a transport protocol.<br />Underlying protocols in SOAP include not only the HTTP already used for everyday Web communications.<br /> SOAP 1.2, also supports protocols in addition to HTTP, including SMTP and TCP/IP.<br />
  9. 9. 2.1.2 SOAP revisited(version 1.2).<br /> SOAP 1.2 is a World Wide Web Consortium(W3C) Recommendation and consists of four basic parts:<br /> An envelope that describes what’s in a message and how to process it<br />A set of encoding rules for application-defined data types<br />A convention for remote procedure calls(RPCs) and response<br />A binding convention for exchanging messages via an underlying protocol.<br />SOAP allows application to invoke object methods on remote servers.<br />
  10. 10. 2.2 Packaging/Extensions: Managing information exchange.<br /> One layer up from the Transport layer in the Web Services Architecture is the Packaging/Extensions layer.<br />This layer is primarily concerned with establishing, managing, securing, and packaging information for exchange between service consumers and providers.<br />Packaging permits text information, images, and other kinds of binary data to be neatly encapsulated and sent to another party over a network.<br />Extensions address enhancements to basic messaging services for the following reasons:<br />To increase the level of security through encryption<br />To strengthen the credentials that establish consumer and provider identities.<br />To manage how messages are delivered from sender to receiver.<br />SOAP provides packaging and extensions for Web services by specifying a binding.<br />
  11. 11. 2.3 Description: Specifying services and related components.<br /> The Description layer encompasses a number of XML applications designed to describe the following:<br />How services are composed<br />How services may be used<br />How services can interact with other services<br />How services must behave<br />What services can offer potential consumers<br />Many languages are available for Description layer services.<br />WSDL can provide a catalog of Yahoo!’s many services and the particulars of each of them.<br />WSDL is an XML format that describes the basic form of Web services requests with different network protocols.<br /> It can be extended to any network protocol or messages format.<br />Each Web service includes a WSDL file that describes the bindings, methods, and data inputs and outputs.<br />
  12. 12. 2.4 Discovery: Finding What’s available.<br /> At the top of the Web Services Architecture, you find XML applications geared to registering Web Services for discovery by searching for services, inquiring about specific services, or inspecting what services a particular service provider offers.<br />The major XML application used for discovery is UDDI.<br />UDDI enables businesses to discover one another, to define how they can interact, and to share service description in a global registry.<br />UDDI is a method for finding Web services.<br />UDDI is built upon SOAP and is independent of platform and implementation.<br />Three types of information are provided in a UDDI registry:<br />Contract and general business information(services, categories, URLS)<br />Information about Web services a business provides and how an application finds a particular service<br />Technical details and binding information.<br />
  13. 13. 3. Where Will Web Services Lead?<br />Those who build Web services applications must master the details of numerous XML languages, as well as know a scripting and/or programming language.<br />The discovery process enables you to find Web services providers.<br />If you want to check out some Web services, here are some Web sites of interest:<br />XMethods:Xmethods(www.xmethods.com) provides a list of publicy available Web services that you can try out.<br />SOAPMethods: Tony Hong of Xmethods has a UDDI browser with a sample repository ready for immediate access at www.soapclient.com/uddisearch.html.<br />Microsoft UDDI Registry: The Microsoft UDDI registry is free, but you must registry to use it at http://uddi.microsoft.com/default.aspx.<br />Web Services List: The Web Services List offers a list of over 1000 Web services. This is updated very frequently and can be accessed at www.webservicelist.com.<br />
  14. 14. THE END<br />