+

Search Tips   |   Advanced Search

UDDI registry client programming

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

The UDDI Version 3 registry supports multiple versions of UDDI. It supports UDDI Version 1, Version 2, and Version 3.

For details of the Version 1 and Version 2 API, refer to the UDDI Version 2 Specifications.

For details of the UDDI Version 3.0.2 API, refer to the UDDI Version 3.0.2 Specification.

The UDDI registry information in this information center defines the support that the UDDI registry provides for the UDDI Version 3.0.2 specification and associated addenda.

The following UDDI Version 3 API sets are supported:

Restriction: In DB2 for zSeries Version 7, the length of publish and inquiry strings are limited to 255 characters. If this limit is exceeded, error 10500 (E_Fatal) is returned. If we use a character set that uses multiple byte characters, it is easy to exceed this limit. Therefore, use care if you use this type of character set.

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

  2. Access the APIs programmatically. The recommended client API is the UDDI Version 3 Client, which allows access to the UDDI Version 3 APIs from Java client code.

    Other client APIs are provided for compatibility with previous versions of the UDDI registry:

    • The UDDI4J programming interface provides Java class libraries for accessing UDDI Version 1 and Version 2 APIs. These class libraries are both deprecated in this release, and are replaced by the UDDI Version 3 Client for Java.

    • The UDDI EJB Interface provides an EJB interface to the UDDI Version 2 APIs. The UDDI EJB interface is deprecated in this release.

    Although the recommended programmatic access to the UDDI APIs is through the UDDI Version 3 Client for Java, it is also valid to use the UDDI APIs directly by using SOAP. To use the SOAP API, construct a properly-formed UDDI message in the body of a SOAP request, and send it by using HTTP POST to the appropriate SOAP endpoint for the UDDI service. The response is returned in the body of the HTTP reply.

    The UDDI registry samples include samples that demonstrate how to program directly to the SOAP API. The samples are written in Java code, but we can use other programming languages to create the SOAP client, provided that you still send requests that are compliant to the SOAP specification. Valid UDDI requests must conform to the UDDI schema, as detailed in the UDDI specification

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


Subtopics


Related information:

Samples for WebSphere Application Server
UDDI Version 2 Specifications
UDDI Version 3.0.2 Specification