+

Search Tips   |   Advanced Search

 

UDDI registry client programming

 

The UDDI registry provides several application programming interfaces (APIs) which you can use to access the UDDI registry programmatically.

 

Procedure

  1. Learn about the standard aspects of the UDDI APIs using the following topics.

  2. Access the APIs programmatically in one of several different ways. The recommended client API is the UDDI V3 Client, which allows access to the UDDI V3 APIs from Java client code. Other client APIs are provided for compatibility with previous versions of the UDDI registry:

    • UDDI4J provides Java class libraries for accessing UDDI V1 and V2 APIs. These class libraries are both deprecated in this release, and replaced by the UDDI V3 Client for Java. See UDDI4J programming interface (Deprecated) for further details.

    • UDDI EJB Interface (Deprecated) provides an EJB interface to the UDDI V2 APIs. The UDDI EJB interface is deprecated in this release.

    Although the recommended programmatic access to the UDDI APIs is through the UDDI V3 Client for Java, it is also valid to use the UDDI APIs directly using SOAP. This can be done by constructing a properly-formed UDDI message within the body of a SOAP request, and sending it using HTTP POST to the appropriate SOAP endpoint for the UDDI service (see UDDI registry SOAP service end points. The response will be returned within the body of the HTTP reply.

    Support is also provided for the use of HTTP GET to return XML representations of UDDI entities: see HTTP GET services for UDDI registry data structures for details.



UDDI registry V3 entity keys

Use of digital signatures with the UDDI registry

UDDI registry Application Programming Interface

UDDI V3 Client

HTTP GET services for UDDI registry data structures

UDDI registry SOAP service end points

UDDI4J programming interface (Deprecated)

UDDI EJB Interface (Deprecated)

 

Related tasks


Use the UDDI registry