Configure SOAP API and GUI services

 

Before you begin

Configuring V1 and V2 SOAP API services

You can configure the following V1 and V2 SOAP interface properties:

  • defaultPoolSize. This is the number of SOAP parsers with which to initialize the parser pool for the SOAP interface. We 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.

To configure these properties after the UDDI application has been installed:

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

            install_root/profiles/profile/config/cells/cell/applications/
          UDDIRegistry.node.servername.ear/deployments/
            UDDIRegistry.node.servername/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 V1 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 application server for the changes to take effect.

Configuring V3 SOAP API services

For the Version 3 SOAP interface, one can specify whether the Publish, Custody Transfer, Security and Inquiry API services are to be secure (accessed using HTTPS ) or insecure (accessed using HTTP). The default for Publish, Custody Transfer and Security APIs is to use HTTPS, and Inquiry to use HTTP.

To configure these properties after the UDDI application has been installed:

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

           install_root/profiles/profile/config/cells/cell/applications/
         UDDIRegistry.node.servername.ear/deployments/
           UDDIRegistry.node.servername/v3soap.war/WEB-INF

  2. Modify the user data constraint transport guarantee which determines whether the service is to be confidential (accessed using HTTPS) or insecure (accessed using HTTP). Use the table below to find the value of ‘security-constraint id’ for the service you wish to modify. Find the relevant security-constraint id in the deployment descriptor and set its ‘user-data-constraint’ ‘transport-guarantee’ to either CONFIDENTIAL or NONE.

    Type of UDDI service Value of security-constraint id
    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 application server for the changes to take effect.

Configuring V3 GUI services

For the Version 3 GUI interface, one can specify whether the Publish and Inquiry API services are to be secure (accessed using HTTPS) or insecure (accessed using HTTP). The default for Publish is to use HTTPS, and Inquiry to use HTTP.

To configure these properties after the UDDI application has been installed:

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

            install_root/profiles/profile/config/cells/cell/applications/
          UDDIRegistry.node.servername.ear/deployments/
            UDDIRegistry.node.servername/v3gui.war/WEB-INF

  2. Modify the user data constraint transport guarantee which determines whether the service is to be confidential (accessed using HTTPS) or insecure (accessed using HTTP). Use the table below to find the value of ‘security-constraint id’ for the service you wish to modify. Find the relevant security-constraint id in the deployment descriptor and set its ‘user-data-constraint’ ‘transport-guarantee’ to either CONFIDENTIAL or NONE.

    Type of UDDI service Value of security-constraint id
    Publish UDDIPublishSecurityConstraint
    Inquiry UDDIInquireSecurityConstraint

  3. Stop and restart the application server for the changes to take effect.

 

Related Tasks


Configuring the UDDI Registry to use WAS security