UDDI Registry Client Programming

 

Before you begin

This topic covers programmatic use of the UDDI APIs. The first subtopics describe some standard aspects of the UDDI APIs:

There are several ways in which one can programmatically access the UDDI APIs. The recommended client API is the IBM UDDI V3 Client for Java, 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:

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.

 

See also


UDDI Registry V3 Entity Keys
Use of digital signatures with the UDDI Registry
UDDI Registry Application Programming Interface
IBM 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)

 



 

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.