universal description discovery and integration uddi
Download
Skip this Video
Download Presentation
Universal Description, Discovery and Integration (UDDI)

Loading in 2 Seconds...

play fullscreen
1 / 31

Universal Description, Discovery and Integration (UDDI) - PowerPoint PPT Presentation


  • 1040 Views
  • Uploaded on

Universal Description, Discovery and Integration (UDDI). Chris Peiris Systems Architect www.chrispeiris.com Chris\[email protected] What we cover . Evolution of UDDI What are Web Services ? What is UDDI? UDDI impact on B2B and B2C markets. What problems does it address?

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Universal Description, Discovery and Integration (UDDI)' - alexia


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
universal description discovery and integration uddi

Universal Description, Discovery and Integration (UDDI)

Chris Peiris

Systems Architect

www.chrispeiris.com

[email protected]

what we cover
What we cover
  • Evolution of UDDI
      • What are Web Services ?
      • What is UDDI?
  • UDDI impact on B2B and B2C markets.
      • What problems does it address?
      • Misconceptions on UDDI
  • UDDI Specification
      • Data Structures
      • API
  • UDDI Registries
  • Questions

©Chris Peiris (www.chrispeiris.com)

uddi prerequisites
UDDI Prerequisites
  • HTTP and XML
  • E-Business Model
      • B2B (Business to Business)
      • B2C (Business to Consumer)
  • SOAP (Simple Object Access Protocol)
      • Remote Function Calls over the internet
      • Using web port (80)
  • Web Services
  • WSDL (Web Service Description Language)

©Chris Peiris (www.chrispeiris.com)

web services
Web Services
  • Web services are applications that can be published, located, and dynamically invoked across the Web.
  • Web services perform functions ranging from simple requests to complicated business processes.
  • Once a Web service is deployed, other applications and other Web services can discover and invoke the deployed service.

©Chris Peiris (www.chrispeiris.com)

slide5
WSDL
  • Web Service Description Language
  • Describes a web service in XML format
  • Created by merging two distinct approaches to web service definitions
      • SCL by Microsoft (Service Contract Language )
      • NASSL by IBM (Network Accessible Service Specification Language )
  • WSDL Provides
      • A contract for interoperability (such as a API)
      • A list of services offered.
      • A list of ports for each service which acts as access points.
  • WSDL works over multiple protocols (ex:- HTTP, MIME)

©Chris Peiris (www.chrispeiris.com)

slide6
Now we know

What Web Services are

What WSDL does

How do we search web services

Use a directory of web services

www.xmethods.com

Some Practical Questions

What Web Services does a given company offer?

What Web Services, categorized as accounting is offered today?

Who do I need to contact about using my company’s Web Service?

What are the Web Services available for Melbourne Metro area regarding the health care industry?

What are the implementation details of particular Web Services?

What companies have written implementation around one of these interfaces?

©Chris Peiris (www.chrispeiris.com)

what is uddi
What is UDDI?
  • Universal Description, Discovery, and Integration
  • Public registry design to house information about businesses and their services in a structured way.
  • UDDI will speed up interoperability and adoption for web services
    • Standards-based specifications for service description and discovery
    • Shared operation of a business registry on the web
  • Partnership among industry and business leaders (~ 280 organisations, Microsoft, IBM, Sun, Oracle, Compaq, HP, Intel, SAP etc) - Gartner

(www.uddi.org)

©Chris Peiris (www.chrispeiris.com)

slide8
Web services technology stack- based on standards

Core

Emerging

©Chris Peiris (www.chrispeiris.com)

the evolution of uddi
The evolution of UDDI
  • Naturally “evolved”
    • Ariba and IBM collaboration around B2B
    • IBM and Microsoft collaboration around XML and SOAP
    • Microsoft and Ariba collaboration around BizTalk and cXML
  • 6 months, ~50 meetings

(www.uddi.org)

©Chris Peiris (www.chrispeiris.com)

slide10
A mid-sized manufacturer needs to create 400 online relationships with customers, each with their own set of standard and protocols

BroaderB2B

Describe Services

A flower shop in Australia wants to be “plugged in” to every marketplace in the world, but doesn’t know how

Discover Services

Smarter

Search

IntegrateThemTogether

(www.uddi.org)

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

Easier

Aggregation

What Problems Do We Solve?

©Chris Peiris (www.chrispeiris.com)

slide11
4.

Marketplaces, search engines, and business apps query the registry to discover services at other companies

2.

5.

BusinessRegistrations

Businesses populate the registry with

descriptions of the services they support

Business uses this data to facilitate easier integration with each other over the Web (www.uddi.org)

3.

UBR assigns a programmatically unique identifier to each service and business registration

How UDDI Works

1.

SW companies, standards bodies, and programmers populate the registry with

descriptions of different types of services

UDDI BusinessRegistry

Service Type

Registrations

©Chris Peiris (www.chrispeiris.com)

misconceptions on uddi
Misconceptions on UDDI
  • UDDI is a registry not a repository
      • Links to out side repository, does not store data locally.
      • Not a web services database.
  • Not a new feature in .NET
      • The concept is been around for a while (ebXML implementations, HP E-Speak).
      • MS .NET has made the web service creation easier and UDDI technology has emerged as a result

©Chris Peiris (www.chrispeiris.com)

slide13
Registry Data

WhitePages

  • Businesses register public informationabout themselves
  • Standards bodies, Programmers, Businesses register information about their Service Types

YellowPages

GreenPages

Service Type

Registrations

©Chris Peiris (www.chrispeiris.com)

slide14
White Pages
  • Business Name
  • Text Description
    • list of multi-language text strings
  • Contact info
    • names, phone numbers, fax numbers, web sites…
  • Known Identifiers
    • list of identifiers that a business may be known by – D-U-N-S (UDDI registry generated unique number for each business)

©Chris Peiris (www.chrispeiris.com)

slide15
Yellow Pages
  • Business categories
    • 5 standard taxonomies in Version 2.0
      • Industry: NAICS (Industry codes - US Govt.)
      • Product/Services: Standard Industrial Classification, USPSC
      • Location: Geographical taxonomy (GGC, ISOGT)
    • Implemented as name-value pairs to allow any valid taxonomy identifier to be attached to the business white page

©Chris Peiris (www.chrispeiris.com)

slide16
Green Pages
  • New set of information businesses use to describe how to “do e-commerce” with them
    • Nested model
      • Business processes
      • Service descriptions
      • Binding information
    • Programming/platform/implementation independent
    • Services can also be categorized

©Chris Peiris (www.chrispeiris.com)

web service search mechanism
Web Service Client

Web Browser

Windows application

WAP Mobile Phone

PDA

Web Service

Any platform (Windows, Java, Unix etc …)

Web Service Search Mechanism

©Chris Peiris (www.chrispeiris.com)

uddi data structures
UDDI Data Structures
  • All XML based
  • API implementations
      • Inquire
      • Publish
  • Close to 15 structures
  • Main Data Structures
      • businessEntity
      • serviceEntity
      • tModel
      • bindingTemplate

©Chris Peiris (www.chrispeiris.com)

slide19
tModel (Abstract)
  • Abbreviation for “Technology Model”
  • Represents technical fingerprints, interfaces and abstract types of meta-data.
  • Binding templates are the concrete implementation of one or more tModels.
  • Inside a binding template, one registers the access point for a particular implementation of a tModel

bindingTemplate (Implementation)

  • The information about invoking a web service is documented in a XML structure called bindingTemplate
    • Are they in a specific XML format geared towards online transactions? (Ex :- OBI , Open Buying on Internet)
    • What are the required security implications to access purchase orders?

©Chris Peiris (www.chrispeiris.com)

wsdl and uddi
WSDL and UDDI
  • WSDL
      • Implementation :- Ports
      • Abstract :- Service descriptions
  • UDDI
      • Implementation :- bindingTemplate
      • Abstract :- tModel
  • Both protocols clearly differentiate between Implementation and Abstraction. This is to stand the test of time with new technology.

©Chris Peiris (www.chrispeiris.com)

slide21
Registry APIs (SOAP Messages)
  • Publishers API
    • Save things
      • save_business
      • save_service
      • save_binding
      • save_tModel
    • Delete things
      • delete_business
      • delete_service
      • delete_binding
      • delete_tModel
    • security…
      • get_authToken
      • discard_authToken
  • Inquiry API
    • Find things
      • find_business
      • find_service
      • find_binding
      • find_tModel
    • Get Details about things
      • get_businessDetail
      • get_serviceDetail
      • get_bindingDetail
      • get_tModelDetail

©Chris Peiris (www.chrispeiris.com)

sample soap uddi call
Sample SOAP UDDI Call

Microsoft

©Chris Peiris (www.chrispeiris.com)

slide23
UDDI and SOAP

UDDI RegistryNode

User

UDDISOAP Request

HTTPServer

SOAPProcessor

UDDISOAP Response

UDDIRegistry Service

B2B Directory

Create, View, Update, and Deleteregistrations

Implementation-neutral

©Chris Peiris (www.chrispeiris.com)

uddi toolkits
UDDI Toolkits

Microsoft UDDI SDK v1.5.2 (http://www.microsoft.com/downloads/release.asp?ReleaseID=30880)

Sun Java API for XML Registries (JAXR) including UDDI (http://java.sun.com/xml/jaxr/index.html)

IBM WebSphere UDDI Registry (http://www7b.boulder.ibm.com/wsdd/downloads/UDDIregistry.html)

JUDDI - 3rd Party UDDI SDK – built on Java Implementation (http://www.juddi.org)

©Chris Peiris (www.chrispeiris.com)

slide25
Registry Operation
  • Peer nodes (websites)
  • Companies registerwith any node
  • Registrations replicatedon a daily basis
  • Complete set of“registered” recordsavailable at all nodes
  • Common set ofSOAP APIs supportedby all nodes
  • Compliance enforced bybusiness contract

queries

IBM

HP

other

UDDI.org

Ariba

Microsoft

©Chris Peiris (www.chrispeiris.com)

uddi registries
UDDI Registries

Operational UDDI Servers

  • http://uddi.microsoft.com/default.aspx (Microsoft)
      • Entirely written in C#
      • .Net beta 2 Common Language Runtime.
      • Leverages SOAP access and XML serialization by using .NET System classes.
      • SQL Server 2000 as data store.
  • http://www-3.ibm.com/services/uddi/find (IBM)

Test UDDI Servers

  • http://test.uddi.microsoft.com (Microsoft)
  • http://www-3.ibm.com/services/uddi/testregistry/index.html (IBM)

©Chris Peiris (www.chrispeiris.com)

uddi impact on business
UDDI impact on Business
  • B2B
    • Electronic Procurement process
        • Order matching
          • Catalog browsing and Auction methods could be avoided
    • Advertise our web services.
  • B2C
    • Myriad of opportunities for software vendors
      • Use MS Passport service to lookup user details to register software licenses.

©Chris Peiris (www.chrispeiris.com)

future of uddi
Future of UDDI
  • Version 3.0 is to be released December, 2001
  • Integrated into future .Net servers
      • UDDI support in office XP SDK
      • Integrated into Windows XP as a service
      • BizTalk 3.0 (Bizet) will be WSDL compliant
  • The number of participating companies (public UDDI nodes) are growing
  • UDDI implementation will be 3rd party software business venture.ex:- Sirvisetti Systems (Similar to web hosting sub set of IT.)

©Chris Peiris (www.chrispeiris.com)

slide29
E-Business GrowthSource: McCall T. quoting Shu L. (2001) Worldwide Business-to-Business Internet Commerce to Reach $8.5 Trillion in 2005. The Gartner Group. Available: www.gartner.com.

©Chris Peiris (www.chrispeiris.com)

references
References
  • .Net web Services by Wrox Press (http://www.wrox.com/Books/Book_Details.asp?section=1_2&isbn=1861004397&subject=&subject_id=)
  • he best web source is http://www.uddi.org
  • UDDI Programmer’s specification 2.0 (http://www.uddi.org/pubs/ProgrammersAPI-V2.00-Open-20010608.pdf)
  • UDDI Executive White Paper 2.0 (http://www.uddi.org/pubs/UDDI_Executive_White_Paper.pdf)
  • UDDI Technical White Paper 2.0 (http://www.uddi.org/pubs/Iru_UDDI_Technical_White_Paper.pdf)
  • UDDI Data Structure Specification (http://www.uddi.org/pubs/DataStructure-V2.00-Open-20010608.pdf)
  • Microsoft UDDI Developer Site (http://uddi.microsoft.com/developer/default.aspx)
  • Alphaworks web site (http://www.alphaworks.ibm.com/)
  • Sun UDDI implementation (http://www.sun.com/software/xml/developers/uddi/)

©Chris Peiris (www.chrispeiris.com)

questions
Questions?????

©Chris Peiris (www.chrispeiris.com)

ad