Web Services and the UDDI Registry

1
Web Services and the UDDI Registry

• Christopher M. Kurt
• Program Manager www.uddi.org
• Group Program Manager UDDI Web Services
• Business Applications Division - Microsoft

2
Standardization Creates Growth

• Successful e-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 provided?
• What is their behavior?
• Is an application compatible?
• Searching and indexing are do not work today
• how to find the right services at the right
  time?
• we need solutions designed for tools and apps
• our expectations have been lowered by the
  Internet experience today

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?
Describe Services
Discover Services
IntegrateThemTogether
Provide a standards-based profile for all
electronic services that are provided. Includes
web sites, other electronic resources
Publish for Accessibility
Web Service Visibility
9
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
10
UDDI Registry Entries

• Standards Bodies, Agencies, Programmers,
  Publishers register specifications for their
  Service Types
• Service providers register precise information
  about themselves and their Web services

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 base taxonomies in V1
• Industry NAICS (Industry codes - US Govt.)
• Product/Services UNSPSC (ECCMA)
• Location Geographical taxonomy (ISO 3166)
• easy extension in upcoming releases

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

Developers
Applications
Marketplaces
End Users
IBM
queries
other
UDDI.org
HP (planned)
other
Microsoft
16
UDDI Roadmap
Ongoing
March 2001
September 2000
December 2001
Industry StandardsBody
17
More Information

• UDDI Resources
• http//www.uddi.org
• http//uddi.microsoft.com
• http//www-3.ibm.com/services/uddi
• Public discussions and mailing lists at
  www.yahoogroups.com
• For Developers
• SOAP/Web Services SDK
• msdn.microsoft.com/xml/general/soap1and2.asp
• Visual Basic UDDI SDK
• www.microsoft.com/downloads/release.asp?ReleaseID
  24822
• IBM AlphaWorks Web Services Toolkit
• http//www.alphaworks.ibm.com/tech/webservicestool
  kit
• ckurt_at_microsoft.com
• uddi-gpm_at_yahoogroups.com