Network Deployment (Distributed operating systems), v8.0 > Reference > Developer detailed usage information


UDDI registry SOAP service end points

UDDI v3 supports multiple versions of SOAP API services. Depending on the security settings for WAS and the user data constraint transport guarantee settings for the UDDI SOAP service, UDDI v3 supports different end points for different services.

The following list of default context root and Uniform Resource Locator (URL) values apply when WAS security is enabled and you and do not change the default supplied security settings. If you do not use the default security settings, the context root and URL values might differ.

In the following URLs, the variables have the following values:

An endpoint is available for using HTTP GET to return XML representations of UDDI entities. See the information about HTTP GET services for UDDI registry data structures.

If you configure the UDDI registry to use WAS security, and you do not change the default data confidentiality settings for the UDDI SOAP service, services with default end point URLs with HTTPS and an SSL port require that their data is transported confidentially. Requests that do not use HTTPS are rejected.

If you configure the UDDI registry to use WAS security and you change the data confidentiality setting for the UDDI SOAP service to NONE, or you disable WAS security, services with default end point URLs with HTTPS and an SSL port can also use HTTP and a HTTP port.

To understand how access to the SOAP APIs is protected, see the information about access control for UDDI registry interfaces.
Access control for UDDI registry interfaces
Configure UDDI registry security
Configure the UDDI registry to use WAS security
Configure UDDI Security with WAS security disabled
UDDI registry client programming


Related


HTTP GET services for UDDI registry data structures

+

Search Tips   |   Advanced Search