Show TOC Start of Content Area

Function documentation UDDI Registry

Use

SAP NetWeaver AS Java provides a UDDI server and UDDI client that fully implement the Universal Description Discovery and Integration (UDDI) functions based on the UDDI v3.0 specification. The client is a Web Dynpro application that you can use for publishing, browsing, and retrieving tModels, business entities, binding templates, and business services based on the standard UDDI specification. You publish your services and business entities in a registry that is part of the AS Java installation.

Prerequisites

      A sap.com/tc~uddi application is running.

Note

The application is started automatically when running the AS Java.

      You have knowledge in Web services and UDDI.

Features

The UDDI server is shipped with SAP NetWeaver AS Java that implements the OASIS standard: UDDI v3.0 specification.

Link to external website

You can find more information at www.oasis-open.org.

The default 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

·        Security API – http://<host>:<port>/uddi/api/security

·        Subscription API – http://<host>:<port>/uddi/api/subscription

The <host>:<port> represents the host name and HTTP port number relevant to your SAP NetWeaver AS Java installation. The use of HTTP proxy for accessing the publishing API is determined by the configuration settings.

Activities

You can start the UDDI client from the start page of the AS Java http://<host>:<port>.

Using the UDDI client, you can:

      Create and publish tModels

      Create and publish business entities

      Create and publish business services

      Search in the UDDI registry

Example

The following scenarios describe some of the cases where the UDDI functions are in use:

      One company publishes a standard in UDDI and the others can find and use the same standard.

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 standard Web service interface already exists and you want to see who supports it, and to choose the one that suits you best.

 

...

End of Content Area