uddi overview at astro seminars

7/30/2019 UDDI Overview at ASTRO Seminars

1/20

1

UDDI (Universal Description, Discovery,and Integration)

An Overview

Version :

Date :

Pages

Responsible Author :

Co-Authors :

Status :

Confidentiality :

1.0

07 Feb 2006

20

Gabriele Zacco ([email protected])

Draft [ ] Proposal [ ] Released [ X ]

Public [ ] Internal [ X ] Restricted [ ]


2/20

2

UDDI in a Nutshell

UDDI is a open, cross-industry effort driven by majorplatform and software providers, as well as marketplaceoperators and e-business leaders within the OASISstandard consortium

It defines a standard method for publishing and discovering

the network-based software components of a service-oriented architecture

UDDI creates a standard interoperable platform thatenables companies and applications to quickly, easily anddynamically find and use Web services over the Internet


3/20

3

A Bit of History

UDDI V1.0 (2000): Create foundation for registry of Internet-based business services

UDDI V2.0 (2003): Align specification with emerging Web servicesstandards and provide support for flexible, external taxonomies Has been implemented in many products by numerous vendors and open source

communities

UDDI V3.0 (Feb 2005): Support secure interaction of private andpublic implementations as key element of service-oriented

infrastructure. Many vendors are developing products that implement the UDDI V3.0

specifications This specification reflects the understanding of the need of supporting mostly

business internal Web services infrastructure rather than highly distributed ones. Current implementation recognizes the need for federated control in real-world

environments and further integrates the standard with other elements of serviceoriented infrastructure

Currently the OASIS UDDI Specification TC is working onimproving security, trustworthiness, semantics, and alignmentwith the Web Service Architecture and other standards


4/20

4

UDDI and Web Services

The UDDI protocol is another XML-based building block ofthe Web services stack along with SOAP (standard forinvoking remote operations) and WSDL (standard forspecifying what these operations look like)

UDDI supplies an infrastructure for systematically

addressing needs such as discovery, manageability andsecurity of Web services beyond what is the simpleorganization of their interactions

By addressing integration, coordination and flexibility issuesof service-oriented systems, UDDI plays an important rolewithin the service-oriented approach to enterprise softwaredesign


5/20

5

Accessing Web Services with UDDI

In some cases it may be that the information that are necessaryto access Web services are known and thus directly stored withinthe applications that use them

Nonetheless it is possible that the definitions and descriptions ofsuch services (WSDL) are published to be discovered on ad hocon-line registries

UDDI defines how these registry should be designed and how touse them to describe, publish and discover services on a network

Rather than forcing applications to include information about anexternal service's application programming interfaces, UDDIregistry provide this binding information dynamically, at run-time

UDDI guarantees flexibility with respect both to the dynamic run-time changes that occur during the life-cycle of web services andto the evolution ofweb application requirements


6/20

6

UDDIs Role in WS Software Development

By adopting UDDI, it turns out that convenience fordevelopers, requirements of enterprise architects, andunderlying business policies are not in opposition

UDDI facilitates Web services software development byproviding systematic, interoperable, standards-based: Management of the development process of web services

Approach for documenting and publishing web services Organizations and managing of web services across multiple systems

and development teams

Documenting interface specification through teams and through timeand for external applications above all in case of change

UDDI help drive better code reuse and developer

productivity (can help developers - across groups - find ashared service and use that service within their ownapplications)


7/20

7

UDDIs Role in SO Infrastructure

UDDI facilitates Service-Oriented Infrastructure: Insulates critical applications from changes or failures in backendservices:

Provides a formal layer of indirection (almost a firewall) necessary forservice-oriented application development and management, useful foraccommodating changes in the life cycle of specific components (updates,policy considerations, service termination)

Helps an organization share information about services in a controlledway that reflects its own business rules and policies:

Client authentication and publish/subscribe for peer registries satisfyoperational governance needs as control of the publication and distributionof information about deployed services according to business policies

Solutions are not hard-coded but takes advantage ofrun-

time binding


8/20

8

UDDI from the Businesses Point of View (1/2)

The UDDI Project enables businesses to: Discover each other

Define how they interact over the internet and share information in a globalregistry architecture

Enact policy-based distribution and management of enterprise web services

The UDDI project is not industry specific Any industry, of any size, worldwide, offering products and services can benefit

from this open initiative because the specifications comprehensively addressesproblems that limit the growth and synergies of B2B commerce and Webservices.

Before the UDDI project, there was no industry-wide approach forbusiness to reach their customers and partners with informationabout their products and Web services, nor there was a method ofhow to integrate into each other's systems and processes.

UDDI is the building block that enables businesses to quickly,easily and dynamically find and transact with one another via theirpreferred applications.


9/20

9

UDDI from the Businesses Point of View (2/2)

Problems solved: Makes it possible for organizations to quickly discover the right

business from millions currently on line

Defines how to enable commerce to be conducted once the preferredbusiness is discovered

Immediate benefits for businesses: Reaching new customers

Expanding offerings

Extending market reach

Increasing access to current customers

Solving customer-driven need to remove barriers to allow for rapidparticipation in the global Internet economy

Describing their services and business processes programmatically in a

single, open and secure environment Using a set of protocols that enables businesses to invoke services

over the internet to provide additional value to their preferredcustomers


10/20

10

UDDI Features

UDDI is similar to the concepts ofDNS and yellow pages In short, UDDI provides an approach to:

Locate a service

Invoke a service

Managemetadata about a service

UDDI specifies: Protocols for accessing a registryfor Web services Methods for controlling access to the registry

Mechanism for distributing or delegating records to other registries


11/20

11

UDDI Specifications

UDDI defines: SOAP APIs that applications use to query and to publish information toa UDDI registry

XML Schema schemata of the registry data model and the SOAPmessages format

WSDL definitions of the SOAP APIs

UDDI registry definitions (technical model - tModels) of variousidentifier and category systems that may be used to identify andcategorize UDDI registrations

The UDDI Specifications Technical Committee also developsTechnical Notes and Best Practice documents that aid usersin deploying and using UDDI registries effectively


12/20

12

UDDI Registry Service

The UDDI specifications define a registry service for Webservices and for other electronic and non-electronic services

A UDDI registry service is a Web service that support thedescription and discovery of service providers, serviceimplementations, and service metadata

UDDI is a meta service for locating web services byenabling robust queries against rich metadata.

Service providers can use UDDI to advertise the servicesthey offer

Service consumer can use UDDI to discover services that

suites their requirements and to obtain the servicemetadata needed to consume those services.


13/20

13

UDDI Registry

Functional purpose: representation of data and metadataabout Web services

Either for use on a public network or within onorganizational internal infrastructure

Offers standards-based mechanism to classify, catalog and

manage Web services so that they can be discovered andconsumed by other applications

Implements generalized strategy of indirection amongstservices based applications

Offers benefits to IT managers both at design and run-time,

including code reuse and improving infrastructuremanagement


14/20

14

UDDI Registry Types

UDDI allows operational registries to be maintained for different

purposes in different contexts A business may deploy one or more:

Private registries: Isolated from the public network, firewalled Restricted access No shared data

Public registries: Unrestricted open and public access Data is shared with other registries

Affiliated registries Controlled environment Access limited to authorized clients Data shared in a controlled manner

Private registry supports intranet applications, while a publicregistry support extranet applications

Affiliated registries supports all other infrastructural topologiese.g., involving delegation, distribution, replication, subscription,that reflects the realities and the relationship of the underlyingbusiness processes


15/20

15

UDDI Registry Data Model

The core information model of UDDI registries is made ofseveral data structures: businessEntity (info about the organization that published the service)

businessService (description of a service business function)

bindingTemplate (services technical details, including a reference tothe API)

tModel (attributes or metadata about the service such as taxonomies,

transports, digital signatures) publisherAssertions (relationship among entities in the registry, v2.0)

Subscription (standing request to track changes to a list of entities)

Each data structure within a given registry is assigned aunique UDDI key

UDDI allows users to specify different taxonomies forproviding semantic structure to the information about Webservices contained in a registry


16/20

16

UDDI Servers

UDDI specifies hierarchical relationship between a singleinstance of a UDDI implementation and others to which it isrelated

UDDI Servers can be: Nodes: supports a minimum set of functionalities of the specification

(they are member of exactly one registry)

Registry: composed of one or more nodes; supports the complete setof functionalities of the specification

Affiliated registry: registry that implements a policy-based sharing ofinformation together with other affiliated registry

Registry Affiliation is the main achievement of UDDI V3.0

Recognition that UDDI is to support the design and operations ofmyriads software applications within and among businessorganizations (not only private/public registries)


17/20

17

UDDI API

Features that supports core data management: Publishing information about a service to a registry

Searching a UDDI registry for information about a service

Features that supports registry interaction: Replicating and transferring custody of data about a service

Registration key generation and management

Registration subscription API set

Security and authorization

These are divided in Node API Sets (for UDDI Servers) andClient API Sets (for UDDI Clients)


18/20

18

UDDI Solutions

Several categories of product and components UDDI Registry Server, UDDI-enabled IDEs and development tools,

Java and .NET client toolkits and browsers, UDDI-integrated Webservices platforms

Supplied by multiple vendors, consortia and also availableas open source Apache.org, BEA, IBM, Microsoft, Oracle, SAP, Sun, Systinet,

UDDI4J.org

jUDDI is an open sourceJava based implementation of aUDDI v2 registry and a toolkit

UDDI4J is a Java class library that provides an API tointeract with a UDDI registry

Java Web Service Developer Pack by Sun Web Application Server by SAP

Webshpere UDDI Registry by IBM


19/20

19

UDDI Misc

WS-Discovery

WS-Inspection (Microsoft, IBM) specification (XML straightforward document structure) address the problem of findinga WSDL description for a given web service or its UDDIdescription and is going to become important, more thanUDDI within the three big web services technologies.


20/20

20

APPENDIX: UDDI Business Registry (UBR)

Free, public implementation of the UDDI standards, jointly operated by IBM,

Microsoft, NTT Communications and SAP, represents a registry of publicly available e-commerce services where was free to publish information to any of the UBR nodesand to query any of these.

It has represented an ideal environment for validating and proposing changes to thestandard of which it was a highly visible reference implementation

UDDI V3.0 was approved as an OASIS standard in February 2005. Having achievedthat milestone, the companies hosting the UDDI Business Registry (UBR) evaluatedthe results of hosting a reference implementation for the UDDI technology. Since thefall of 2000, the UBR has been a significant asset for testing during the development

of the three versions of the UDDI specifications and the vendor software based on it.UBR also provided a proof of concept for early Web services business applications.Considering that Web service and UDDI specifications are now mature standards andthe significant number of vendor supplied UDDI products that are available, hostingthis registry is no longer necessary. Over the past five years, as Web servicesapplications have matured, the role of UDDI based registries has also evolved in partbased on testing experiences with UBR. Registries based on UDDI have beenestablished within enterprises and organizations and have an important role in Webservices business applications. The availability of UBR provided valuable validationand guidance during the early days of UDDI. With the fulfillment of these goals, theUBR was discontinued

uddi overview at astro seminars

Documents