Web Services and the UDDI Registry by vev19514


									            Web Services and the
               UDDI Registry

Christopher M. Kurt
Program Manager – www.uddi.org

Group Program Manager – UDDI & Web Services
Business Applications Division - Microsoft
Standardization Creates Growth

 Successful
 models require consistency
   Examples  abound
    U.S. Railroads in the 1880s
    Long Distance Telephone
     in the 1960s
    Internet in the 1990s

 Web   Services today
A Simple View of Web Services

 What’s   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
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
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
What is UDDI?
 Universal     Description Discovery and Integration
       Industry-wide initiative supporting web services

 Specifications
     Schemas for service description
     Schemas for business (service implementers)
     Developed on industry standards (XML, HTTP, TCP/IP,
     Applies equally to XML and non-XML web services

   Implementation
       Public web service registry and development
Industry-Wide Project Support
 Allmajor 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
 What Problems Do We Solve?
                An organization needs to
                create 400 electronic
   Broader      relationships with
      B2B       partners, each with its       Describe
                own standards and
                protocols                     Services
                A small business wants to
   Smarter      be “plugged in” to every      Discover
                marketplace in the world,
    Search      but doesn’t know how          Services

                A B2B marketplace cannot      Integrate
     Easier     get catalog data for
                relevant suppliers in its     Them
Aggregation     industry, along with
                connections to shippers,
                insurers, etc.

                Provide a standards-based
Web Service     profile for all electronic    Publish for
                services that are provided.
   Visibility   Includes web sites, other     Accessibility
                electronic resources
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 Registry Entries
   Standards Bodies,
    Agencies, Programmers,
    Publishers register
    specifications for their
    Service Types

   Service providers register
    precise information about
    themselves and their Web
 Business name
 General business description
   Any    number of languages
 Contact    info
   Names,phone numbers,
   fax numbers, web sites, etc.
 Known     identifiers
   Listof unique identifiers for a business
    D-U-N-S, Thomas, domain name, stock
     ticker symbol, other
 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
 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
                             How UDDI Works
                             Software companies, standards
     1.                      bodies, and developers populate
                             the registry with descriptions
                             (specifications) of types of services                   Marketplaces, search engines,
                                                                                     and business applications
                                                                               4.    query the registry to discover
                                                                                     services at other companies
                                                                                     and to facilitate integration
                                          UDDI Registry

                                       Implementations         Service Types
          populate the
                                   UDDI Registry assigns a programmatically unique
          registry with       3.   identifier to each service and registration
          descriptions of
          their businesses
          and the services
          they expose                                                                    Large businesses apply
                                                                                         the same architecture
                                                                                         and technologies
       Public Registry Operation
   Peer registry nodes (websites)         Developers
   Information registered
    with any node                                   Applications
   Registrations replicated                             Marketplaces
    on a daily basis
   Complete set of                                                End Users
                                   IBM               queries
    “registered” records
    available at all nodes
   Common set of
    SOAP APIs supported
    by all nodes             other
   Compliance enforced                                 HP (planned)
    by business contract
   All technologies applied
                                 other      Microsoft
         Interoperability
           verified constantly
UDDI Roadmap
     V1              V2              V3
“Registration”   “Integration”   “Aggregation”    Ongoing

 September          March         December        Industry
   2000             2001            2001         Standards
    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
    Visual Basic UDDI SDK
    IBM AlphaWorks Web Services Toolkit

   ckurt@microsoft.com
   uddi-gpm@yahoogroups.com

To top