+

Search Tips   |   Advanced Search

UDDI registry SOAP service end points

UDDI Version 3 supports multiple versions of SOAP API services. Depending on the security settings for WebSphere Application Server and the user data constraint transport guarantee settings for the UDDI SOAP service, UDDI Version 3 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 we 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 we configure the UDDI registry to use WAS security, and we 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 we configure the UDDI registry to use WAS security and we 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.


Related:

  • 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
  • HTTP GET services for UDDI registry data structures