1 / 12

Presentation 9:

Presentation 9:. UDDI - Universel Description, Discovery & Integration. Outline. What we have seen so far Service-Oriented Architecture Service Registration and Discovery Why UDDI? Problem how to share Web services UDDI initiative is born How UDDI works Phonebook Metafor

stash
Download Presentation

Presentation 9:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Presentation 9: UDDI - Universel Description, Discovery & Integration

  2. Outline • What we have seen so far • Service-Oriented Architecture • Service Registration and Discovery • Why UDDI? • Problem how to share Web services • UDDI initiative is born • How UDDI works • Phonebook Metafor • ONLY NEED TO UNDERSTAND THE PRINCIPLES BEHIND UDDI • Why do we need UDDI • How can it support us (in Visual Studio for instance)

  3. Service-Oriented Architecture (SOA) What we have seen so far 3 Client Server Legacy code on server 1 2 Registry Abstract Architechture - Webservice stack

  4. How to share Web services? • Need to know the server location (WSDL URL) • Problem: How to discover Web services? • Newsgroups • Webpages? • Google? • UDDI is the ”Google of Web Services” • Can be accessed via GUI (for humans) • Or programmatically via SOAP for dynamic queries

  5. UDDI initiative is born • Naturally “evolved” • Ariba and IBM collaboration around B2B • IBM and Microsoft collaboration around XML and SOAP • Microsoft and Ariba collaboration around BizTalk and cXML • UDDI “born” in 2001

  6. 4. Marketplaces, search engines, and business apps query the registry to discover services at other companies 2. 5. BusinessRegistrations Businesses populate the registry with descriptions of the services they support Business uses this data to facilitate easier integration with each other over the Web 3. UBR assigns a programmatically unique identifier to each service and business registration How UDDI works 1. SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services a Taxonomy UDDI BusinessRegistry Segrvice Type Reistrations

  7. Registry and replication • Peer nodes (websites) • Companies registerwith any node • Registrations replicatedon a daily basis • Complete set of“registered” recordsavailable at all nodes • Common set ofSOAP APIs supportedby all nodes • Compliance enforced bybusiness contract queries IBM Ariba other UDDI.org other Microsoft

  8. Phonebook Metaphor • “ White pages” – Address, contact, and known identifiers • “ Yellow pages” • industrial categorizations • Industry: NAICS (Industry codes - US Govt.) • Product/Services: UN/SPSC (ECMA) • Location: Geographical taxonomy • “ Green pages” • technical information about services – incl. link to WSDL

  9. Who & What uses UDDI? • Tool building client (Service Consumer) • Visual Studio, JBuilder, JDeveloper and other IDE’s • Browse or search registry • Create a service proxy • Tool publishing the service • Visual Studio, JBuilder, JDeveloper and other IDE’s • Generates WSDL • Construct UDDI entries • Applications that needs dynamic binding • Directly access UDDI (via SOAP) • Query can be pre-generated • For AXIS – use UDDI4J from IBM or JAXR from Sun • WE WILL NOT DVELVE FURTHER INTO THIS!

  10. Visual Studio – consuming a Web service

  11. Finding a suitable Weather Web service

  12. Private UDDI registries • As a part of an application or intranet • For sharing data access • For dynamic binding • For load balancing & fail over – finding the right server • More will probably come • Maybe use other technologies – UDDI considered weakest link • Not wanting to share with others • Security concerns etc. • Problem with public UDDI registration: • only around 50% of the Web services actually works! • Because of ”no moderation” by editors

More Related