1 UDDI (Universal Description, Discovery and Integration)
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
UDDI
(Universal Description, Discovery and Integration)
2
Agenda ● What is and Why UDDI?● UDDI Data Types and their structural
relationship● UDDI Categorization● UDDI Programming model● UDDI over SOAP● Authoring Steps of WSDL, UDDI● Discovery, Binding and Invocation of a Service● Issues of UDDI● Java API for UDDI● UDDI 3.0 & Future of UDDI
3
What is and Why UDDI?
4
Service Architecture
ServiceRegistry
ServiceProvider
ServiceConsumer
Publish Bind
Discover
UDDI defines a scheme to publish and discover information about Web services.
5
What is UDDI?● Programmatic registration and discovery
of business entities and their Web services
● Based on SOAP, HTTP, XML● Registry data– Business registrations– Service type definitions
6
Registry Data
Service TypeDefinitions
(Meta information onWSDL documents)
BusinessRegistrations
Created by businesses
Created by standardorganizations, industryconsortium
7
Business Registration Data● “White pages”
– address, contact, and known identifiers● “Yellow pages”
– industrial categorizations● Industry: NAICS (Industry codes - US Govt.)● Product/Services: UN/SPSC (ECMA)● Location: Geographical taxonomy
• “Green pages”– technical information about services
8
What uses UDDI?
• Tool building client (Service Consumer)– Browse or search registry– Create a service proxy
• Tool publishing the service – Generates WSDL– Construct UDDI entries
• Application that needs dynamic binding – Directly access UDDI– Query can be pre-generated
9
Why UDDI or something like UDDI?• Platform independent service
publication and discovery • Enables dynamic service discovery
10
UDDI Adoption Phases
• Phase 1: Experimental stage• Phase 2: Private UDDI registry within an
intranet (where we are today)• Phase 3: Public UDDI registries with no
coordination among them• Phase 4: Public UDDI registries with
coordination (i.e. replication)• Phase 5: Value added registry services
11
Possible UDDI Topology
Private instances provideboth a layer above the public UDDI, and private registration for industry-based or use-based categorization and for net market makers.
Selective pointers to public UDDI data
Pointers to hosted servicesPrivate UDDI Public UDDI
12
UDDI Data Types & Their Hierarchical
Relationship
13
UDDI Data Types
BusinessEntity
BusinessService
BindingTemplate
BindingTemplate
Tmodel
● Business Entity– White Pages information
● Business Services– Yellow Pages information
● Binding Templates– Green Pages information– Contains references to
tModels● tModels
– Service Type Definitions – Contains references to
WSDL documents
Tmodel
14
Business Entity Data Type
businessEntitybusinessKeynameURLdescriptioncontactsbusinessServicesidentifierBagcategoryBag
PhoneAddressEmail
Contact
businessService
PhoneAddressE-mail
Contact
businessServiceserviceKeyNameDescriptionBindingTemplates
keyedReferencetModelKeykeyNamekeyValue
keyedReferencetModelKeykeyNamekeyValue
keyedReferencetModelKeykeyNamekeyValue
keyedReferencetModelKeykeyNamekeyValue
● Top-level data structure that holds descriptive information about a business entity
● Service descriptions and technical information are expressed within a businessEntity
● Contains categoryBag
15
BusinessService<businessService businessKey="..." serviceKey="..."> <name>StockQuoteService</name> <description> (...) </description> <bindingTemplates> (...) <bindingTemplate> (...) <accessPoint urlType="http"> http://example.com/stockquote </accessPoint> <tModelnstanceDetails> <tModelnstanceInfo tModelKey="..."> </tModelnstanceInfo> <tModelnstanceDetails> </bindingTemplate> </bindingTemplates> </businessService>
● Represents the business services provided by the businessEntity
● Unique key used to represent a service
● Name of the service
● Contains BindingTemplate structures
16
BindingTemplate<businessService businessKey="..." serviceKey="..."> <name>StockQuoteService</name> <description> (...) </description> <bindingTemplates> (...) <bindingTemplate> (...) <accessPoint urlType="http"> http://example.com/stockquote </accessPoint> <tModelnstanceDetails> <tModelnstanceInfo tModelKey="..."> </tModelnstanceInfo> <tModelnstanceDetails> </bindingTemplate> </bindingTemplates> </businessService>
● Specifies Network endpoint address
● Contains a reference to a tModel
17
tModel● Service type definition● Is expected to be created by industry
consortium (as opposed to business entities)– Business entities create businessEntity's,
businessService's, and bindingTemplate's● Shared by business entities● Has a reference to WSDL document ● Enables quick search of all “business
entities” which supports a particular service● Contains categoryBag
18
tModel Example<tModel authorizedName="..." operator="..." tModelKey="..."> <name>StockQuote Service</name> <description xml:lang="en"> WSDL description of a standard stock quote service interface </description> <overviewDoc> <description xml:lang="en"> WSDL source document. </description> <overviewURL> http://stockquote-definitions/stq.wsdl </overviewURL> </overviewDoc> <categoryBag> <keyedReference tModelKey="UUID:..." keyName="uddi-org:types" keyValue="wsdlSpec"/> </categoryBag> </tModel>
19
categoryBag Element● Allows businessEntity, businessService and
tModel structures to be categorized according to any of several available taxonomy based classification scheme
20
identifierBag Element● Allows businessEntity or tModel structures
to include information about common forms of identification such as D-U-N-S numbers, tax identifiers, etc.
● Can be used to signify the identity of the businessEntity, or can be used to signify the identity of the publishing party
● Enhances the search behaviors exposed via the find_xx
21
Registry Data
Service TypeDefinitions
(Meta information onWSDL documents)
BusinessRegistrations
Created by businesses
Created by standardorganizations, industryconsortium
businessEntity'sbusinessService'sbindingTemplate's
tModel's
22
UN/SPCNAICS
DUNS NumbersThomas Registry ID
Rosetta-NetBASDA
Simple.BuySchemas,Interchange specification
Information ModelWeb Service
Web Service
businessEntitybusinessEntitybusinessEntitybusinessServicebusinessService
bindingTemplatebindingTemplateInstanceDetailsInstanceDetails
categoryBagkeyedReferencekeyedReference
identifierBagkeyedReferencekeyedReference
tModels
23
UDDI
Categorization
24
Categorization● NAICS (Industry code)● UNSPAC● D-U-N-S● ISO 3166● SIC
25
UDDI Programming Interface
26
Publishing Services• Publishers interface
– 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
4 messages to save each of the 4 structures
● Each save message accepts as input the authToken and one or more corresponding structures.
4 messages to delete each of the 4 core structures
● They all accept the corresponding uuid key as the parameter.
Security:● request an authentication token ● inform registry that the authToken is
no longer valid.
27
Programmer's API:Service Discovery
• Inquiry interface– Find things
• Find_business• Find_service• find_binding• find_tModel
– Get details• Get_businessDetail• get_serviceDetail• get_bindingDetail• Get_tModelDetail
• Taxonomy interface• validate_categorization
• Browse– 4 messages to find
each of the 4 structures• Drill-down
– The get call can be used to get information regarding a specific instance of any of the 4 data types, given the key
28
UDDI over SOAP
29
UDDI Runs “Over” SOAP
User UDDI
SOAP Request
UDDISOAP Response
UDDI RegistryNode
HTTPServer
SOAPProcessor
UDDIRegistry Service
B2B DirectoryCreate, View, Update, and Deleteregistrations Platform-neutral
30
SOAP Message Example for get_serviceDetail request<Envelope> <Body> <get_serviceDetail generic="1.0"> <serviceKey>6FD77EF6-E7D6-6FF6-1E41-EBC80107D7B5 </serviceKey> </get_serviceDetail> </Body></Envelope>
31
SOAP Message Example for get_serviceDetail response<Envelope> <Body> <serviceDetail generic="1.0" operator="XMethods"> <businessService serviceKey="6FD77EF6-E7D6-6FF6-1E41-EBC80107D7B5" businessKey="D1387DB1-CA06-24F8-46C4-86B5D895CA26"> <name>Currency Exchange Rate</name> <description>Endpoint for service</description> <description>IMPLEMENTATION: glue</description> <description>CONTACT EMAIL: [email protected]</description> <bindingTemplates> <bindingTemplate bindingKey="0036DEBC-2F1B-EB84-09E2-3A4332C3E8B4" serviceKey="6FD77EF6-E7D6-6FF6-1E41-EBC80107D7B5"> <description>SOAP binding</description> <accessPoint URLType="http">http://services.xmethods.net:80/soap</accessPoint> <tModelInstanceDetails> <tModelInstanceInfo tModelKey="uuid:D784C184-99B2-DA25-ED45-
3665D11A12E5"/> </tModelInstanceDetails> </bindingTemplate> </bindingTemplates> </businessService> </serviceDetail> </Body></Envelope>
32
UDDI and WSDLHow They Are
Related
33
UDDI, WSDL Relationships
URL ref
tModelbindingTemplatebusinessService
WSDL
Instance Interface
Network endpointinformation Details of
accessingthe service
UDDI
34
<definitions name=“StockQuoteService” targetNamespace=“http://...”>
<import namespace=“http://...”location=“http://...”>
<service name=“StockQuoteService”>
<port name=“SingleSymbolService” binding=“iface:SingleSymbolBinding”>
...</service>
</definitions>
WSDL Service Implementation
<businessEntity businessKey=“...”><name>Stock Quote Service, Inc.</name>...
<businessService serviceKey=“...”<name>StockQuoteService</name>...<bindingTemplates>
<bindingTemplate bindingKey=“...”>...
<tModelInstanceInfo tModelKey=“...”>...<overviewDoc>
<overviewURL>http://.../SQS.wsdl
</overviewURL>...
</bindingTemplates></businessService>
</businessEntity><definitions name=“StockQuoteService-interface” targetNamespace=“http://...” >
<message name=“SingleQuoteRequest”></message>...
<portType name=“SingleSymbolService”></portType>...
<binding name=“SingleSymbolBinding”type=“tns:SingleSymbolService”>
...</binding>
</definitions>
WSDL Service Interface
UDDI Registry
<tModel tModelKey=“...”><name>http://...</name><overviewDoc><overviewURL>
http://.../SQS-interface.wsdl</overviewURL>
</overviewDoc><categoryBag><keyedReference tModelKey=“...”
keyName=“uddi-org:types”keyValuee=“wsdlSpec”/>
</categoryBag> </tModel>
35
Authoring Steps of WSDL & UDDI
36
Steps that could be Performed by Industry Consortium ● Create WSDL document that contains
abstract part of service definition (WSDL interface definition)
● Create tModel that – makes a URL reference to WSDL interface
definition– includes category information– can be shared by many business entities
● Register the tModel to UDDI registry
37
Steps that are performed by Business entities● Find tModel for a particular service to offer
from the UDDI registry● Determine the port address● Create bindingTemplate that – contains the port address– makes a reference to the previously found
tModel● Create businessService that refers to the
bindingTemplate● Create businessEntity if necessary
38
Discovery, Binding
and Invocation of a Service
39
Discovery of a Service● Programmatically– via Categorization (Yellow paging)– via identity information (White paging)– via Drill-down – via name patterns
● Through UDDI Browser
40
Binding to and Invocation of a Service● Obtain WSDL interface information from the
tModel● Obtaining port address from bindingTemplate● Construct WSDL instance definition (WSDL
document with concrete binding and port address)
● Create service proxy from WSDL● Invocation pattern– Cache the bindingTemplate info for a service– If call to web service fails, re-check info in UDDI
41
Issues and Current Status of UDDI
42
Issues of UDDI● How do you know if the data you get is
valid, legitimate, and up to date?● How do you measure quality of data?● How do you make sure only the qualified
entities register their service information (authentication)?
● How do you provide access control to the data in the registry?
● How do you synchronize the data in multi-registry environment?
43
Current Status of UDDI● No production-quality deployment and
usage in a public domain– Only experimental UDDI servers are present
● Limited usage within an Intranet
44
Java API for UDDI
45
JSR 93: Java™ API for XML Registries (JAXR)● API to expose heterogeneous and
distributed XML registries:– ebXML, UDDI, …– Publish, subscribe, query, associate…
● Web service metadata● Schemas● Business processes● Documents
46
JUDDI
● Open source implementation of UDDI V2● Runs over any Servlet 2.3 compliant
container
47
UDDI 3.0 andFuture of UDDI
48
UDDI 3.0 from OASIS
● Digital signature● Publisher assigned key– Maintains the same key when copy a UDDI
entry from one UDDI registry to another● Multi-registry support● DNS style key format (instead of UUID
format)● Policy
49
Resources
50
Resources● OASIS UDDI TC
– http://www.oasis-open.org/committees/uddi-spec/
● UDDI– www.uddi.org
● UDDI server from Java Web Services Development Pack– http://java.sun.com/webservices/downloads/we
bservicespack.html● Example UDDI Browser from Java Web Services
Development Pack– http://java.sun.com/webservices/downloads/we
bservicespack.html
51
Resources● Using UDDI WSDL in a UDDI Registry (UDDI
Working Draft Best Practice Document)– http://www.uddi.org/pubs/wsdlbestpractices-
V1.05-Open-20010625.pdf
Related Documents
