Before you begin
Note: Note that the UDDI4J Version 2 APIs are deprecated in WebSphere
Application Server Version 6. The IBM UDDI Version 3 Client for Java is the
preferred API for accessing UDDI using Java.
The following considerations
are specific to the support for UDDI4J specification provided by WebSphere
Application Server:
- UDDI4J class libraries provided.
WebSphere Application Server
provides two UDDI4J class libraries:
- uddi4jv2.jar
- This class library contains classes which support Version 2 of the UDDI
specification. The classes in this library are deprecated.
- uddi4j.jar
- This class library is provided for compatibility with WebSphere Application
Server and supports Version 1 of the UDDI specification. The classes in this
library are deprecated.
The UDDI4J methods map onto the UDDI Version 1 and
Version 2 SOAP inquiry and publish APIs. These APIs are protected as described
in
Access
control for UDDI Registry interfaces. If the role mappings for these
APIs are such that requests to these interfaces will require a WebSphere Application
Server authenticated userid, a client program using UDDI4J should pass the
user name and password by setting the system properties http.basicAuthUserName
and http.basicAuthPassword. A UDDI4J client program can also specify details
for a proxy server, including a user name and password, using the following
system properties:
- http.proxyHost
- http.proxyPort
- http.proxyUserName
- http.proxyPassword
You can find the API documentation for UDDI4J at the Javadoc
welcome page.