Configure SOAP API and GUI services for the UDDI registry

 

For SOAP API and graphical user interface (GUI) UDDI services, you can configure whether or not the API is secure. For SOAP API services you can also configure the default pool size. You must have installed the UDDI registry application.

 

Overview

For the V1 and V2 SOAP interface, you can configure the following properties:

• defaultPoolSize. This is the number of SOAP parsers with which to initialize the parser pool for the SOAP interface. You can set this independently for the Publish (uddipublish) and Inquiry (uddi) APIs. For example, if you expect more inquiries than publish requests through the SOAP interface, you can set a larger pool size for the Inquiry API. The default initial size for both APIs is 10.

• Whether the API is to be secure (accessed using HTTPS) or insecure (accessed using HTTP). The default for Publish is to use HTTPS and Inquiry to use HTTP.

For the V3 SOAP interface, you can specify whether Publish, Custody Transfer, Security and Inquiry APIs are to be secure (accessed using HTTPS) or insecure (accessed using HTTP).

For the V3 GUI interface, you can specify whether the Publish and Inquiry API services are to be secure (accessed using HTTPS) or insecure (accessed using HTTP).

 

Procedure

 

• Optional: Configure V1 and V2 SOAP API services by performing the following steps.

  1. Edit the active deployment descriptor (web.xml) for the Version 1 and V2 SOAP module (soap.war). This file is located in the following directory:

             profile_root/config/cells/cell/applications/
               UDDIRegistry.node.server.ear/deployments/
                 UDDIRegistry.node.server/soap.war/WEB-INF
     

  2. To modify defaultPoolSize for V1 or V2 Publish, modify the ‘param-value’ element in the servlet with ‘servlet-name’ = uddipublish

  3. To modify defaultPoolSize for V1 or V2 Inquiry, modify the ‘param-value’ element in the servlet with ‘servlet-name’ = uddi

  4. To modify the user data constraint transport guarantee for Version 1 or V2 publish, which determines whether the Publish service is to be confidential (accessed using HTTPS) or insecure (using HTTP), find the ‘security-constraint’ with id = ‘UDDIPublishTransportConstraint’ and set its ‘user-data-constraint’ ‘transport-guarantee’ to CONFIDENTIAL or NONE.

  5. Stop and restart the appserver for the changes to take effect.

   

• Optional: For the V3 SOAP interface, specify whether the Publish, Custody Transfer, Security and Inquiry API services are to be secure or insecure by performing the following steps. The defaults are for Publish, Custody Transfer and Security APIs to use HTTPS, and for the Inquiry API to use HTTP.

  1. Edit the active deployment descriptor (web.xml) for the Version 3 SOAP module (v3soap.war). This file is located in the following directory:

            profile_root/config/cells/cell/applications/
              UDDIRegistry.node.server.ear/deployments/
                UDDIRegistry.node.server/v3soap.war/WEB-INF
     

  2. Locate the <security-constraint> element for the service to modify by searching the deployment descriptor (web.xml) file for the relevant <display-name> value (see the table below). When you have found the <security-constraint> element, set its <user-data-constraint> <transport-guarantee> to either CONFIDENTIAL (the service can only be accessed using HTTPS) or NONE (the service can be accessed using HTTP). The <security-constraint> element represents a type of service, and contains the <display-name> element, <user-data-constraint> <transport-guarantee> elements, and other elements.

     Type of UDDI service	Value of <security-constraint> <display-name> element
     Publish	AxisServlet Publish Resource Collection
     Custody transfer	AxisServlet CustodyTransfer Resource Collection
     Security	AxisServlet Security Resource Collection
     Inquiry	AxisServlet Inquiry Resource Collection

  3. Stop and restart the appserver for the changes to take effect.

   

• Optional: For the V3 GUI interface, specify whether the Publish and Inquiry API services are to be secure or insecure by performing the following steps. The defaults are for the Publish API to use HTTPS, and the Inquiry API to use HTTP.

  1. Edit the active deployment descriptor (web.xml) for the Version 3 GUI module (v3gui.war). This file is located in the following directory:

             profile_root/config/cells/cell/applications/
               UDDIRegistry.node.server.ear/deployments/
                 UDDIRegistry.node.server/v3gui.war/WEB-INF
     

  2. Use the table below to find the id value for the <user-data-constraint> element that corresponds with the service to change. Search for this value in the deployment descriptor (web.xml) file to find the <user-data-constraint> element, then set the <user-data-constraint> <transport-guarantee> to either CONFIDENTIAL (the service can only be accessed using HTTPS) or NONE (the service can be accessed using HTTP).

     Type of UDDI service	Value of <user-data-constraint id>
     Publish	UDDIPublishTransportConstraint
     Inquiry	UDDIInquireTransportConstraint

  3. Stop and restart the appserver for the changes to take effect.

---

 

Related tasks

Configure the UDDI registry to use WAS security
Use the UDDI registry