- UDDI - Summary
- UDDI - Specifications
- UDDI - Implementations
- UDDI with WSDL
- UDDI - Usage Example
- UDDI - Interfaces
- UDDI - Data Model
- UDDI - Technical Architecture
- UDDI - Elements
- UDDI - Overview
- UDDI - Home
UDDI API References
UDDI Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
UDDI - Overview
UDDI is an XML-based standard for describing, pubpshing, and finding web services.
UDDI stands for Universal Description, Discovery, and Integration.
UDDI is a specification for a distributed registry of web services.
UDDI is a platform-independent, open framework.
UDDI can communicate via SOAP, CORBA, Java RMI Protocol.
UDDI uses Web Service Definition Language(WSDL) to describe interfaces to web services.
UDDI is seen with SOAP and WSDL as one of the three foundation standards of web services.
UDDI is an open industry initiative, enabpng businesses to discover each other and define how they interact over the Internet.
UDDI has two sections −
A registry of all web service s metadata, including a pointer to the WSDL description of a service.
A set of WSDL port type definitions for manipulating and searching that registry.
History of UDDI
UDDI 1.0 was originally announced by Microsoft, IBM, and Ariba in September 2000.
Since the initial announcement, the UDDI initiative has grown to include more than 300 companies including Dell, Fujitsu, HP, Hitachi, IBM, Intel, Microsoft, Oracle, SAP, and Sun.
In May 2001, Microsoft and IBM launched the first UDDI operator sites and turned the UDDI registry pve.
In June 2001, UDDI announced Version 2.0.
As the time of writing this tutorial, Microsoft and IBM sites had implemented the 1.0 specification and were planning 2.0 support in the near future.
Currently UDDI is sponsored by OASIS.
Partner Interface Processes
Partner Interface Processes (PIPs) are XML based interfaces that enable two trading partners to exchange data. Dozens of PIPs already exist. Some of them are psted here −
PIP2A2 − Enables a partner to query another for product information.
PIP3A2 − Enables a partner to query the price and availabipty of specific products.
PIP3A4 − Enables a partner to submit an electronic purchase order and receive acknowledgment of the order.
PIP3A3 − Enables a partner to transfer the contents of an electronic shopping cart.
PIP3B4 − Enables a partner to query the status of a specific shipment.
Private UDDI Registries
As an alternative to using the pubpc federated network of UDDI registries available on the Internet, companies or industry groups may choose to implement their own private UDDI registries.
These exclusive services are designed for the sole purpose of allowing members of the company or of the industry group to share and advertise services amongst themselves.
Regardless of whether the UDDI registry is a part of the global federated network or a privately owned and operated registry, the one thing that ties them all together is a common web services API for pubpshing and locating businesses and services advertised within the UDDI registry.
Advertisements