UDDI Project Introduction

1
UDDI Project Introduction

• Christopher Kurt
• Group Program Manager UDDI Web Services
• General Program Manager uddi.org
• Business Applications Division
• Microsoft Corporation

2
Standardization Creates Growth

• Successful commerce models require consistency
• Examples abound
• U.S. Railroads in the 1880s
• Long Distance Telephone in the 1960s
• Internet in the 1990s
• Web Services today

3
A Simple View of Web Services

• Whats a web service?
• A provider of information or capabilities exposed
  on a network through a consistent set of
  interfaces and protocols
• Typically
• Lightweight/Medium Grained
• Request/Response Messages
• Targeted Functionality
• Always
• Completely independent of service consumer

4
A Simple View of Web Services

• Flexibility
• Independent of development language, technology,
  or platform
• Designed to support heterogeneous environment
  seamlessly
• XML and SOAP are key standards
• Other protocols can be used as well
• Efficiency
• Focus on automation of development and deployment

5
Web Service Challenges

• Who provides web services?
• How are they implemented?
• Where are they exposed?
• What is their behavior?
• Is an application compatible?
• What are they for?
• ... searching and indexing is broken
• (find the right services at the right time)

6
What is UDDI?

• Universal Description Discovery and Integration
• Industry-wide initiative supporting web services
• Specifications
• Schemas for service description
• Schemas for business (service implementers)
  description
• Developed on industry standards (XML, HTTP,
  TCP/IP, SOAP)
• Applies equally to XML and non-XML web services
• Implementation
• Public web service registry and development
  resources

7
Industry-Wide Project Support

• All major technology providers
• Global corporations
• Strong resource and product commitment
• Roadmap for transition to standards body
• Unprecedented collaboration
• XML and Web Services recognized as core standards
• Competition on services built on a common model
• Technology, platform, and development language
  neutral

8
What Problems Do We Solve?
9
Foundation for Web Services
Publish, Find, Use Services UDDI
Formal Service Descriptions WSDL
Service Interactions SOAP
Universal Data Format XML
Ubiquitous Communications Internet
Simple, Open, Broad Industry Support
10
UDDI Registry Entries

• Entities register published informationabout
  themselves
• Standards Bodies, Programmers, Publishers
  register information about their Service Types
  (specs)

11

• Business name
• General business description
• Any number of languages
• Contact info
• Names, phone numbers, fax numbers, web sites,
  etc.
• Known identifiers
• List of unique identifiers for a business
• D-U-N-S, Thomas, domain name, stock ticker
  symbol, other

12

• Business categories
• 3 standard taxonomies in V1
• Industry NAICS (Industry codes - US Govt.)
• Product/Services UN/SPSC (ECMA)
• Location Geographical taxonomy (ISO 3166)
• more in upcoming releases
• Implemented as name-value pairs to allow any
  valid taxonomy identifier to be attached to the
  business white page

13

• New set of information businesses use to describe
  how to do e-commerce with them
• Nested model
• Business process (functional)
• Service specifications (technical)
• Binding information (implementation)
• Programming/platform/implementation agnostic
• Services can also be categorized

14
How UDDI Works
1.
Software companies, standards bodies, and
developers populate the registry with
descriptions (specifications) of types of services
Marketplaces, search engines, and business
applications query the registry to discover
services at other companies and to facilitate
integration
4.
2.
UDDI Registry
Service Types
Implementations
5.
Implementers populate the registry
with descriptions of their businesses and the
services they expose
Large businesses apply the same architecture and
technologies internally
15
Public Registry Operation

• Peer registry nodes (websites)
• Information registeredwith any node
• Registrations replicatedon a daily basis
• Complete set ofregistered recordsavailable at
  all nodes
• Common set ofSOAP APIs supportedby all nodes
• Compliance enforced by business contract
• All technologies applied
• Interoperability verified constantly

queries
IBM
Ariba
other
UDDI.org
other
Microsoft
16
UDDI Roadmap
Ongoing
March 2001
September 2000
December 2001
Industry StandardsBody
17
More Information

• UDDI Resources
• http//uddi.org
• http//uddi.microsoft.com
• Public discussions and mailing lists at
  www.yahoogroups.com
• For Developers
• SOAP/Web Services SDK
• msdn.microsoft.com/xml/general/soap1and2.asp
• VB6 UDDI SDK
• www.microsoft.com/downloads/release.asp?ReleaseID
  24822
• Test Site test.uddi.microsoft.com
• ckurt_at_microsoft.com