Title: Introduction to UDDI
1Session 4
2Review of Session 3 (1 of 2)
- XML can be used with HTTP for communication
amongst applications working on different
platforms, giving a solution to the
interoperability problem. - SOAP is an XML-based protocol, which allows
components, and applications to communicate using
HTTP. - A SOAP message consists of a mandatory SOAP
envelope, a mandatory SOAP body and an optional
SOAP header.
3Review of Session 3 (2 of 2)
- The namespace identifier for the attributes and
elements defined in a SOAP envelope is
http//schemas.xmlsoap.org/envelope/. - Remote garbage collection is not supported by
SOAP. - The SOAP Fault element is used to transport error
or status information or both, within a SOAP
message. - The first new layer added by SOAP is the
element-normal-form encoding style described SOAP
specification.
4Objectives
- Define UDDI
- Recognize the need for UDDI
- Search the UDDI registries
- Describe the data structure model used in UDDI
- Discuss the fields present in the data structures
5Registering and Using Web Services
Available services
Need for services
Search
Register
UDDI
6UDDI
UDDI
Register
Search
Services
Need Services
- Stands for Universal Description, Discovery and
Integration - Helps businesses to
Describe the business and the services offered by
them
Discover other businesses, which may be of some
assistance
Integrate with other businesses for expansion
7UDDI Business Registry
Aims at integrating e-commerce sites
Markets Search Engines
Industries
UDDI Business Registry (UBR)
Business
Register / Search
8Working of UDDI
XML File
Submitted to
UDDI
Green Pages
White Pages
Yellow Pages
Technical information about the services
Includes address, contact etc.
Industrial Category information
9UDDI Business Registry (UBR)
Registrar
UBR
??? Future Nodes ???
Existing Nodes
Replicated daily
Register Directly
10Finding a Web Service (1)
- Go to the site http//www.uddi.org
Click
Choose a node
11Finding a Web Service (2)
12Registry Architecture and Data Structures
publisherAssertion (pA)
bindingTemplate (bT)
businessEntity (bE)
businessService (bS)
bE
pA
bE
pA
bS
bS
bS
bT
bT
tModel
tModel
13businessEntity
- Contains information about the party that
publishes descriptive information and the
services it offers.
14businessService
- Structure represents a logical service
classification - Contains a business description of the service,
a list of categories that describe the service,
and a list of pointers to references and
information related to the service.
15bindingTemplates
- Provides the technical descriptions about the
Web service - Each bindingTemplate has a single parent
businessService structure.
16tModel Structure
- Represents technical information about those
data structures, which are used as references by
instances of business entity. - Illustrates the manner in which the Web service
could be interacted.
17publisherAssertion
- publisherAssertion data structures bear
references to business entities
18Web Services and UDDI
UDDI A service on the Web that helps locate a
Web service
Search
UDDI
Client needs a Web service
Find
A collection of Web Services
19Summary (1 of 2)
- The data provided during a registration with UDDI
can be classified into white pages containing
general information about the business entity,
yellow pages that categorize the Web Service, and
the green pages consisting of technical
information about the services. - Companies hosting the UBR are known as node
operators. - A company, which does registration for another
company / business on its behalf, is known as a
registrar. - Access to and from UBR is done using SOAP.
20Summary (2 of 2)
- The data contained in the three pages can be
further classified into the following core data
structures - businessEntity
- businessService
- bindingTemplate
- tModel
- publisherAssertion
- No core data structure has more than one parent
structure. - A unique UDDI id (UUID) is given to each core
data structure.