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

2. Ingeniørhøjskolen i Århus Slide 2 af 12 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. Ingeniørhøjskolen i Århus Slide 3 af 12 Service-Oriented Architecture (SOA) Client Server Registry Abstract Architechture - Webservice stack Abstract Architechture - Webservice stack Legacy code on server Legacy code on server 1 1 2 2 3 3 What we have seen so far

4. Ingeniørhøjskolen i Århus Slide 4 af 12 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. Ingeniørhøjskolen i Århus Slide 5 af 12 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. Ingeniørhøjskolen i Århus Slide 6 af 12 How UDDI works UDDI Business Registry 3.3. UBR assigns a programmatically unique identifier to each service and business registration Marketplaces, search engines, and business apps query the registry to discover services at other companies 4.4. Segrvice Type Reistrations SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services a Taxonomy 1.1. Business Registrations Businesses populate the registry with descriptions of the services they support 2.2. Business uses this data to facilitate easier integration with each other over the Web 5.5.

7. Ingeniørhøjskolen i Århus Slide 7 af 12 Registry and replication IBM Ariba Microsoft other Peer nodes (websites) Companies register with any node Registrations replicated on a daily basis Complete set of “registered” records available at all nodes Common set of SOAP APIs supported by all nodes Compliance enforced by business contract UDDI.org queries

8. Ingeniørhøjskolen i Århus Slide 8 af 12 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. Ingeniørhøjskolen i Århus Slide 9 af 12 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. Ingeniørhøjskolen i Århus Slide 10 af 12 Visual Studio – consuming a Web service

11. Ingeniørhøjskolen i Århus Slide 11 af 12 Finding a suitable Weather Web service

12. Ingeniørhøjskolen i Århus Slide 12 af 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