Scribd
Upload
291 views11 pages

Uddi Tutorial

Uddi Tutorial

Uploaded by

Anusha Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
291 views11 pages

Uddi Tutorial

Uddi Tutorial

Uploaded by

Anusha Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.

About the Tutorial

UDDI is an XML-based standard for describing, publishing, and finding Web services. In
this tutorial, you will learn what is UDDI and why and how to use it.

Audience
This tutorial has been designed for beginners interested in learning the basic concepts of
UDDI.

Prerequisites
Since UDDI is an XML-based standard, all that you need to have is a basic understanding
of XML to make the most of this tutorial.

Copyright & Disclaimer


 Copyright 2015 by Tutorials Point (I) Pvt. Ltd.

All the content and graphics published in this e-book are the property of Tutorials Point
(I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or
republish any contents or a part of contents of this e-book in any manner without written
consent of the publisher.

We strive to update the contents of our website and tutorials as timely and as precisely
as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I)
Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our
website or its contents including this tutorial. If you discover any errors on our website or
in this tutorial, please notify us at contact@[Link]

i
Table of Contents
About the Tutorial .....................................................................................................................................

Audience ................................................................................................................................................... i

Prerequisites ............................................................................................................................................. i

Copyright & Disclaimer ............................................................................................................................. i

Table of Contents ..................................................................................................................................... ii

1. UDDI – OVERVIEW ................................................................................................................. 1

What is UDDI? .......................................................................................................................................... 1

History of UDDI ........................................................................................................................................ 1

Partner Interface Processes ..................................................................................................................... 1

Private UDDI Registries ............................................................................................................................ 2

2. UDDI – ELEMENTS .................................................................................................................. 3

White Pages ............................................................................................................................................. 3

Yellow Pages ............................................................................................................................................ 3

Green Pages ............................................................................................................................................. 3

3. UDDI – TECHNICAL ARCHITECTURE ........................................................................................ 4

UDDI Data Model ..................................................................................................................................... 4

UDDI API Specification ............................................................................................................................. 4

UDDI Cloud Services ................................................................................................................................. 4

4. UDDI – DATA MODEL ............................................................................................................. 6

businessEntity Data Structure .................................................................................................................. 6

businessService Data Structure ................................................................................................................ 7

bindingTemplate Data Structure .............................................................................................................. 7

tModel Data Structure ............................................................................................................................. 8

publisherAssertion Data Structure ........................................................................................................... 9

5. UDDI – INTERFACES.............................................................................................................. 10

ii
The Publisher Interface .......................................................................................................................... 10

The Inquiry Interface.............................................................................................................................. 11

6. UDDI – USAGE EXAMPLE ...................................................................................................... 12

Creating Registry .................................................................................................................................... 12

Retrieving Information ........................................................................................................................... 13

7. UDDI – UDDI WITH WSDL ..................................................................................................... 15

8. UDDI – IMPLEMENTATIONS ................................................................................................. 17

Java Implementations ............................................................................................................................ 17

Perl Implementation .............................................................................................................................. 17

Ruby Implementation ............................................................................................................................ 17

Python Implementation ......................................................................................................................... 17

9. UDDI – SPECIFICATIONS ....................................................................................................... 18

UDDI Replication .................................................................................................................................... 18

UDDI Operators ..................................................................................................................................... 18

UDDI Programmer's API ......................................................................................................................... 18

UDDI Data Structures ............................................................................................................................. 18

10. UDDI – SUMMARY.............................................................................................................. 19

What's Next? ......................................................................................................................................... 19

11. UDDI – API QUICK REFERENCE ........................................................................................... 20

The UDDI Inquiry APIs ............................................................................................................................ 20

The UDDI Publishing APIs ....................................................................................................................... 21

find_binding........................................................................................................................................... 22

find_business ......................................................................................................................................... 23

find_relatedBusinesses .......................................................................................................................... 24

find_service ........................................................................................................................................... 25

find_tModel ........................................................................................................................................... 26

iii
get_bindingDetail .................................................................................................................................. 27

get_businessDetail ................................................................................................................................. 27

get_businessDetailExt ............................................................................................................................ 28

get_serviceDetail ................................................................................................................................... 29

get_tModelDetail ................................................................................................................................... 29

get_authToken ....................................................................................................................................... 30

discard_authToken ................................................................................................................................ 31

save_business ........................................................................................................................................ 31

save_service .......................................................................................................................................... 33

save_binding .......................................................................................................................................... 34

save_tModel .......................................................................................................................................... 35

delete_business ..................................................................................................................................... 36

delete_service ........................................................................................................................................ 37

delete_binding ....................................................................................................................................... 38

Error Returned ....................................................................................................................................... 38

delete_tModel ....................................................................................................................................... 39

get_registeredInfo ................................................................................................................................. 40

set_publisherAssertions ......................................................................................................................... 40

add_publisherAssertions ....................................................................................................................... 41

delete_publisherAssertions ................................................................................................................... 42

get_assertionStatusReport .................................................................................................................... 43

get_publisherAssertions ........................................................................................................................ 44

Error Code Reference ............................................................................................................................. 45

iv
UDDI
1. UDDI – OVERVIEW

What is UDDI?
UDDI is an XML-based standard for describing, publishing, 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, enabling 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 live.

 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 listed here:

 PIP2A2: Enables a partner to query another for product information.

1
UDDI

 PIP3A2: Enables a partner to query the price and availability 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 public 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 publishing and locating businesses and services advertised within the
UDDI registry.

2
UDDI
2. UDDI – ELEMENTS

A business or a company can register three types of information into a UDDI registry. This
information is contained in three elements of UDDI.

These three elements are:

 White Pages,
 Yellow Pages, and
 Green Pages.

White Pages
White pages contain:

 Basic information about the company and its business.

 Basic contact information including business name, address, contact phone number,
etc.

 Unique identifiers for the company tax IDs. This information allows others to discover
your web service based upon your business identification.

Yellow Pages
 Yellow pages contain more details about the company. They include descriptions of the
kind of electronic capabilities the company can offer to anyone who wants to do
business with it.

 Yellow pages use commonly accepted industrial categorization schemes, industry


codes, product codes, business identification codes and the like to make it easier for
companies to search through the listings and find exactly what they want.

Green Pages
Green pages contain technical information about a web service. A green page allows someone
to bind to a web service after it's been found. It includes:

 The various interfaces

 The URL locations

 Discovery information and similar data required to find and run the web service.

NOTE: UDDI is not restricted to describing web services based on SOAP. Rather, UDDI can
be used to describe any service, from a single webpage or email address all the way up to
SOAP, CORBA, and Java RMI services.

3
UDDI
3. UDDI – TECHNICAL ARCHITECTURE

The UDDI technical architecture consists of three parts:

UDDI Data Model


UDDI Data Model is an XML Schema for describing businesses and web services. The data
model is described in detail in the "UDDI Data Model" chapter.

UDDI API Specification


It is a specification of API for searching and publishing UDDI data.

UDDI Cloud Services


These are operator sites that provide implementations of the UDDI specification and
synchronize all data on a scheduled basis.

The UDDI Business Registry (UBR), also known as the Public Cloud, is a conceptually single
system built from multiple nodes having their data synchronized through replication.

The current cloud services provide a logically centralized, but physically distributed, directory.
It means the data submitted to one root node will automatically be replicated across all the
other root nodes. Currently, data replication occurs every 24 hours.

UDDI cloud services are currently provided by Microsoft and IBM. Ariba had originally planned
to offer an operator as well, but has since backed away from the commitment. Additional
operators from other companies, including Hewlett-Packard, are planned for the near future.

It is also possible to set up private UDDI registries. For example, a large company may set
up its own private UDDI registry for registering all internal web services. As these registries
are not automatically synchronized with the root UDDI nodes, they are not considered as a
part of the UDDI cloud.

4
UDDI

5
UDDI

End of ebook preview

If you liked what you saw…

Buy it from our store @ [Link]

Common questions

Powered by AI

Private UDDI registries differ from public UDDI registries primarily in their purpose and data synchronization. Private registries are used exclusively within a company or industry group to share and advertise services among members and are not intended for public access . These registries are not automatically synchronized with UDDI cloud nodes, unlike public registries, which are part of the global federated network where data is regularly synchronized across different nodes, typically every 24 hours . This means private registries maintain internal data independently, while public registries benefit from broader visibility and cross-node data consistency.

Enterprises might face challenges such as handling the complexity of UDDI's XML schema, ensuring interoperability between different service platforms, and managing the synchronization of data within public or private registries . Additionally, the initial setup for secure and efficient communication using UDDI could require significant resources and expertise to implement. To mitigate these challenges, enterprises can invest in training to enhance their teams' understanding of XML and UDDI standards, utilize middleware solutions that facilitate integration, and establish clear protocols for data replication and synchronization to maintain data consistency across registries. Engaging with experienced service providers can also help streamline the implementation of UDDI infrastructures.

The UDDI Data Model is utilized by businesses to describe businesses and web services in a structured manner. It forms the basis for publishing and discovering web services in a UDDI registry, crucial for businesses that require interoperability between diverse systems . The core data structures of the UDDI Data Model include businessEntity, businessService, bindingTemplate, tModel, and publisherAssertion. These structures allow businesses to represent themselves (businessEntity), their services (businessService), their binding details (bindingTemplate), models of service technical specifications (tModel), and relationships between different business entities (publisherAssertion). This versatility makes the UDDI Data Model integral to managing and utilizing business-related web service information.

UDDI cloud services offer several advantages over traditional on-premises registries. These include greater scalability, as cloud services can handle varying loads without requiring physical infrastructure changes . They also provide enhanced data resilience and availability through automatically synchronized, distributed systems that ensure data consistency across multiple nodes, typically every 24 hours . Furthermore, cloud services facilitate easier global access and collaboration, given their integration into a federated network that supports broader service discovery and interaction with diverse industries. These benefits make UDDI cloud services attractive for businesses seeking reliable and scalable service registries without the burden of managing physical hardware.

UDDI's specification of APIs significantly enhances its functionality by providing standardized methods for developers to search and publish data within UDDI registries. The API specification streamlines the interaction process with the registries through defined operations such as find_business, find_service, get_businessDetail, save_business, and delete_business, among others . These APIs enable developers to efficiently discover and manage web services, ensuring seamless integration and communication across varying platforms. Furthermore, the use of APIs allows developers to automate UDDI tasks, reducing manual work and increasing productivity in service-oriented architecture environments .

The UDDI Inquiry API facilitates service discovery by providing well-defined operations that allow users to search and retrieve information about businesses and services in the UDDI registry . Critical operations of the Inquiry API include find_business, which searches for businesses based on various criteria; find_service, which identifies services under specified business entities; find_tModel, which locates technical models within the registry; get_businessDetail, which provides detailed business information; and get_serviceDetail, which retrieves comprehensive service descriptions . These operations enable efficient retrieval of necessary data, supporting seamless integration and usage of web services across different organizational needs and platforms.

UDDI supports several key interface processes known as Partner Interface Processes (PIPs) which facilitate interactions between trading partners by allowing data exchange through XML-based interfaces. Some PIPs include PIP2A2, which enables querying for product information; PIP3A2, which queries price and availability of products; PIP3A4, which allows submission and acknowledgment of electronic purchase orders; and PIP3B4, which queries shipment statuses . These processes streamline the interactions between business partners by providing standard interfaces for common trading activities, enhancing efficiency, and reducing the complexities associated with business-to-business integrations.

UDDI's development began with the announcement of UDDI 1.0 by Microsoft, IBM, and Ariba in September 2000. The initiative quickly garnered the support of over 300 companies, including major industry players like Dell, Fujitsu, and Sun, indicating widespread industry interest and collaboration . Microsoft and IBM led the first operational sites in May 2001. UDDI 2.0 was subsequently announced in June 2001, showing progression and adoption of the specification . The industry's role has been crucial in both the development and adoption of UDDI as a specification for web services discovery and integration, demonstrating a major collaborative effort to establish a universal web services framework.

UDDI consists of three primary components: White Pages, Yellow Pages, and Green Pages, each contributing uniquely to its functionality. White Pages contain basic information about the company, contact details, and unique identifiers, facilitating the discovery of web services through business identification . Yellow Pages provide detailed descriptions of the company's electronic capabilities using categorization schemes and industry codes, aiding companies in precise searches . Green Pages contain technical information about a web service, including interfaces, URL locations, and discovery data necessary for running the web service . Together, these components enable UDDI to serve as a comprehensive registry for the description, discovery, and integration of web services, supporting seamless interactions over the internet.

UDDI employs WSDL and SOAP as part of its core framework for describing, discovering, and integrating web services. WSDL is used to describe the interfaces to web services, providing a detailed specification of service functionalities and offering a standard method for defining operations and messages . SOAP serves as the communication protocol that allows UDDI registries to interact with web services across different platforms. This integration offers significant benefits, including platform independence, interoperability, and the ability to automatically bind to and execute services, leveraging UDDI's registry functions combined with WSDL's descriptive capabilities and SOAP's communication efficiency .

You might also like