WS-Talk and UDDI Department of Computer Science Royal Holloway, University of London Fionn Murtagh, Pedro Contreras {fionn, cs.rhul.ac.

Size: px

Start display at page:

Download "WS-Talk and UDDI Department of Computer Science Royal Holloway, University of London Fionn Murtagh, Pedro Contreras {fionn, cs.rhul.ac."

Derek Gordon
5 years ago
Views:

1 WS-Talk and UDD Department of Computer Science Royal Holloway, University of London Fionn Murtagh, Pedro Contreras {fionn, cs.rhul.ac.uk UDP

2 ntroduction What s UDD Searches in UDD UDD Distributions and flavours Commercial mplementation vs Open Source JUDD, UDD Browser, UDD4J Discussion WS-Talk and UDD

3 What s UDD Universal Description Discovery and ntegration is de facto standard web services catalogue. t consists of a directory where business can register and search for web services, centred around a WS interface described by a WSDL document. t is based on a set of specifications (OASS standard) with public and private implementations and providing two web services: nquiry : provide functions such as find_business, get_businessdetails Publisher : provide functions such as save_business, delete_business All these operations are based in SOAP messages.

4 Searches in UDD Three can of searches can be performed using UDD registry: White pages search: returns basic information such as address, contact, and identifiers about a company. Yellow pages search: retrieve information according to industrial categorization and taxonomies, such as NACS, SO3166, and UNSPSC Green pages service search: retrieve technical information about Web service, as well as information about how to execute these services.

5 Commercial implementations Acumen Technology, BEA, WebLogic Server UDD Registry Fujitsu, BM, nfravio, ONA, Microsoft, Novell, Oracle, SAP, Select Business Solutions, SOA Software, Sun Microsystems, Java Web Services Developer Pack. Systinet,

6 Open Source mplementations Apache.org, JUDD, Open Source and Platform ndependent Supports for JDK and later UDD version 2.0 compliant implementation Use with any relational database that supports ANS standard SQL (MySQL, DB2, Sybase, JDataStore, HSQLDB, etc.) Deployable on any Java application server that supports the Servlet 2.3 specification (Jakarta Tomcat, JOnAS, WebSphere, WebLogic, Enterprise Server, JRun, etc.) judd registry supports a clustered deployment configuration. Easy integration with existing authentication systems UDD Browser, Still early version but gives a GU to work from the client point of view over different UDD repositories

7 Open Source mplementations APs UDD4J.org, UDD4J contains an implementation of the client side of UDD from which the application needs to publish, find, and to bind a Web service. t also includes the source of the code, the complete JavaDoc documentation, and sample applications. SOAP:LTE, or Collection of Perl modules that provides a simple and lightweight implementation of SOAP, XML-RPC, UDD and other webservice-related spec. PHPUDD, Stand-alone PHP classes with no external dependencies, supporting basic UDD inquiry APs. However, not able to publish documents. Not as relevant as those above.

8 JUDD Methods JUDD AP (proprietary) get_registrynfo find_publisher get_publisherdetail save_publisher delete_publisher JUDD nquiry AP find_business find_service find_binding find_tmodel find_relatedbusinesses get_businessdetail get_businessdetailext get_servicedetail get_bindingdetail get_tmodeldetail JUDD Publish AP get_authtoken get_registerednfo discard_authtoken save_business save_service save_binding save_tmodel delete_business delete_service delete_binding delete_tmodel add_publisherassertions set_publisherassertions get_publisherassertions delete_publisherassertio get_assertionstatusrepo

9 Find_plublisher JUDD Example Query <?xml version="1.0" encoding="utf-8"?> <soapenv:envelope xmlns:soapenv=" <soapenv:body> <find_publisher maxrows="100" generic="1.0" xmlns="urn:juddi-org:api_v1"> <name>***</name> </find_publisher> </soapenv:body> </soapenv:envelope> Results <?xml version="1.0" encoding="utf-8"?><soapenv:envelope xmlns:soapenv=" xmlns:xsd=" xmlns:xsi=" <soapenv:body> <publisherlist generic="1.0" operator="judd.org" xmlns="urn:juddi-org:api_v1"> <publishernfos/> </publisherlist> </soapenv:body> </soapenv:envelope>

10 Populating JUDD server Two methods were tried Produce a piece of source code to insert records like UDD4J or SOAP:LTE. Development effort needed. nsert records directly into the DB using MySQL. The easiest option. DB reverse engineering needed to understand data structure.

11 JUDD BUSNESS_NAM E_D NAM E BUSNESS_NAM E varchar(41) i nteger(11 ) varchar(5) varchar(255) CONTACT_D CONTACT D CONTACT_ va rchar(4 1) in teg er(11) in teg er(11) va rchar(5 ) va rchar(2 55) <pk,fk1,fk2 > <pk,fk2> CONTACT_ D PERSON_NAM E CONTACT varcha r(41) i nteger(1 1) varcha r(255) varcha r(255) DSCOVERY_ URL_D URL DENTFER_ D TMODEL_KEY_REF KEY_VAL UE BUSNESS D CATEGORY_D TMODEL_KEY_REF KEY_VAL UE SERVCE_KEY SERVCE_NAME_D NAM E BNDNG_ KEY CATEGORY_D TMODEL_KEY_REF KEY_VAL UE BNDNG_ KEY BNDNG D BUSNESS_DENTFER BUSNESS_CATEGORY SERVCE_KEY SERVCE D SERVCE_KEY CATEGORY_D TMODEL_KEY_REF KEY_VAL UE DSCOVERY_URL i nte ger(11) BUSNESS_ i nte ger(11) SERVCE_ NAM E BNDNG_ CATEGORY i nte ger(11) BNDNG_ varchar(41) i nteger(11 ) varchar(255) varchar(255) varcha r(41) i nteger(1 1) varcha r(5) varcha r(255) i nte ger(11) varchar(5 ) SERVCE_ varchar(41) i nteger(11 ) varchar(5) varchar(255) SERVCE_ CATEGORY i nte ger(11) varchar(41) integer(11) varchar(5) varchar(255 ) SERVCE_ KEY LAST_ UPDATE AUTHORZED_ NAM E PUBLSHER_D OPERATOR LAST_UPDATE BUSNESS_SERVCE va rchar(41 ) va rchar(41 ) ti m estam p(19) SERVCE_KEY BNDNG_ KEY ACCESS_ PONT_TYPE ACCESS_ PONT_URL HOSTNG_REDRECTOR L AST_UPDATE BUSNESS_ENTTY < fk> < pk> BNDNG_TEM PLATE varchar(2 0) varchar(41 ) varchar(41 ) varchar(20 ) tim estam p(19) varchar(25 5) varchar(25 5) ti m estam p(19) < fk> < pk> <fk> CONTACT_D EMAL_ D EMAL_ ADDRESS CONTACT_D PHONE_ D PHONE_ NUM BER PUBLSHER_ D PUBLSHER_ NAM E EMAL_ ADDRESS S_ADM N S_ENABLED CONTACT_D ADDRESS_D SORT_CODE TMODEL_KEY BNDNG_KEY BNDNG_KEY EM AL varchar(41 ) intege r(11) intege r(11) varchar(25 5) varchar(25 5) <pk,fk1,fk2 > <pk,fk2 > NSTANCE_DETALS_ TMODEL_NSTANCE_NFO_ D NSTANCE_DETALS D NSTANCE_DETALS_DOC_ TM ODEL_NSTANCE_NFO_D NSTANCE_DETAL S_DOC D LANG_CODE PHONE varchar(41 ) intege r(11) intege r(11) varchar(25 5) varchar(50 ) PUBLSHER varch ar(20) varch ar(255 ) varch ar(255 ) varch ar(5) varch ar(5) <pk,fk1,fk2 > <pk,fk2 > < pk> TM ODEL_NSTANCE_NFO_ BNDNG_KEY TMODEL_NSTANCE_NFO_ D TMODEL_NSTANCE_NFO D ADDRESS : 2 varch ar(41) integer(11) integer(11) varch ar(255 ) varch ar(10) varch ar(41) <pk,fk1,fk2> <pk,fk2> <fk3> varch ar(41) i nteger(1 1) i nteger(1 1) varch ar(5) varch ar(255) va rchar(4 1) in teg er(11) in teg er(11) va rchar(5 ) va rchar(41 ) in tege r(11) in tege r(11) va rchar(5) va rchar(25 5) va rchar(2 55) <pk,fk1,fk2 > <pk,fk2> <pk,fk1,fk2 > <pk,fk2 > < pk,fk1,fk2> < pk,fk2> < pk> CONTACT_ D ADDRESS_ D ADDRESS_ LNE_D LNE KEY_VALUE AUTH_TOKEN PUBLSHER_D PUBLSHER_NAME CREATED LAST_USED NUMBER_OF_ USES TOKEN_STATE BUSNESS_ KEY CONTACT_D ADDRESS_D SORT_CODE TM ODEL_KEY ADDRESS_ LNE AUTH_TOKEN varcha r(41) i nteger(11 ) i nteger(11 ) i nteger(11 ) varcha r(80) varcha r(255) varcha r(255) va rchar(51 ) va rchar(20 ) va rchar(25 5) ti m estam p(19) ti m estam p(19) in teg er(11) in teg er(11) ADDRESS : 1 varchar(41) intege r(11) intege r(11) varchar(255 ) varchar(10) varchar(41) <fk> TM ODEL _NSTANCE_NFO BNDNG_KEY TM ODEL _NSTANCE_NFO_D TM ODEL _KEY OVERVEW_ URL NSTANCE_PARM S <pk,fk1,fk2> <pk,fk2> <fk3> varch ar(41) integer(11) varch ar(41) varch ar(255 ) varch ar(255 ) TMODEL_KEY TM ODEL_ KEY AUTHORZED_NAME PUBL SHER_D OPERATOR NAM E OVERVEW_URL DELETED LAST_UPDATE < pk,fk1> < pk> < fk2> TMODEL_KEY TMODEL D TM ODEL TM ODEL _ TMODEL_KEY CATEGORY_D TMODEL_KEY_REF KEY_VAL UE varchar(41) varchar(255) varchar(20) varchar(255) varchar(255) varchar(255) varchar(41 ) intege r(11) varchar(5) varchar(25 5) varchar(5) tim esta mp(19) TM ODEL _DOC_ TMODEL_DOC D TMODEL_KEY varchar(41) integer(11) varchar(5) varchar(255 ) TMODEL_CATEGORY <fk> DENTFER_ D TMODEL_KEY_REF KEY_VAL UE PUBLSHER_ASSERTON FROM _KEY TO_KEY TM ODEL_KEY KEY_NAME KEY_VALUE FROM _CHECK TO_CHECK i nte ger(11) TMODEL_DENTFER i nte ger(11) varchar(5 ) varchar(5 ) <fk>

12 JUDD Data Model BUSNESS_ NAM E_D L ANG_ CODE NAM E BUSNESS_ NAM E <pi > BUSNESS_DENTFER CONTACT D L ANG_ CODE CONTACT_ CONTACT_ D USE_ TYPE PERSON_NAM E CONTACT <pi > TM ODEL _DOC_ TM ODEL _DOC D LANG_CODE < pi> DENTFER_D TM ODEL_ KEY_REF KEY_ NAM E KEY_ VALUE BUSNESS D L ANG_ CODE DSCOVERY_URL_D URL BUSNESS_CATEGORY CATEGORY_D TM ODEL_ KEY_REF KEY_ NAM E KEY_ VAL UE <pi> BUSNESS_ DSCOVERY_URL <pi > <pi > VA41 VA41 AUTHORZED_NAM E OPERATOR LAST_UPDATE BUSNESS_ENTTY < pi> VA4 1 TS PHONE_D PHONE_NUM BER EM AL _D EM AL _ADDRESS PUBLSHER_D PUBLSHER_NAM E EM AL _ADDRESS S_ADM N S_ENABLED PHONE EM AL 0 PUBLSHER < pi> VA2 0 ADDRESS_LNE_D LNE KEY_ NAM E KEY_ VAL UE ADDRESS_LNE AUTH_TOKEN PUBLSHER_NAM E CREATED LAST_USED NUM BER_OF_USES TOKEN_ STATE <pi> AUTH_TOKEN ADDRESS_D SORT_CODE VA80 < pi> 1 TS TS ADDRESS : 1 <pi> VA10 CATEGORY_D TM ODEL _KEY_REF KEY_VAL UE TM ODEL_CATEGORY < M < M SERVCE_ NAM E_D NAM E SERVCE D SERVCE_ NAM E <pi> SERVCE_ SERVCE_KEY LAST_UPDATE BUSNESS_SERVCE VA4 1 TS ADDRESS_D SORT_CODE NSTANCE_ DETALS_ NSTANCE_DETALS D LANG_CODE ADDRESS : 2 <pi> VA10 < pi> TM ODEL_ KEY AUTHORZED_NAM E OPERATOR NAM E OVERVEW_URL DELETED L AST_UPDATE TM ODEL VA41 TS TM ODEL_ DENTFER CATEGORY_D TM ODEL_ KEY_REF KEY_ NAM E KEY_ VALUE BNDNG_CATEGORY CATEGORY_D TM ODEL_ KEY_REF KEY_ NAM E KEY_ VAL UE SERVCE_CATEGORY <pi> <pi > VA41 VA41 BNDNG_ KEY ACCESS_ PONT_TYPE BNDNG_TEM PLATE ACCESS_ PONT_URL HOSTNG_ REDRECTOR L AST_UPDATE <pi > VA41 VA20 TS NSTANCE_ DETALS_DOC_ NSTANCE_ DETALS_DOC D LANG_ CODE <pi > TM ODEL_ NSTANCE_NFO TM ODEL_NSTANCE_NFO_D OVERVEW_URL NSTANCE_ PARM S PUBLSHER_ASSERTON FROM _KEY TO_ KEY KEY_VALUE FROM _CHECK TO_ CHECK DENTFER_D TM ODEL_KEY_ REF KEY_VALUE VA4 1 VA4 1 < pi> BNDNG_ TM ODEL_NSTANCE_ NFO_ TM ODEL_ BNDNG D LANG_CODE TM ODEL_NSTANCE_ NFO D LANG_CODE <pi > TM ODEL D <pi >

13 JUDD Advantages Free and Open Source t works Supports a variety of Data Bases Can be deployed in any Servlet container that supports spec. 2.3 Clustering method can be used to integrate different JUDD

14 JUDD Problems Poor documentation, just an list is available Could be a little tricky to make it work at the beginning. But we got that documented UDD spec. 2 is supported at the moment

15 UDD Browser

16 Open questions Which UDD version? JUDD supports UDD standard version 2, but currently the specification is v. 3. V. 3. Specifies a series of UDD flavours. Corporate/private: internal registry behind a firewall Affiliated: controlled environment where limited access is granted Public: open registry UDD in WS-Talk? Are we going to use a single centralised repository, or a set of distributed ones. The solution for this may be in the use of ActiveBPEL engine. Others issues?

This tutorial has been designed for beginners interested in learning the basic concepts of UDDI.

About the Tutorial is an XML-based standard for describing, publishing, and finding Web services. In this tutorial, you will learn what is and why and how to use it. Audience This tutorial has been designed