Show TOC Start of Content Area

Function documentation UDDI  Locate the document in its SAP Library structure

Use

The J2EE Engine provides a tool that fully implements the Universal Description Discovery and Integration (UDDI) functions based on the UDDI v2.0 specification. The tool is a Web-based client that you can use for publishing, browsing, and retrieving Web services based on the standard UDDI specification. You publish your Web services and Web service definitions in a public, private, or test registry.

Prerequisites

·        A J2EE Engine is installed and running.

·        The SAP Java Cryptographic Toolkit is installed on the J2EE Engine.

·        An sap.com/com.sap.engine.services.webservices.tool application is running.

·        An sap.com/tc~uddi application is running.

Note

Both applications are started automatically when the J2EE Engine is running.

·        SAP NetWeaver Developer Studio is installed and running.

·        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 knowledge of Web services and UDDI.

Features

You can start the UDDI client from the J2EE Engine Visual Administrator or simply by pointing the browser to the following URL: http://<host>:<port>/uddiclient.

Besides the UDDI client, a UDDI server is shipped with SAP Web AS Java that implements the OASIS standard: UDDI v2.0 specification excluding the Replication specification.

Link to external website

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

The UDDI Server supports all database vendors, but the default one 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 <host>:<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.

Activities

Using the UDDI client, you can perform the following actions:

·        Configuring the UDDI Client and UDDI Server

·        Publishing a Web Service as a Business Service

·        Publishing a Web Service Definition as a tModel

·        Creating a Web Service Client

·        Querying UDDI

·        Changing the Database of the UDDI Server

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