UDDI 
Purpose
The SAP J2EE Engine provides full UDDI client functionality based on UDDI Specification 2.0. This can be used for publishing, browsing, and retrieving Web services based on standard UDDI APIs. You can publish your Web service and Web service definitions in a public, private, or test registry.
Implementation Considerations
General UDDI Terminology
· tModel – Description of specifications for services or taxonomies. Basis for technical fingerprints.
· Binding template – Technical information about a service entry point and construction specifications. Binding template data contains references to tModels. These tModels designate the interface specifications for a service.
· Business service – Descriptive information about a particular service.
· Business entity– Information about the party that publishes information about a family of services
Simple UDDI Scenarios
...
· One company publishes a standard in UDDI and the others can find and use the same standard.
For example, a tour office company may offer rooms from several hotels. This company publishes a Web Service Interface in UDDI and each hotel that wants to be represented by this company implements a Web service that extends this Web Service Interface. Later on, after an agreement between both companies, the tour company may use the WSDL of the Hotel Web service to ask for free rooms, book rooms, and so on.
· A published standard Web Service Interface already exists and you want to see who supports it and to choose the one that suits you best.
Prerequisites
· An installed and running SAP J2EE Engine
· Installed SAP Java Cryptographic Toolkit
You can download the package at service.sap.com/download under Downloads ® SAP Cryptographic Software. Further steps are described in the chapter Deploying the SAP Java Cryptographic Toolkit.
· A running sap.com/com.sap.engine.services.webservices.tool application
· A running sap.com/tc~uddiapplication
Both applications are started automatically, when running the J2EE Engine.
· An installed and running SAP NetWeaver Developer Studio (this is not necessary for all scenarios)
· You have knowledge of the SAP NetWeaver Developer Studio and its different projects.
· You know how to create a Web Service Definition, Web service, and a Web service client.
· You have at least basic knowledge of Web Services and UDDI.
Features
The UDDI client is a Web-based tool that is fully integrated in the SAP NetWeaver Developer Studio, enabling you to publish Web Service Definitions. Also, the UDDI client can be started from the SAP J2EE Engine Visual Administrator or simply by pointing the browser to the following URL: http://<host>:<port>/uddiclient
In addition, a UDDI server is shipped with SAP Web AS that implements the OASIS standard: UDDI v2 specifications excluding the Replication specifications.
You can find more information at oasis-open.org
The UDDI Server supports all database vendors as by default, is SAP DB. If you want to run the UDDI server on an installation with another database, see Changing the Database of the UDDI Server.
The SOAP APIs exposed by the server are as follows:
· Inquiry API – http://<host>:<port>/uddi/api/inquiry
· Publishing API – http(s)://<host>:<port>/uddi/api/publish
The <hostname>:<port> represents the host name and HTTP port number relevant to your Web AS installation. The use of HTTP proxy for accessing the publishing API is determined by the configuration settings.
Configuration of the UDDI server is provided by the Visual Administrator tool. For more information, see Managing the UDDI Server in the Administration Manual.
See also:
Publishing a Web Service as a Business Service
Publishing a Web Service Definition as a tModel
UDDI Discovery for Creating Web Service Clients
Changing the Database of the UDDI Server