The usage of UDDI APIs

It is possible to use UDDI web service API s to do different operations such as search services, add services, add businesses and many more. Governance Registry contains UDDI WS-APIs and are able to perform previously mentioned operations.

Follow the given steps to test UDDI API services.

1. First configure Governance Registry server to make WSDLs of admin services to be vsisble. To do that make the value of the following configuration false in carbon.xml at GREG_HOME/repository/conf/.

   <HideAdminServiceWSDLs>false</HideAdminServiceWSDLs>

   
   

2. Start Governance Registry server as mentioned in Support for UDDI. 
   
   
3. Now a user can view the WSDLs of UDDI API services and it is possible to create external clients which can perform UDDI operations on Governance Registry. The WSDL of UDDIInquiryService can be accessed as below.
   https://localhost:9443/services/UDDIInquiryService?wsdl 
   
   
   
   
4. For an example if the server is UDDI enabled and when a user adds a service from the Governance Registry side that resource would also get added to UDDI registry. Therefor a user can view any service  added at Governance Registry side using the UDDIInquiryService.This can be perform as follows. 
   
   
   1. Add a WSDL to the Governance Registry. (E.g. - http://www.webservicex.net/globalweather.asmx?wsdl ) ,This would create the corresponding service.
      
      
      
      
   2. Use a tool like soapUI to send a request to the UDDIInquiryService . First the user has to create a project in soapUI using the UDDIInquiryService WSDL as given below.
      
      
      
      
   3.  When the new project is created it will display all the available operations of the service on the left hand side menu of soapUI. Users are able to rename the requests of operations listed out in the menu. 
      
      
      
      

   4. In here the user can use find_business to find any business added in the UDDI registry. For the following SOAP request all the businesses in UDDI registry would return. Users are able to edit the SOAP request as they preferred to get expected results.  

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:uddi-org:api_v3">
         <soapenv:Header/>
         <soapenv:Body>
            <urn:find_business>
               <urn:findQualifiers>
                  <!--1 or more repetitions:-->
                  <urn:findQualifier>approximateMatch</urn:findQualifier>
               </urn:findQualifiers>
               <!--Zero or more repetitions:-->
               <urn:name>%</urn:name>
            </urn:find_business>
         </soapenv:Body>
      </soapenv:Envelope>

      The service that has been added from the Registry side can be seen in the list of services as given below.

      
      

   5. Users can use find_service method to find any service added in the UDDI registry. The following SOAP request can be used to search for the WeatherForecast service. Users are able to edit the SOAP request as they preferred to get expected results.

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:uddi-org:api_v3">
         <soapenv:Header/>
         <soapenv:Body>
            <urn:find_service>
               <urn:findQualifiers>
                  <!--1 or more repetitions:-->
                  <urn:findQualifier>approximateMatch</urn:findQualifier>
               </urn:findQualifiers>
               <!--Zero or more repetitions:-->
               <urn:name>WeatherForecast</urn:name>
            </urn:find_service>
         </soapenv:Body>
      </soapenv:Envelope>

       

      

5. Similar to UDDIInquiryService other service API classes can also be tested on governance registry using the soapUI. 
    
6. Refer the section JAXR sample  in order to know how to use the JAXR API against UDDI.