CA API Gateway 9.1

9.4 9.1

Searching the UDDI Registry

The Search UDDI dialog allows you to search a UDDI registry while performing the following tasks:
gateway
The Search UDDI dialog allows you to search a UDDI registry while performing the following tasks:
  • When publishing a SOAP web service, you can enter either the URL or file path to the WSDL document. If a UDDI registry has been configured, you can also search the UDDI to retrieve the appropriate URL.
  • When publishing a business service, you can search a UDDI registry for a specific business entity.
    Before you can search a UDDI registry, ensure that the UDDI registry product is correctly installed and at least one UDDI registry has been configured in the Gateway. 
To search a UDDI registry:
  1. Do one of the following:
    • Click [
      UDDI
      ] button in Step 1 of the Publish SOAP Web Service Wizard. If the [UDDI] button is not visible, then no UDDI registries were configured. 
    • Click the [
      Select
      ] button on the [UDDI] tab of the Service Properties dialog.
    The Search UDDI dialog is displayed. The following example shows the dialog that is displayed when searching for a WSDL URL from a UDDI registry.
  2. Configure the search as follows:
    Setting
    Description
    UDDI Registries
    From the drop-down list, select the UDDI registry to be searched. Only registries that are enabled are shown.
    Service Name
    To refine your search, you can optionally specify that the Service Name Contains or Equals the string of characters that you specify. ('Contains' encloses the search string within '%' characters.)
    Leave the Service Name search field blank to retrieve all available services.
    Case Sensitive
    Select this check box to make the search case sensitive.
    Allow Wildcards
    Select this check box to use the percent symbol (%) wildcard to match any number of characters, or the underscore symbol (_) to match any single character.
    Wildcards can be used with both 'Contains' and 'Equals'. When used with 'Contains', they work in addition to the '%' already added to the start and end of the entered search text.
    Retrieve WSDL URL in search results
    (only for Service searches)
    Select this check box to retrieve the WSDL URL for each service in the search results. Clearing this check box will improve the search performance as only a single UDDI query needs to be made.
    Many UDDI queries are required to assemble the list of service names and WSDL locations. By omitting the WSDL URL, fewer searches are required and the results are returned more quickly. When you select a service, the WSDL location is then resolved for that service.
    [Search]
    Click this button to begin the search. The search will run until it returns results or is cancelled by the user.
    Results
    The number of items found is displayed. The table shows the results of the search.
    The WSDL Locations column will be blank if the Retrieve WSDL URL in search results check box is not selected.
    Show select wsdl:port dialog
    (only for Service searches)
    Select this check box if you need to select a specific port to use from the WSDL. See "Selecting a wsdl:port" below for more information.
  3. Click [
    Select
    ] after selecting the Business Service or Business Entity. The Search UDDI dialog closes and your selected service is added to the previous dialog.
Selecting a wsdl:port
When the
Show select wsdl:port
 check box is selected, the "Select wsdl:port" dialog is displayed after you select a row and click [Select]. This dialog allows you to select a specific wsdl:port to use.
Why select a wsdl:port? You will do this if you want to place the published service's WSDL to be under the control of the UDDI registry. Once the WSDL is under UDDI control, its possible to enable monitoring. Monitoring cannot be enabled unless the Gateway knows which specific wsdl:port (bindingTemplate) in the UDDI Business Service to monitor.
Technical Note
When a Gateway publishes a WSDL to a UDDI Registry, it may publish each wsdl:port twice, if the Gateway cluster defines an HTTPS and an HTTP endpoint. When this happens, the search results will shown more than a single wsdl:port and possibly namespace with the same values. In this case the endpoint values should differ by protocol. For WSDL's published to UDDI which do not originate from the Gateway, the wsdl:port and namespace columns uniquely identify each wsdl:port from a WSDL.

Content feedback and comments