Before you begin
The UDDI4J methods map onto the UDDI 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 that interface will require a WebSphere Application Server authenticated userid, a client program using UDDI4J should pass the userid and password by setting the relevant system properties, such as http.basicAuthUserName.
You can find the API documentation for UDDI4J at the Javadoc welcome page.
Note that the uddi4jv2 APIs are deprecated in IBM WebSphere UDDI Registry Version 3. The IBM UDDI Version 3 Client for Java is the preferred API for accessing UDDI using Java.