WAS v8.5 > Administer applications and their environment > Administer web services - UDDI registry > Administer the UDDI registry

Configure SOAP API and GUI services for the UDDI registry

For SOAP API and graphical user interface (GUI) UDDI services, we can configure whether the service is secure. For v1 and v2 SOAP API services, we can also configure the default pool size.

The UDDI registry application must be installed. For the v1 and v2 SOAP interface, we can configure the following properties:

• defaultPoolSize. The number of SOAP parsers with which to initialize the parser pool for the SOAP interface. We can set this property independently for the Publish (uddipublish) and Inquiry (uddi) APIs. For example, if you expect more inquiries than publish requests through the SOAP interface, we can set a larger pool size for the Inquiry API. The default initial size for both APIs is 10.
• Whether the API is secure, that is, accessed using HTTPS, or insecure, that is, accessed using HTTP. The default is to use HTTPS for the Publish API and HTTP for the Inquiry API.

For the v3 SOAP interface, we can specify whether Publish, Custody Transfer, Security and Inquiry APIs are secure, that is, accessed using HTTPS, or insecure, that is, accessed using HTTP. The default is to use HTTPS for the Publish, Custody Transfer, and Security APIs, and HTTP for the Inquiry API.

For the v3 GUI interface, we can specify whether the Publish and Inquiry services are secure, that is, accessed using HTTPS, or insecure, that is, accessed using HTTP. The default is to use HTTPS for the Publish service and HTTP for the Inquiry service.

• Optional: To configure v1 and v2 SOAP API services, use the following steps.
  1. Edit the active deployment descriptor, web.xml, for the v1 and v2 SOAP module, soap.war. The web.xml file is in the following directory:

     profile_root/config/cells/cell_name/applications/
     UDDIRegistry.node_name.server_name.ear/deployments/
     UDDIRegistry.node_name.server_name/soap.war/WEB-INF

  2. To modify the defaultPoolSize parameter for the v1 or v2 Publish API, modify the param-value element in the servlet with servlet-name = uddipublish.
  3. To modify the defaultPoolSize parameter for the v1 or v2 Inquiry API, modify the param-value element in the servlet with servlet-name = uddi.
  4. To set whether the Publish service is secure or insecure for the v1 or v2 Publish API, modify the user data constraint transport guarantee. Find the security-constraint element with id = UDDIPublishTransportConstraint. Set the user-data-constraint transport-guarantee for that element to CONFIDENTIAL, that is, the service is secure and is accessed using HTTPS, or NONE, that is, the service is insecure and is accessed using HTTP.
  5. Stop and restart the application server for the changes to take effect.

• Optional: For the v3 SOAP interface, specify whether the Publish, Custody Transfer, Security, and Inquiry API services are secure or insecure using the following steps. The default is to use HTTPS for the Publish, Custody Transfer, and Security APIs, and HTTP for the Inquiry API.
  1. Edit the active deployment descriptor, web.xml, for the v3 SOAP module, v3soap.war. The web.xml file is in the following directory:

     profile_root/config/cells/cell_name/applications/
     UDDIRegistry.node_name.server_name.ear/deployments/
     UDDIRegistry.node_name.server_name/v3soap.war/WEB-INF

     Each type of service is represented by a <security-constraint> element in web.xml. Each <security-constraint> element includes the <display-name> element and <user-data-constraint> <transport-guarantee> element.

  2. For each service to modify, search web.xml for the relevant <display-name> value (see the following table) to locate the <security-constraint> element for that service. Set the <user-data-constraint> <transport-guarantee> for that element to CONFIDENTIAL, that is, the service is secure and is accessed using HTTPS, or NONE, that is, the service is insecure and is accessed using HTTP.

     Display name values in web.xml for UDDI services. The table lists the different types of UDDI service and the value of the <security-constraint> <display-name> element for each one.

     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.

• Optional: For the v3 GUI interface, specify whether the Publish and Inquiry services are secure or insecure using the following steps. The default is to use HTTPS for the Publish service and HTTP for the Inquiry service.
  1. Edit the active deployment descriptor, web.xml, for the v3 GUI module, v3gui.war. The web.xml file is in the following directory:

     profile_root/config/cells/cell_name/applications/
     UDDIRegistry.node_name.server_name.ear/deployments/
     UDDIRegistry.node_name.server_name/v3gui.war/WEB-INF

  2. For each service to modify, search web.xml for the relevant <user-data-constraint> value (see the following table). Set the <user-data-constraint> <transport-guarantee> for that element to CONFIDENTIAL, that is, the service is secure and is accessed using HTTPS, or NONE, that is, the service is insecure and is accessed using HTTP.

     User data constraint ids in web.xml for UDDI services. The table lists the different types of UDDI service and the value of the <user-data-constraint id> element for each one.

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

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

Related

Configure the UDDI registry to use WAS security

+

Search Tips   |   Advanced Search