UDDI Server and Services Registry 

At the core of the Services Registry is an open standard UDDI v3.0 conformant registry. Wherever the Services Registry is present in a landscape, it needs a UDDI Server and a classification service.

The UDDI server has the following basic architecture:

UDDI Server Components

·        Web User Interface

The Web 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 the UDDI client with:

http://<host>:<port>/index.html

and then choose UDDI Client.

In the <host> field, enter the required host name. In the <port> name, enter 50000. By default, the port is 50000. The Web User Interface can be used if a JEE engine has been started and the UDDI server has been configured on this application server.

For more information about the UDDI client see UDDI Registry.

●      SOAP API

UDDI servers can be operated either manually through the browser or through client programs using SOAP 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.

●      Database

The UDDI registry data is usually stored in a relational database.

●      UDDI Server Logic

The UDDI server logic implements the search and publication functions defined in the UDDI standard. 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.

More information:

UDDI Server Configuration