This document discusses UDDI (Universal Description, Discovery and Integration), which is a standard for web services registries. It contains 6 sessions that cover topics like UDDI overview, plug and play, metadata, programming SDKs, BizTalk integration, and delivering UDDI architecture. The agenda introduces UDDI and discusses its key concepts like the data model, APIs, behaviors, and policy. It also explains how UDDI organizes information into white pages (basic company info), yellow pages (service classifications), and green pages (technical details).

1. Produced By: ARCOM Architecture TeamProduced By: ARCOM Architecture Team
•Mohamed zakaryaMohamed zakarya
•Ahmed ZewitaAhmed Zewita
•Ahmed AssarAhmed Assar
•Shady abo shadyShady abo shady
•Sarfaraz AhmedSarfaraz Ahmed
About ARCOM SERVICES: http://www.arcom.com.sa/index.htmlAbout ARCOM SERVICES: http://www.arcom.com.sa/index.html
1
WE DELIVER, WE SETTING STANDARDS
Information Technology & Communications

2. 2
Session 1 : UDDI Overview
Session 2.0: UDDI Plug and Play Part 1
Session 2.1: UDDI Plug and Play Part 2
Session 3.0: UDDI Deep Knowledge in Meta-Data Part 1
Session 3.1: UDDI Deep Knowledge in Meta-Data Part 2
Session 3.2: UDDI Deep Knowledge in Meta-Data Part 3
Session 4: UDDI Programming SDK
Session 5: UDDI with BizTalk ESB Toolkit
Session 6 : Update Architecture Repository with UDDI Deliverable
Agenda::

3. Introduction to UDDI

4. 4
Overview
• The Universal Description, Discovery, and Integration (UDDI)
protocol is a central element of the group of related standards that
comprise the Web services stack.
• The UDDI specification defines a standard method for publishing and
discovering the network-based software components of a service-
oriented architecture (SOA).
• Its development is led by the OASIS consortium of enterprise software
vendors and customers.

5. Why UDDI?
• There is huge power for SOA governance
• If you store process policy SLA and related information about service
in a registry
• Gartner believes that registries will be to minimally discover and
document service and preferably to enable the government function
uddi 5

6. 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.
6

7. Why a Registry?
•Location and invocation metadata for run-time binding
•Flexibility for business rules: security, transport, quality of service, etc.
•Structure for otherwise ad hoc process of component interactions
7

8. What’s in UDDI?
• UDDI Data Model
• Programmer APIs
• Behaviors of Node and Registry
• Policy
8

9. 9
Typical Applications of A UDDI Registry
• A UDDI registry’s functional purpose is the representation of data and
metadata about Web services.
– Use on a public network or within an organization’s internal infrastructure
– A standards-based mechanism to classify, catalog, and manage Web services, so
that they can be discovered and consumed by other applications
• UDDI offers several benefits to IT managers
– Publishing information about Web services and categorization rules specific to an
organization
– Finding Web services (within an organization or across organizational boundaries)
that meet given criteria
– Determining the security and transport protocols supported by a given Web service
and the parameters necessary to invoke the service
– Providing a means to insulate applications (and providing fail-over and intelligent
routing) from failures or changes in invoked services

10. 10
A Brief History of UDDI

11. UDDI Elements
• A business or company can register three types of information into a
UDDI registry.
• This information is contained into three elements of UDDIs, which
are:
• 1.White pages,
• 2.Yellow pages,
• 3.Green pages
11

12. White Pages
• UDDI white pages category contains:
• Basic information about the Company and its business.
• Basic contact information including business name, address, contact
phone number etc.
• A unique identifier for the company tax ID. This information a llows
others to discover your web service based upon your business
identification.
12

13. Yellow Pages
• UDDI yellow pages category contains:
• More details about the company, and includes descriptions of the kind
of electronic capabilities the company can offer to anyone who wants
to do business with it.
• It uses commonly accepted industrial categorization schemes, industry
codes, product codes, business identification cod es and the like to
make it easier for companies to search through the listings and find
exactly what they want.
13

14. Green Pages
• UDDI green pages contain technical information about a web service.
• This includes:
• The various interfaces;
• The URL locations;
• Discovery information and similar data required to find and r un 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 web page or email address all the way up to SOAP, CORBA,
and Java RMI services.
14

15. 15
Key Functional Concepts in the UDDI Specification
• UDDI describes a registry of Web services and programmatic
interfaces for publishing, retrieving, and managing information about
services.
• The UDDI specification defines services that support the description
and discovery of
1. businesses, organizations, and other Web services providers,
2. the Web services they make available, and
3. the technical interfaces which may be used to access and manage those
services.
• UDDI is based upon several other established industry standards,
including
– HTTP, XML, XML Schema, SOAP and WSDL.

16. Key Functional Concepts
• UDDI data mode
• business Service, business Entity, binding Template, tModels
(metadata)
• Hierarchy of registry instances
• Nodes, registries, affiliated registries
• Key programmatic interfaces
• Publish, search, replicate, subscribe, key management,
authentication
• Multiple, flexible service taxonomies
uddi 16

17. UDDI describes four core types of information
• UDDI describes four core types of information:
– business Entity
• A business or organization providing services.
• White page.
– business Service
• Services provided by an organization.
• Support classification using various taxonomy systems.
• Yellow page.
– binding Template
• Technical information necessary to access a service.
• Green page.
– tModel (Technical Model)
• Descriptions and pointers to a reusable concept, external technical
specifications or taxonomies.
• E.g., Web service type, a protocol used by Web services, a category
system.
17

18. Overview of UDDI Registry
18

19. 19
Defining UDDI Nodes, Registries, and Affiliated
Registries
• The UDDI specification includes a specific definition of the hierarchical
relationship between a single instance of a UDDI implementation and others
to which it is related.
• Three major classifications of UDDI servers:
– A node is a UDDI server that supports at least the minimum set of functionality
defined in the specification.
• It may perform one or more functions on the UDDI data to which it has access.
• It is a member of exactly one UDDI registry.
– A registry is composed of one or more nodes.
• A registry performs the complete set of functionality as defined in the specification.
– Affiliated Registries are individual UDDI registries that implement policy-based
sharing of information among them.
• The affiliated registries share a common namespace for UDDI keys that uniquely identify
data records.

20. 20
Essential Programmatic Interfaces in UDDI
• Application programming interfaces
– Publishing information about a service to a registry
– Searching a UDDI registry for information about a service
• These inquiry and publishing functions represent the core data management
tools of a registry.
• Multiple registries may form a group, known as an affiliation, to permit
policy-based copying of core data structures among them.
• Some of the most important concepts that support registry interaction include:
– Replicating and transferring custody of data about a service
– Registration key generation and management
– Registration subscription API set
– Security and authorization
• These functions are divided into Node API Set (server) and Client API Set
(Client).