Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - UDDI registry > Develop with the UDDI registry
UDDI registry client programming
The UDDI registry provides several API that you can use to access the UDDI registry programmatically. The UDDI v3 registry supports multiple versions of UDDI. It supports UDDI v1, v2, and v3.
For details of the v1 and v2 API, refer to the UDDI Version 2 Specifications.
For details of the UDDI v3.0.2 API, refer to the UDDI v3.0.2 Specification.
The UDDI registry information in this information center defines the support that the UDDI registry provides for the UDDI v3.0.2 specification and associated addenda.
The following UDDI v3 API sets are supported:
- The UDDI V3 Inquiry API
- The UDDI V3 Publish API
- The UDDI V3 Custody and Ownership Transfer API
- The UDDI V3 Security API
Restriction: In DB2 for zSeries v7, the length of publish and inquiry strings are limited to 255 characters. If this limit is exceeded, error 10500 (E_Fatal) is returned. If you 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.
Procedure
- Learn about the standard aspects of the UDDI APIs by using the following topics.
- UDDI registry v3 entity keys explains UDDI entity keys, and the capability with UDDI v3 to save UDDI entities with publisher-assigned keys.
- Digital signatures and the UDDI registry explains the support for digital signing of UDDI entities, and for validation of signatures.
- Access the APIs programmatically. 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:
- The UDDI4J programming interface provides Java class libraries for accessing UDDI Version 1 and v2 APIs. These class libraries are both deprecated in this release, and are replaced by the UDDI v3 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 v3 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 you can use other programming languages to create your 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.
Related
Inquiry API for the UDDI v3 registry
Publish API for the UDDI v3 registry
Custody and Ownership Transfer API for the UDDI v3 registry
Security API for the UDDI v3 registry
UDDI registry v3 entity keys
Digital signatures and the UDDI registry
UDDI v3 Client
UDDI4J programming interface (Deprecated)
Use the UDDI EJB Interface (Deprecated)
UDDI registry SOAP service end points
HTTP GET services for UDDI registry data structures
Use the UDDI registry
Samples for WAS
UDDI v2 Specifications
UDDI v3.0.2 Specification