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
UDDI4J programming interface (Deprecated)
The UDDI4J v2 APIs are deprecated in this version of WAS. The UDDI v3 Client for Java is the preferred API for accessing UDDI through Java code.
WAS provides UDDI4J classes in the com.ibm.uddi.jar file. This file contains classes that support v1 and v2 of the UDDI specification, providing compatability with earlier versions of WAS. The UDDI4J classes in this file are deprecated.
The UDDI4J methods map onto the UDDI v1 and v2 SOAP Inquiry and Publish APIs. These APIs are protected by access control mechanisms, for example role mappings. If the role mappings for these APIs are such that requests to these interfaces require a WAS authenticated user ID, a client program that uses UDDI4J must pass the user name and password, by setting the system properties //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .basicAuthUserName and //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .basicAuthPassword. A UDDI4J client program can also specify details for a proxy server, including a user name and password, by using the following system properties:
- //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .proxyHost
- //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .proxyPort
- //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .proxyUserName
- //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .proxyPassword
Related
UDDI v3 Client
Access control for UDDI registry interfaces
UDDI registry client programming
Additional Application Programming Interfaces (APIs)