Your SlideShare is downloading. ×
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Web Services (Nuts a..
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Web Services (Nuts a..


Published on

  • 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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Web Services (Nuts and Bolts) ITEC 625 Web Development Fall 2006 Reference : Building Web Services with Java (Making sense of XML, SOAP, WSDL, and UDDI), “Web Services Basics Part I” (Chapters 1-6),Graham et al., Developers Library, 2004
  • 2. Service-Oriented Architectures (SOAs)
    • Main roles
      • Service provider
        • Service description
      • Service requestor
      • Service registry
    • Operations
      • Publish, find, bind
  • 3. Why the fuss?
    • SOA augments and grows your applications portfolio to a portfolio of components (services and apps composed of services)
    • Organizations better able to construct software to integrate business processes and respond rapidly to changes in business environment.
    • Implicit, seamless software integration
    • Approach makes it easier to focus on business processes and tasks as services; less need to focus on underlying technical details of a service.
    • Easy selection of service interface design, most appropriate and existing IT investments for ease of building SOA, and best business processes.
  • 4. Justifying Web Services
    • Application integration is faster, cheaper
    • Many options for integration using many types of devices (PDAs, cell phones, desktops, etc)
    • Time to market is reduced
    • Use of standards provides benefits (choice of tools, more vendor options)
    • Relatively low cost of entry
    • Interface-based development reduces time to integrate applications
  • 5. Web Services vs. SOA
    • Associated but distinct.
    • SOA
      • An architectural concept , approach to building systems that focuses on loosely coupled set of component services that can be dynamically composed.
    • Web Services
      • One approach to building an SOA , providing a standard for a particular set of XML-based technologies that can be used to build SOA systems.
  • 6. XML
    • Document-centric vs Data-centric
    • Instances (prolog, elements, attributes)
    • Namespaces
    • Schemas
      • Well-formed, iaw rules of XML syntax
      • Valid, iaw DTD or Schema
      • Parsers can be validating/non-validating
      • If Valid, then well-formed
  • 7. XML Processing
    • Pull parsing: application asks parser to give it the next piece of info about the doc
    • Push parsing, event-based parsing: parser sends info to application about XML doc pieces encountered during the parse, sent in order, as they appear. Simple API for XML (SAX v. 2.0)
    • One-step parsing, DOM parsing. Parser reads whole document, generates a data structure (tree), deeply nested; DOM is language and platform independent. Don’t map well to native data structures, thus JDOM (Java DOM) for simplifying manipulation of doc trees in Java
    • Hybrid parsing, combinations
    • Issues: Memory efficiency, computational efficiency, ease of programming
    • Also JAXP, Java API for XML Processing, version 1.2
  • 8. XML Resources
    • DOM Level 1, 2
      • or 2
    • JAXB
      • http://
    • JAXP
      • http://
    • JDOM
      • http://
    • JSP1.2
      • http://
    • SAX
      • http:// /
    • XML, XML Namespaces, XML schema
      • or 1 or 2
  • 9. SOAP Protocol
    • Version 1.2
    • Two parts for spec
      • Part 1, the Messaging framework, central foundation
        • Processing model
        • Extensibility model
        • Message structure
      • Part 2, the Adjuncts
        • Optional
        • But give enough to developers (core of Part 1 is not enough)
  • 10. SOAP Resources
    • XML Protocol Working Group
    • SOAP 1.2 and Primer
    • SOAP with attachments
    • MTOM
    • XOP
  • 11. Describing Web Services
    • WSDL is an IDL (Interface Description Language)
    • A WSDL description describes:
      • What a service does, operations (methods), data needed (arguments and returns)
      • How a service is accessed, data formats and protocols, etc .
      • Where a service is located, URL, etc.
  • 12. Major elements of WSDL
    • portType
    • message
    • types
    • binding
    • port
    • service
  • 13. WSDL Resources
    • WSDL 1.1 and 2.0
    • WS-Policy and PolicyAttachment
  • 14. Implementing Web Services with Apache Axis
    • One of best Java-based Web services engines
    • One of most extensible, can be tuned to support new versions of SOAP
    • Can run on top of simple servlet engine or a full-blown J2EE application server
  • 15. Axis Resources
    • Apache Axis
    • Log4j
    • Jakarta Discovery library and commons
    • JUnit
    • SOAP builders
      • http://
  • 16. Discovering Web Services
    • Request copy of service description directly from provider
    • Centralized service registry (UDDI)
    • Other publication and service discovery mechanisms
      • At service provider’s point of offering
        • Using WS-Inspection specification (see resources)
      • Public repository of WSDL documents
        • http://
  • 17. UDDI Datatypes
    • businessEntity
    • businessService
    • bindingTemplate
    • tModel
    • publisherAssertion
  • 18. Using a UDDI Registry
    • A UDDI registry is itself an example of a Web Service
    • Entries in the registry can be published and queried using a SOAP-based interface
    • SOAP-based interface is used for all publish and query operations
    • Publishing usually requires registration and authentication token for creating, updating, deleting entries in the registry
    • For publishing…Each datatype uses Save API and Delete API
    • For inquiry… Each datatype uses Find API and Get API
  • 19. WSDL Service Interface Definitions for UDDI Registry
    • Inquiry API v2.0
    • Publication API v2.0
    • API v3.0 portTypes
    • API v3.0 Bindings
  • 20. UDDI Resources
    • UDDI specs
    • UDDI best practices
    • UDDI technical notes
    • WS-Inspection