UDDI (Universal Description Discovery and Integration)
• To make Web services more useful the developers of Web services need to advertise their web services.
- You need to publish your services.
- You need to be able to find available services.
- You need to provide a convenient location for developers to download WSDL documents.
• To find available services we need to provide the same type of services that JNDI provides Enterprise
Beans (EJB).
- Using JNDI is a transfer of binary information unlike UDDI which uses SOAP and XML to transfer
data (text based).
- Another significant difference is the runtime nature of looking up EJB; UDDI isn’t typically used at
runtime, but before coding.
• A registry service for Web services must provide several features.
- The registry service must be public, or at least public enough to allow developers to share information.
- The way to register and lookup services must be vendor neutral.
- The registry must be global to your application, providing unchanging services.
• UDDI (Universal Description Discovery and Integration) is a standard aimed at producing a way to
find Web services.
• UDDI uses (unsurprisingly) XML and SOAP to describe the services available.
- UDDI is a definition of what services a registry (UDDI Registry) must support.
- UDDI uses SOAP messages to communicate these method calls between client and server.
• UDDI products provide a HTML-based user interface for browsing.
- Used by project teams to “discover” reusable services and learn more about them.
• UDDI browsers have been integrated into IDEs.
- Systinet Developer plugs into Eclipse and JBuilder.
• UDDI provides registry and lookup services separately by creating logical separations.
- The Business Life Cycle Manager interface provides the user with the ability to register and update
business listings on the UDDI Server.
- The Business Query Manager interface defines how to lookup and search the registry for businesses
and services.
• The original concept behind UDDI was of one universal “phone book” type of service.
- In practice, UDDI is not strictly required. If you can find a server’s WSDL file without using UDDI
you could still program web services.
- UDDI is also being used in a more local setting, only providing registration services for one company or
set of systems.
- UDDI is an important concept, but unlike in tightly coupled systems, it is not strictly required.
• To make Web services more useful the developers of Web services need to advertise their web services.
- You need to publish your services.
- You need to be able to find available services.
- You need to provide a convenient location for developers to download WSDL documents.
• To find available services we need to provide the same type of services that JNDI provides Enterprise
Beans (EJB).
- Using JNDI is a transfer of binary information unlike UDDI which uses SOAP and XML to transfer
data (text based).
- Another significant difference is the runtime nature of looking up EJB; UDDI isn’t typically used at
runtime, but before coding.
• A registry service for Web services must provide several features.
- The registry service must be public, or at least public enough to allow developers to share information.
- The way to register and lookup services must be vendor neutral.
- The registry must be global to your application, providing unchanging services.
• UDDI (Universal Description Discovery and Integration) is a standard aimed at producing a way to
find Web services.
• UDDI uses (unsurprisingly) XML and SOAP to describe the services available.
- UDDI is a definition of what services a registry (UDDI Registry) must support.
- UDDI uses SOAP messages to communicate these method calls between client and server.
• UDDI products provide a HTML-based user interface for browsing.
- Used by project teams to “discover” reusable services and learn more about them.
• UDDI browsers have been integrated into IDEs.
- Systinet Developer plugs into Eclipse and JBuilder.
• UDDI provides registry and lookup services separately by creating logical separations.
- The Business Life Cycle Manager interface provides the user with the ability to register and update
business listings on the UDDI Server.
- The Business Query Manager interface defines how to lookup and search the registry for businesses
and services.
• The original concept behind UDDI was of one universal “phone book” type of service.
- In practice, UDDI is not strictly required. If you can find a server’s WSDL file without using UDDI
you could still program web services.
- UDDI is also being used in a more local setting, only providing registration services for one company or
set of systems.
- UDDI is an important concept, but unlike in tightly coupled systems, it is not strictly required.
Table of Contents
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
UDDI
Courseware
Training Resources
Tutorials
Services