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 user ID, 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