Universal Description, Discovery and Integration (UDDI) is a registry record or data base where publishers publish there service and consumers can search for the desired service.

1. UDDI AND DISTRIBUTED
ENVIRONMENT
Presented By : Submitted To:
Aniket Choudhury prof. Jasmine Jha
140320702501(C.E)

2. OUTLINE
 Introduction
 History
 Architecture
 Data inside UDDI
 UDDI Technical Overview
 UDDI data model
 Working
 Conclusion
 References

3. INTRODUCTION
What is UDDI?
 UDDI[3] stands for Universal Description, Discovery, and
Integration.
 Defines a way to publish and discover information about
web services.
 “Web service” describes specific business functionality
to be used by another company.
 It represents technical specification for publishing and
finding businesses and Web services.

4. WEB SERVICE PROTOCOL STACK

5. HISTORY
 UDDI 1.0 was originally announced by Microsoft, IBM
and Ariba in September 2000
 UDDI 2.0 was announced in June 2001
 Approved by the Organization for the Advancement of
Structured Information Standards (OASIS) as a formal
standard in April 2003
 Currently UDDI 3.0 has been published as OASIS
committee specifications.

6. ARCHITECTURE
 UDDI Registry Record[3]

7. DATA INSIDE UDDI
The data captured within UDDI is divided into
three main categories:
White page[2]:
 Contain general info about a specific company.
 E.g. Business name, business description, contact info, address
and phone nos.
Yellow pages[2]:
 Extend the ability to locate a business or service .
 Support classification using various taxonomy systems for
categorization.

8. CONTI…
 Green pages[2]:
 Provide information on how and where to programmatically
invoke a service .
 Contain technical info about a Web service.
 Provide address for invoking service.
 Not necessary SOAP-based service.
 Can provide references to a Web page, email address or services
using other component technologies, CORBA, RMI, etc.

9. CONTI…

10. EXAMPLE
 Let us consider an example of RosettaNet[4]

11. CONTI…
One of RosettaNet’s[4] main accomplishments is
the creation of Partner Interface Processes (PIPs)
PIPs are XML-based interfaces that enable two
trading partners to exchange data. E.g.
 PIP2A2: Enable a partner to query another for product info.
 PIP3A4: Enable a partner to submit an electronic purchase
order and receive acknowledgement of the order.
Many PIPs have been registered within the
UDDI of RosettaNet[4] .

12. CONTI…
RosettaNet[4] facilitates, using its UDDI, the
semiconductor companies to integrate into
existing supply chains
– The companies can register themselves in the UDDI to
advertise their components.
– By using PIP2A2, the buyers can query their product info.
– If everything’s fine, the buyers can also submit the purchase
order using PIP3A4.

13. CONTI…
RosettaNet[4] is just a Web portal with the
following additional features:
– Automatic
 Operations, such as discovering and publishing, are not
only done by human but also computer programs
automatically.
– Standard interface
 PIPs are provided for human or computer programs to
communicate.
– Seamless integration
 Allow integration of services by chaining together services
at run time.

14. UDDI DATA MODEL
 UDDI includes an XML Schema that describes
four core types of information:
– businessEntity
 About the actual business, e.g. business name, etc.
– businessService
 About the services provided by the business
– bindingTemplate
 About how and where to access a specific service
– tModel (Technical Model)
 Include descriptions and pointers to external technical
specifications or taxonomies

15. CONTI…

16. CONTI…

17. CONTI…
 businessEntity element includes info about the
actual business
– Business name, description, contact info such as address,
phone, contact person, etc.
 Each business will receive a unique
businessKey value when registration to a UDDI
server
– e.g. businessKey of Microsoft in its UDDI server:
0076b468-eb27-42e5-ac09-9955cff462a3
 The key is used to tie a business to its published
services

18. CONTI…
 Can also include other unique value(s) in
identifierBag that identifies the company.
 Businesses can also register multiple business
categories in categoryBag based on standard
taxonomies.

19. CONTI…

20. CONTI…

21. CONTI…
 businessService element includes info about a single
web service or a group of related Web services
 Include the name, description and an optional list of
bindingTemplates
 Like businessEnitity, each businessService has a unique
service key
 Should specify the businessKey to relate with the
business that provides that service

22. CONTI…

23. CONTI…
 BindingTemplate element includes info about how and
where to access a specific web service
 The serviceKey ties the bindingTemplate with the
businessService “the Stock Quote Service”.
 tModelInstanceDetails should further specify the key of
the tModel used in this service

24. CONTI…
 tModels are primarily used to provide pointers to
external technical specifications
 Binding Template only provides info about where to
access the SOAP binding, but not how to interface with it
 tModel element fills this gap by providing a pointer to an
external specification, such as WSDL
 In fact, tModels are not reserved to Web services

25. CONTI..

26. CONTI..

27. working
UDDI Registry
Company ABC
ABC
Business
ABC
Service
ABC
tModel
Publication
Step 1

28. Step 2
UDDI Registry
Company XYZ
find_business (ABC)
ABC’s
businessKey = ba744ed0-3aaf-11d5-80dc-002035229c64
serviceKey = d5921160-3e16-11d5-98bf-002035229c64

29. Step 3
UDDI Registry
Company XYZ
get_serviceDetail
(ABC’s serviceKey)
ABC’s service
accessPoint = http://services.xmethods.net:80/soap
tModelKey = uuid:0e727db0-3e14-11d5-98bf-002035

30. Step 4
UDDI Registry
Company XYZ
get_tModelDetail
(tModelKey)
tModel’s
overviewURL =
http://www.xmethods.net/tmodels/SimpleStockQuote.wsdl

31. Step 4Step 5
Company XYZ
(access point and
http://www.xmethods.net/tmodels/SimpleSt
ockQuote.wsdl)
Company ABC
WSDL document
Helper files

32. Step 4Step 6
Company XYZ
Based on the helper files, invoke the
service
Company ABC
Result

33. CONCLUSION
 UDDI(Universal Description,Discovery, and Integration)
is an XML-based registry for businesses worldwide to
list themselves on the Internet.
 It streamlines online transactions by enabling companies
to find one another on the Web and make their systems
inter-operable for e-commerce.

34. REFERENCES
Papers:
[1] "UDDI Technical White Paper". Retrieved 6 September 2000.
[2] Justin R. Erenkrantz, “Web Services: SOAP, UDDI, and
Semantic Web”, ICS 221, University of California, Irvine, CA
92697-3425
Books:
[3] Thomas Erl, “Web Services and Primitive SOA,” in Service-
Oriented Architecture: Concepts, Technology, and Design, vol. 4,
Prentice Hall PTR, Eds. San Francisco, CA: Academic, 2005,
pp. 139-141.
[4]RosettaNet[Online]. Available:
http://en.wikipedia.org/wiki/RosettaNet

35. THANK YOU