Transcript UDDI Registry

UDDI
Universal Description,
Discovery & Integration
By
C.Madhumathi,
II MCA ‘B’ sec,
Bharathidasan University,
Tiruchirappalli
•
•
•
•
CONTENTS
Introduction
Evolution of UDDI
UDDI- At a Glance
Analogies with telephone directories
– White pages
– Yellow pages
– Green pages
• The UDDI Business registry
• Conclusion
• References
INTRODUCTION
 Businesses along a value chain - use UDDI registries
dynamically and automatically - select new business
partners, locate the electronic services implemented by
them - start executing e-commerce transactions with
them.
 Is UDDI DOA (Dead On Arrival) ?
 What will enterprises do with UDDI?
 What do enterprise architects have to know about
UDDI ?
ADVANTAGES
• Wipe out the need for human
interaction in many business tasks
• Reduce overheads
• Reduce middleman costs
Thus,
fundamentally enable a dynamic and
fluid e-business environment
Evolution of UDDI
Overview
Evolution of UDDI (Cont)
What is new in Version 3? (Topics)
• Registration key generation and management
(integrity)
• Registration subscription API set
• XML digital signatures (security)
All to enhance Registry Interaction
Foundation for Web Services
Publish and Discover Services:
UDDI
Formal Service Descriptions: WSDL
Service Interactions:
SOAP
Universal Data Format:
XML
Ubiquitous Communications: Internet
Broad Industry Support, Simple Process
UDDI – At a glance
 UDDI is a registry and a protocol for
publishing and discovering web services.
 As web services – standards-based,
open and platform-independent means of
accessing functional capabilities of other
companies.
 UDDI – used in publishing and locating
those services.
SERVICES ORIENTED ARCHITECTURE
(SOA)
 Issue of locating web services becomes increasingly
important
 Each company controlled everything - both the
services and the consuming applications
 Necessary information about the services - Priori
 Which business partners have this service?
 What types of services do these partners offer?
 Emerging need: For a registry where a
service provider could publish not only list of their
services but also information necessary to use the
services.
 Businesses could search through the registry to
discover those service providers and their services.
ANALOGIES WITH TELEPHONE
DIRECTORIES
Phone Book
•
•
•
Directory of telephone numbers,
addresses of large number of people
and business.
When adding or updating entries, the
requester must validate his/her
identity and provide evidence that
he/she has the right to add or change
the information.
•
Changes in phone books become critical
•
Search from an alphabetical listing of
people or business names or through
categories of business.
Directory of technical information about
the web services that are available from
different service provider.
•
It provides to add new services,remove
existing services and changing the
contact(ie endpoint) information for
services.
•
Only authenticated users(eg.Service
providers)can add or change their
information on the UDDI registry.nonauthenticated users are not allowed to
change any information on a UDDI
registry.
•
Since it is dynamic changes can be easily
accomodated.
•
Straightforward name lookup,or may
involve searching through the
taxonomies(service provider
categories)provided by the UDDI
registry.
Only the phone company or its
authorized agent publishes the phone
book.
•
UDDI Registry
What Problems Do We Solve?
Broader
B2B
Smarter
Search
Easier
Aggregation
Web Service
Visibility
An organization needs to
create 400 electronic
relationships with
partners, each with its
own standards and
protocols
Describe
Services
A small business wants to
be “plugged in” to every
marketplace in the world,
but doesn’t know how
Discover
Services
A B2B marketplace cannot
get catalog data for
relevant suppliers in its
industry, along with
connections to shippers,
insurers, etc.
Integrate
Them
Together
Provide a standards-based
profile for all electronic
services that are
provided. Includes web
sites, other electronic
resources
Publish for
Accessibility
• Business or entity name
• General business description
– Any number of languages
• Contact info about the service provider
– Names, address, phone numbers,
fax numbers, web sites, etc.
– Other short description information about the service
provider.
• Known identifiers
– List of unique identifiers for locating the business
Eg: domain name, stock ticker symbol, etc
• Business categories under which web services
implementing funtionalities within those
categories can be found.
– 3 base taxonomies in V1
• Industry: NAICS (Industry codes - US
Govt.)
• Product/Services: UNSPSC (ECCMA)
• Location: Geographical taxonomy (ISO 3166)
• …easy extension in upcoming releases
• New set of information businesses use to describe how to
“do e-commerce” with them.
• Technical information about the capabilities and behavioral
grouping of web services.
– Nested model
• Business process (functional)
• Service specifications (technical)
• Binding information (implementation)
– Programming/platform/
Services can also be categorized
Similarities between Telephone
Directory and UDDI registeries
Telephone Directory Book
Search
for
business
Business Name
Phone Number
Address
Connect with
Business using
phone number
UDDI Registry
Search for
business and
services
Business Name
Service Endpoint
Service Description
Connect with
Business using
Service
endpoint
How people use Telephone
Directory?
• User-Product-in mind. Looks up-business names-to
find their contact information.
• Searches-product categories-locate a vendor.
Identified-suitable vendor-looks up phone no and
contacts the vendor.
• Multiple possible vendors:
Winning vendor-chose based on
 price
 a lot of business with the vendor in the past
User-shy away-vendor-unreliable or has
delivered shoddy product.
How people use UDDI
registry?
• Users-search-UDDI registry-appropriate web
service-meets their needs.
• Searching through the taxonomies (service provider
categories) provided by the UDDI registry.
Multiple Web services:
Winner-based on
 Cost
 Personal preferences
 Business Relationships
Each Web service implements a unique API.
No direct interaction with UDDI registeries.
..contd
• Information-UDDI-not people friendly.
Portals and Software tools-access to UDDI
registeries.
• Middleware and Application Development toolssupport web service development-allow users-easily
 add new services
 Browsing through the services
• Augument information-with their own analysis.
• Analysis-based on QoS (Quality-of-service)
information.
• Which Web service to use for a particular application
is based on:
 Technical needs
 QoS requirements
 Business relationships
Typical roles played while
interacting with an UDDI
registry
Technical
Requirements
Programmer
Selected
Service
Get Binding
Information for
Selected Service
Business
Analyst
Select Web
Service
UDDI
Registry
Selection of Web Services
• Business issues-quite fluid.
• Dynamics-most business environments-rapidly changing
relationships results in continuously changing-or atleast
evoloving business-driven requirements.
• Flexibility in selecting and consuming web services is important.
• Misconception-dynamically select and consume web services.
• Software-Some degree of human intervention-automation-web
services-implements-unique API-Programmatic and architectural
changes to the consuming application.
• Some newer tools support the use of business rules to automate
the process of service selection but some level human
intervention is necessary.
The UDDI Business Registry
(UBR)
• It is a global implementation-UDDI specification.
• It is a single registry for web services.
• A group of companies operate and host UBR nodes, each of
which is an identical copy of all other nodes.
• New entries or updates are entered into a single node, but are
propagated to all other nodes.
• The UBR is a key element of the deployment of Web services
and provides the following capabilities:

A centralized registration facility at which to publish and
make others aware of the web services a company makes
available.

A centralized search facility at which companies that
require a particular service can locate businesses that provide
that service as well as relevant information about that service.
Various means of accessing and
interacting with an UDDI Registry.
Service Marketplace
Access
Service Aggregator
Access
Web Portal Access
Direct programmatic
Access
UDDI
Registry
Two important and Relevant
features of the API
• UBR nodes implement a simple API for direct electronic
(computer-to-computer) access to the contents of the registry.
• Searches available for web services are done through human
friendly means: phone conversations between existing business
partners,the home pages of the UBR, Web service aggregator
portals such as www.xmethods.com or a standard web search
engines such as Google.
• UBR node home pages also provide information pertaining to
UDDI or to that particular UBR node. This information includes
policies on data replication, publishing restrictions and other
administrative or usage issues.
Two important and Relevant
features of the API
Features
of API
Inquiry
Publication
..contd
• Inquiry API:
It allows searching through the registry for information
about businesses, the web services the business makes available,
as well as implementation and interface information for each
service.

Inquiry API and home page use standard HTTP.

•
Publication API:
It allows adding, changing and deleting business and service
information within the registry.

Endpoint requires authentication and uses the HTTPS
protocol.

..contd
• URL access endpoint information of the home page,
inquiry API and publication API of each UBR node is
different.
• Operator nodes:
Provides a fully functional test environments
where companies can develop and test their offering
without affecting other users.
• Test nodes:
It provides a inquiry, publication to test their
services.
How UDDI Works
Software companies, standards
bodies, and developers populate
the registry with descriptions
(specifications) of types of
services
1.
4.
2.
Marketplaces, search
engines, and business
applications query the
registry to discover
services at other
companies and to facilitate
integration
UDDI Registry
Implementers
populate the
registry with
descriptions of
their businesses
and the services
they expose
Implementations
3.
Service Types
5.
UDDI Registry assigns a programmatically unique
identifier to each service and registration
Large businesses
apply the same
architecture and
technologies internally
Public Registry Operation
• Peer registry nodes (websites)
• Information registered
with any node
• Registrations replicated
on a daily basis
• Complete set of
IBM
“registered” records
available at all nodes
• Common set of
SOAP APIs supported
other
by all nodes
• Compliance enforced
by business contract
other
• All technologies applied
–
Interoperability
verified constantly
Developers
Applications
Marketplaces
queries
UDDI.org
Microsoft
End Users
HP (planned)
Conclusion
• UDDI has evolved to reflect today’s
pragmatic business requirements.
• V3 emphasizes the interaction of
private and public registries.
References
• UDDI
– http://www.uddi.org
– http://uddi.microsoft.com
- http://www.ibm.com/in/en/