Configure SOAP API and GUI services

Configuring Version 1 and Version 2 SOAP API services You can configure the following Version 1 and Version 2 SOAP interface 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.

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

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

           install_root/profiles/profile_name/config/cells/cell_name/applications/
             UDDIRegistry.node.server_name.ear/deployments/
               UDDIRegistry.node.server_name/soap.war/WEB-INF

2. To modify defaultPoolSize for Version 1 or Version 2 Publish, modify the 'param-value' element in the servlet with 'servlet-name' = uddipublish

3. To modify defaultPoolSize for Version 1 or Version 2 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 Version 2 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 Version 3 SOAP API services

For the Version 3 SOAP interface, you 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 Version 3 SOAP module (v3soap.war). This file is located in the following directory:

          install_root/profiles/profile_name/config/cells/cell_name/applications/
            UDDIRegistry.node.server_name.ear/deployments/
              UDDIRegistry.node.server_name/v3soap.war/WEB-INF

2. Each type of service is represented in the deployment descriptor (web.xml) file by a <security-constraint> element, which contains, amongst other things, a <display-name> element and a <user-data-constraint> <transport-guarantee> element. Locate the <security-constraint> element for the service that you want 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).

   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 application server for the changes to take effect.

Configuring Version 3 GUI services

For the Version 3 GUI interface, you 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 Version 3 GUI module (v3gui.war). This file is located in the following directory:

           install_root/profiles/profile_name/config/cells/cell_name/applications/
             UDDIRegistry.node.server_name.ear/deployments/
               UDDIRegistry.node.server_name/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 that you want 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 application server for the changes to take effect.

Related tasks
Configuring the UDDI Registry to use WebSphere Application Server security