05 Using Uddi

Using UDDI
Susanne Rothaug
SAP AG 2004 / Susanne Rothaug / Using UDDI
Obj ec t i ves
Af t er c ompl et i ng t hi s sessi on, you w i l l be abl e t o:
Describe the basic principles of UDDI
Configure your own UDDI server in SAP Web AS
Publish a Web service in a UDDI registry
Discover a Web service in a UDDI registry
UDDI is
A specification for service description and discovery
The shared operation of a business registry
With strong industry support
Even competitors are working jointly together
Usi ng UDDI : Over vi ew - 1 -
UDDI Business Registry
A shared Operation of a public,
global and free of charge Business
Registry on the Internet
IBM
Microsoft
SAP
other
UDDI
Business
Registry
UDDI Specification
The Specification for
interacting with
Web Service Registries
UDDI Technical Committee
Partnership among Industry
and Business Leaders
A Service Directory shows the service providers and the servicesthey offer.
A Service Provider describes their business and the services they offer by publishing this information to
the Service Directory.
A Service Requestor searches the Service Directory in order to discover suitable Service Providers and
their services.
Once the Service Provider discovered suitable services, they caninvoke these services at an access point
offered by the Service Provider.
The SAP J 2EE Engine provides full UDDI functionality based on UDDI Specification 2.0. This can be
used for publishing, browsing, and retrieving Web services basedon standard UDDI APIs. You can
publish your Web service and Web service definitions in a public, private, or test registry.
UDDIs Focus
Service Directory
3
Service
Execution
2
Service Requestor
Service
Discovery
Service Provider
1
Service
Publication
The registry is something like an address book where services and their providers are listed. The focus is on
the services, all other information can be used to locate the service.
A UDDI business registry provides three types of information:
White Pages
The white pages are a register that is sorted by provider name. The white pages get their information from
the business entity element, a basic data structure in the UDDI information model. The name, address,
and industry sector of the Web service provider are stored here. The business entity element also
functions as a type of container in which all other information on a Web service is contained. Therefore,
one main prerequisite for the publication of a Web service in a UDDI registry is the availability of a
business entity.
Yellow Pages
The yellow pages are a registry sorted by categories. The service information in the yellow pages is stored
in the business service element. They serve the purpose of sorting services into groups for example, on
the basis of the business processes for which they were conceived. Examples of business processes
include e-business services for purchasing goods.
Green Pages
The green pages contain technical details on services provided. They contain binding templates, that is,
technical data, with the help of which a user can get in contact with a Web service and communicate
with it. This category includes, for example, the Web address under which a service can be reached. The
t-Model element provides even more detailed data a subset of the binding templates. It describes the
specification of the interfaces used by a Web service.
Web service registry
Metadata (business or technical categories) used to find services
E.g. business categories such as
Industry: NAICS
Products/Services: UNSPSC
Location: ISO 3166
E.g. technical categories such as
Interface type: RosettaNet PIP
Protocol: SOAP 1.1
Publication, discovery available via Web services
Usage scenarios
Enterprise service registry
E-Business capabilities in private exchange
WSRP portlet directory
Important terms in the UDDI context:
Business entity Information about the party that publishes information about a family of services.
Contains master data about the business and its contacts, e.g. company X.
Business service Descriptive information about a particular service. Semantically describes the
services offered, e.g. Buy from X.
Binding template Technical information about a service entry point and construction specifications.
Technically describing the various implementations of each business service, e.g.
- Buy from X using fax, number Y
- Buy from X using XML, schema Y, URL Z
tModel Basis for technical fingerprints. Binding template data contains references to tModels. These
tModelsdesignate the interface specifications for a service. tModelscan represent
- Identification systems, e.g. D&B D-U-N-S numbers
- Categorization systems, e.g. UNSPSC
- Service types, i.e. those characteristics that remain same across a variety of business service
implementations, e.g. a RosettaNet PIP
Usi ng UDDI : Gener al Ter mi nol ogy
business
Entity
business
Service
binding
Template
*
*
tModel
ID
*
*
category
*
*
category
*
*
category
*
*
service type
*
*
Who
A businessEntity represents a
Web service provider
What for
A businessService represents a
logical grouping of Web services,
similar to a WSDL service
Where
A bindingTemplate represents a
Web service endpoint, similar to a
WSDL endpoint
What and how
A tModel defines a (reusable) Web
service type, similar to a WSDL
binding or interface
Web User Interface
The user interface for a UDDI server is the UDDI client. It enables you to perform a browser-based search for and
publish data on the UDDI server. You call a UDDI client as follows: http://<host>:<port>/uddiclient
In the <host>field, enter the required host name. In the <port>name, enter 50000. A J2EE engine has been started
and the UDDI server configured (see below) on this application server.
SOAP API
UDDI servers can be operated either manually through the browser or through client programs using Web service
APIs.
To access the data of a UDDI registry, the client software uses SOAP through HTTP. UDDI provides, as a web
service, an inquiry API and a publishing API in accordance with the specifications. The calls for applications
that search through the business registry form the inquiry API. This includes calls such as find_business and
find_service. On the other hand, applications must be in a position to createand change this information. For this
purpose, calls such as save_business and save_service are available. You can use them to create or update
information for a business entity or for a business service.
The following SOAP APIs can be used with the UDDI server.
Inquiry API: http://host:port/uddi/api/inquiry
Publishing API: http(s)://host:port/uddi/api/publish
You can decide in the Visual Administrator on whether to use thepublishing API http or https.
Database
The data of a UDDI registry is usually stored in a relational database. SAP DB is supported as a database instance.
Using a few administrative steps, you can also store data in other databases.
UDDI Logic
The UDDI logic implements the search and publication functions defined in the standard version. The data searched
for using a SOAP API or a Web user interface is read from the database using UDDI logic. Likewise, data is
published and written to the database with the help of the appropriate utilities.
Usi ng UDDI : UDDI Ser ver Ar c hi t ec t ur e
Before you can set up registries you have to preload tModelsand taxonomies. After installation the UDDI
Server database is empty and does not include even the core tModels. To use the UDDI server, you must
reset the database used. UDDI data that was available previouslyis deleted; UDDI core tModelsand
taxonomies are imported.
In the Visual Administrator, choose Web Services Container Runtime UDDI Server. In the General
register, select the checkbox Preload base tModels and taxonomies (UNSPSC, ISO-3166, NAICS, etc)
and choose afterwards Reset DB.
Usi ng UDDI : UDDI Ser ver Pr el oad Tax onomi es
Preload base
tModels and
taxonomies
Create a new registry:
In the Visual Administrator, choose Web Services Container Runtime UDDI Server. Choose New
Registry and enter the name of the registry, the inquiry, and the Publish URL.
Configure the HTTP proxy settings
Select the Settings tab and enter the required proxy host and port information. Choose Save.
Usi ng UDDI : UDDI Ser ver - Set t i ng up Regi st r i es
Create a registry
Configure HTTP
proxy settings
Users and roles play an important part in the publication of newservices in UDDI registries. If you have a
non-public registry, only a selected circle of users should be allowed to make entries in the UDDI
database.
In the Visual Administrator, choose Web Services Container Runtime UDDI Server Users. Enter
the user names and the appropriate levels of authorization.
Usi ng UDDI : UDDI Ser ver - Assi gni ng User s
These are the types of users that can be created.
Usi ng UDDI : UDDI Ser ver - Assi gni ng User s
To publish your service, first you have to create a business entity containing specific information such as
contacts, identifiers, and categories. To perform this action, you have to load the UDDI tool from a
browser window pointing to <host>:<port>/uddiclient. The default is localhost:50000/uddiclient.
Select Publish Business Entity and choose Next
Select a UDDI Registry and enter the user name and password.
A list of already published entities is displayed.
To create a new business entity choose Create Business
Choose Names New Name andenter the name of the business entity
UDDI-specific information for the business entity can be added as names and descriptions of the entity in
various languages, contact persons, identifiers, and categories that are used to identify and classify the
business entity.
Enter the information that you want to be available for this entity and choose Publish.
Usi ng UDDI : Publ i sh a Busi ness Ent i t y
You have to publish the
following objects:
Business entity
tModel
Business service
Call the SAP NetWeaver Developer Studio and choose the Web Service Definition of the service you wish
to publish in the UDDI registry. On the right-hand side, choose the UDDI registry and afterwards Publish.
Identify yourself using the administrator password for the J2EE engine.
Remember that, in the Developer Studio, the host of the UDDI server must be entered under Windows ->
Preferences ->SAP J 2EE Engine.
In the window that is displayed, enter a user name and password for connecting to the SAP J 2EE Engine.
This user name and password are kept until you do restart the Developer Studio or choose Window
Preferences Web Services Reset Upload Username/Password.
If you want the VI and WSD to be automatically uploaded when you change and save them, then choose
Enable Auto upload on save.
Usi ng UDDI : Publ i sh a Web Ser vi c e Def i ni t i on as a t Model -
1
Choose
Publish
WSD
Select the UDDI registry where you want to publish your WSD and enter the user name and password
that you created before.
Enter the name of the tModel that will represent this Web service definition in the Name tab.
The service definition publication page is used to enter specific UDDI information for the WSD before
it is published. If the service definition has already been published, its tModel key is displayed and
buttons for updating or publishing the definition as a new tModel are available.
Enter information in rest of the tabs for specifying your tModel.
Usi ng UDDI : Publ i sh a Web Ser vi c e Def i ni t i on as a t Model -
2
1.
2.
3.
Deploy the Web service to the J 2EE engine.
The tModel is now displayed in the tModel Publications window.
Usi ng UDDI : Publ i sh a Web Ser vi c e Def i ni t i on as a
t Model - 3 -
returned tModel-key
in the Web Service
Definition
Open the Visual Administrator, and choose Web Services Container Runtime Web Services
Select your Web service and choose Publish.
In the displayed dialog window, select a UDDI registry and choose OK.
The SAP J 2EE Engine Visual Administrator starts the UDDI client browser, which guides you step-by-
step through the process of publishing your Web service. The URL that is opened in the UDDI client
browser window contains the fully qualified host name that includes the domain as well. Therefore, if the
client cannot be opened from local computers and if you are using a proxy, include the local domain in the
browser exclude list. If you are using Internet Explorer, chooseTools Internet Options Connections
LAN Settings Advanced Exceptions and enter the local domain name.
Enter the user name and password.
Usi ng UDDI : Publ i sh a Web Ser vi c e as a Busi ness
Ser vi c e - 1
Select a business entity and enter your data about the business service you want to publish.
If the service has already been published, its tModel key is displayed and buttons to update it or publish it
as a new service are available.
You can fill in the following data:
Names in different languages
Descriptions in different languages
Categories used to classify the service
Binding templates
The UDDI-specific information for a binding template consists of: descriptions of the template, the type
and URL of the address point (the target address of the port), and information about the different
instances. A separate screen configures the information about each instance.
Choose Publish to publish your Web service as a business service.
Usi ng UDDI : Publ i sh a Web Ser vi c e as a Busi ness Ser vi c e -
2
The UDDI client provides a Search page for querying the UDDI registries for published tModels, business
entities and Web services, along with all the information provided.
To invoke and use the UDDI Search page, proceed as follows:
Open a browser window and enter http://<host>:<port>/uddiclient on the address bar.
In the window that is displayed, select a language and choose Search Registry.
Select the UDDI registry that you want to query
Depending on what you are searching for, select the corresponding tab TModel, Service, Business Entity.
You can search your component by name, categories, or identifiers. If you are not sure about the name,
use the percent sign (%). For example, if you are looking for a tModel beginning with My but you do
not know the rest of the name, then enter My% and choose Search. In addition, if you enter only %,
this will display you all tModelspublished in the specified registry.
From the list of the components displayed, select one and chooseView.
All information registered in UDDI about this component is displayed.
Usi ng UDDI : Quer yi ng UDDI
Enter your
Search Criterion
Basic principles.
UDDI servers should enable companies to register Web services and to provide them to internal and
external users. A UDDI server can be set up for each J2EE engine. You use a UDDI Server to provide
certain services to a group of appropriately authorized users. You configure a UDDI server by setting up
registries and users for the UDDI server.
You can publish Web Services in a UDDI registry by publishing the tModel in the SAP NetWeaver
Developer Studio and then making the Web service available with the Visual Administrator. It is
imperative that you have published a business entity that contains the general information on the name,
address and business sector of the Web service provider.
Summar y
Now you shoul d be abl e t o:
Describe the basic principles of UDDI
Configure your own UDDI server in SAP Web AS
Publish a Web service in a UDDI registry
Discover a Web service in a UDDI registry

05 Using Uddi

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

05 Using Uddi

Uploaded by

Copyright:

Available Formats

Using UDDI

You might also like